mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: hal@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, rpurdie@rpsys.net,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: 2.6.30: hald crashes on resume from STR apparently on LED device
Date: Sun, 14 Jun 2009 22:19:02 +0400	[thread overview]
Message-ID: <200906142219.06891.arvidjaar@mail.ru> (raw)

[-- Attachment #1: Type: Text/Plain, Size: 4727 bytes --]

I did not experience this crash under 2.6.29. I got it under 2.6.30 
(both rc and final) with varying frequency. At least for me it is 2.6.30 
regression.

hald aborts on D-Bus assertion with stack trace below.Program received 
signal SIGABRT, Aborted.
0x00007f183ff9e915 in raise (sig=<value optimized out>) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64	  return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0  0x00007f183ff9e915 in raise (sig=<value optimized out>) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00007f183ff9ff8a in abort () at abort.c:88
#2  0x00007f1840793f35 in _dbus_abort () at dbus-sysdeps.c:88
#3  0x00007f184078fd6d in _dbus_warn_check_failed (
    format=0x7f184079c5a0 "arguments to %s() were incorrect, assertion 
\"%s\" failed in file %s line %d.\nThis is normally a bug in some 
application using the D-Bus library.\n") at dbus-internals.c:283
#4  0x00007f18407873f9 in dbus_pending_call_set_notify (pending=0x0, 
function=0x41b320 <reply_from_singleton_device_changed>, 
    user_data=0xc74c30, free_user_data=0x416000 <del_sdci>) at dbus-
pending-call.c:598
#5  0x0000000000415f6e in singleton_signal_device_changed 
(connection=0xbdc140, device=0x7f18411af2c0, added=1)
    at hald_dbus.c:3481
#6  0x0000000000419fe2 in hald_singleton_device_added 
(command_line=0xc601e0 "hald-addon-leds", device=0x7f18411af2c0)
    at hald_dbus.c:3570
#7  0x0000000000413e5f in gdl_store_changed (store=<value optimized 
out>, device=0x7f18411af2c0, 
    is_added=<value optimized out>, user_data=<value optimized out>) at 
hald.c:134
#8  0x00007f1840c78bae in IA__g_closure_invoke (closure=0xbcba10, 
return_value=0x0, n_param_values=3, param_values=0xc914a0, 
    invocation_hint=0x7fff3cac7d20) at gclosure.c:767
#9  0x00007f1840c8f108 in signal_emit_unlocked_R (node=0xbca8a0, 
detail=<value optimized out>, instance=<value optimized out>, 
    emission_return=<value optimized out>, instance_and_params=<value 
optimized out>) at gsignal.c:3247
#10 0x00007f1840c9059e in IA__g_signal_emit_valist (instance=0xbbd600, 
signal_id=<value optimized out>, detail=0, 
    var_args=0x7fff3cac7f10) at gsignal.c:2980
#11 0x00007f1840c90b33 in IA__g_signal_emit (instance=0xbc7, 
signal_id=3015, detail=6) at gsignal.c:3037
#12 0x0000000000411d01 in hal_device_store_add (store=0xbbd600, 
device=0x7f18411af2c0) at device_store.c:277
#13 0x0000000000430d72 in dev_callouts_add_done (d=0x7f18411af2c0, 
userdata1=0xc6ee20, userdata2=<value optimized out>)
    at device.c:4666
#14 0x00000000004086c4 in hal_util_callout_device_add (d=0x7f18411af2c0, 
callback=0x430d10 <dev_callouts_add_done>, 
    userdata1=0xc6ee20, userdata2=0x0) at util.c:996
#15 0x0000000000408524 in hal_util_callout_device_preprobe 
(d=0x7f18411af2c0, 
    callback=0x4310e0 <dev_callouts_preprobing_done>, 
userdata1=0xc6ee20, userdata2=0x657fa0) at util.c:1035
#16 0x0000000000425394 in hotplug_event_begin_sysfs 
(hotplug_event=0xc6ee20) at hotplug.c:172
#17 0x00000000004257a8 in hotplug_event_process_queue () at 
hotplug.c:295
#18 0x00000000004242b7 in hald_udev_data (source=<value optimized out>, 
condition=<value optimized out>, 
    user_data=<value optimized out>) at osspec.c:259
#19 0x00007f18409e1a4e in IA__g_main_context_dispatch (context=0xbc0320) 
at gmain.c:1814
#20 0x00007f18409e51b8 in g_main_context_iterate (context=0xbc0320, 
block=<value optimized out>, 
    dispatch=<value optimized out>, self=<value optimized out>) at 
gmain.c:2445
#21 0x00007f18409e5645 in IA__g_main_loop_run (loop=0xbbcc20) at 
gmain.c:2653
#22 0x00000000004133ed in main (argc=<value optimized out>, 
argv=0x7fff3cac9b50) at hald.c:821


Appearance of hald-addon-leds may be red herring; still here is the only 
led device I have (for Intel 3946ABG).

udi = '/org/freedesktop/Hal/devices/leds_iwl_phy0_radio'
  info.addons.singleton = {'hald-addon-leds'} (string list)
  info.capabilities = {'leds'} (string list)
  info.category = 'leds'  (string)
  info.interfaces = {'org.freedesktop.Hal.Device.Leds'} (string list)
  info.parent = '/org/freedesktop/Hal/devices/pci_8086_4222'  (string)
  info.subsystem = 'leds'  (string)
  info.udi = '/org/freedesktop/Hal/devices/leds_iwl_phy0_radio'  
(string)
  leds.device_name = 'iwl-phy0'  (string)
  leds.function = 'radio'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'leds'  (string)
  linux.sysfs_path = 
'/sys/devices/pci0000:00/0000:00:1c.1/0000:0c:00.0/leds/iwl-phy0::radio'  
(string)


 This is Dell XPS M1330 notebook. I am ready to provide any required 
information; so far crash is reproducible after several suspend/resume 
cycles. 

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-06-14 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 18:19 Andrey Borzenkov [this message]
2009-06-21 14:17 ` Andrey Borzenkov
2009-06-22 13:57   ` Richard Purdie
2009-06-27 20:34     ` Andrey Borzenkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200906142219.06891.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=hal@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=rpurdie@rpsys.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®