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

Fri Sep 30 08:09:43 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

martin.pitt at ubuntu.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO

------- Additional Comments From martin.pitt at ubuntu.com  2005-09-30 09:09 UTC -------
(In reply to comment #0)

> Anyway, after a bunch of testing, I narrowed the problem down to hal.  If I
> remove hal, everything works fine.  With hal installed, I can't resume after my
> first suspend/resume cycle.  (I still don't see why it would work once, but fail
> the next time.)  So, I tried adding dbus-1 to /etc/defaults/acpi-support in the
> STOP_SERVICES section.  It still locks up on subsequent resumes  BUT I actually
> get my console back.  It freezes right after that though (keyboard not
> responsive, etc).

OK, from that I guess that stopping hal, suspending, and resuming should work
fine, and your computer freezes as soon as you start hal after resuming.

What you can try is: 

  * remove dbus from STOP_SERVICES again
  * manually stop hal with "sudo killall hald"
  * suspend, resume
  * do you get a working system?
  * then please start hal in debugging mode:
      sudo hald --drop-privileges --daemon=no --verbose=yes 2>&1 | tee ~/hal.log
    and look how far it comes? it should freeze at some point. the output should
be recorded in ~/hal.log, can you please attach this here? Please also attach
your /var/log/kern.log.

Thanks!

P.S. hal is the daemon that monitors hardware and provides the foundation for
automatically mounting removable devices, monitor battery status, etc.

-- 
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.