[Bug 16396] HAL causing system lockup after suspend/resume cycles.

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Sun Oct 2 02:17:38 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=16396
Ubuntu | hal





------- Additional Comments From mark at veravirtus.com  2005-10-02 03:17 UTC -------
First, I'd just like to thank you for taking the time to reply.  Unfortunately,
I ran into some problems though.

On Hoary, I couldn't even get a disk write before the system locked up so
hal.log was gone after rebooting.

Here are the last few lines though, copied by hand:

[I] callout.c:318: Invoking /etc/hal/device.d/40-hal-hotplug-map.hal
[I] callout.c:330: Child pid 10814 for 40-hal-hotplug-map.hal
[I] callout.c:193: Callouts done for /org/freedesktop/Hal/devices/ide_host_1
[I] callout.c:173: Child pid 10814 terminated
[I] hald.c:81: Added device to GDL; udi=/org/freedesktop/Hal/devices/ide_1_0
[I] linux/osspec.c:804: handling /sys/block/hdc block
[I] linux/block_class_device.c:1415: Bus type is ide!

And that's where it freezes.  I want to note that it only freezes if I suspend
at least 2 times or more.  If I just suspend once, I can start hald with no
problems.

Now, onto Breezy.  Again, I don't think I managed to capture all of the verbose
output before it crashes.  But hal.log was still there when I rebooted.  Just in
case, I'll also copy the last couple of lines by hand.

[I] hald_dbus.c:2731: 10282: Got a connection
[I] hald_dbus.c:2732: dbus_connection_get_is_connected = 1
[I] hald_dbus.c:2693: local_server_message_handler: destination=(null)
obj_path=/org/freedesktop/DBus/Local interface=org.freedesktop.DBus.local
method=Disconnected
[I] hald_dbus.c:2709: Client to local_server was disconnected
[I] hald_dbus.c:2719: unregistered
[I] util.c:517: child exited for pid 10296
[I] classdev.c:880: entering; timed_out=0, return_code=1
[I] classdev.c:964: class_add: subsys=input sysfs_path=/sys/class/input/mouse1
dev=/dev/input/mouse1 physdev=0x080b64e8
*** handling /dev/input/mouse1
[I] hald_dbus.c:2731: 10282: Got a c

And it freezes right there.  I guess it would have said ...onnection.  :P

And here's what I got out of <a hef="http://veravirtus.com/hal.log">hal.log</a>
 and <a href="http://veravirtus.com/kern.log">kern.log</a>.

And here are some more observations.

1)  Like I already said before, hald only causes me to crash if I suspend two or
more times.

2)  On Breezy, attempting to suspend the third time, even with hald disabled
doesn't completely crash the system but pretty much makes it unresponsive.  This
is before even successfully suspending.  It just starts scrolling "hdc: lost
interrupt" after "Stopping tasks ======= etc.".  If it hit some keys on the
keyboard, I get "psmouse.c: bad data from KBC - timeout" and occasionally I'll
get "query EC, IB not empty" twice at a time.  I can still switch ttys, however
going back to X crashes it completely.  I've suspended/resumed the system many,
many times on Hoary without any problems, as long as hald is disabled.

3)  Also on Breezy.  hald seems to freeze at random times when restarting it. 
What I mean is, I don't see the same messages right before it crashes.  In fact,
it looks like it freezes at a completely differenct point. For example, the
lines I copied up top have something to do with the mouse, but on a second run,
it freezes during what looks like USB probing. Hoary on the other hand ALWAYS
freezes at the same spot (the messages I wrote down up top).

Anyway, let me know if there's anything else I can do.  I wish I could provide
some more information.
Thanks again.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the desktop-bugs mailing list