Package: kernel
Severity: important

Hi all,

this is a clone of the Ubuntu bug #1940 [1] and has been reported before
as Debian bug #286820 "hal - breaks resume on iBook G3". 
The latter has been closed by the hal maintainer with the following
reasoning:

> On Wed, Dec 22, 2004 at 02:22:21PM +0100, Bastian Blank wrote:
>> Package: hal
>> Severity: important
>> Version: 0.4.2-3
>>
>> hal breaks resume on my iBook G3 if it is able to access the cdrom.
>> The real reason is currently unknown, but it happens before the
>> kernel resumes the cdrom device.
>
> This is a kernel problem, not a hal problem. If you don't want hal
> polling your cdrom you should disable it. 

<rant>
It would have been more appropriate to reassign the bug instead of just
closing it.
</rant>

Reading the comments at Ubuntu Bugzilla, it seems the bug is present in
kernel 2.6.8 and 2.6.10 at least.

This issue should be recorded in the BTS. Since bug #286820 is archived
and cannot be reopened, I'm filing a new bug. If you think it should be
filed against another kernel package, please reassign it accordingly. 

Regards,
Nikolaus

[1] https://bugzilla.ubuntu.com/show_bug.cgi?id=1940

PS:
As far as hal is concerned, here's a (slightly modified) workaround from
Ubuntu's Bugzilla that stops hal before suspend. Copy to
/etc/power/scripts.d and create a symlink in /etc/power/event.d.

#!/bin/sh

# name        : hal
# author      : Carlos A. Paramio <[EMAIL PROTECTED]>
# description : Stops/starts hal service before/after suspend
# requirements: 
# limitations : 

# <NS>
# Hal/dbus-1 breaks suspend/resume.
# As a workaround, this script stops dbus-1 (and thus hal) 
# before we suspend. The patch is taken from an Ubuntu bugreport. 
#
# Changelog: 
# * use invoke-rc.d instead of calling /etc/init.d/dbus-1

PATH=/bin:/sbin:/usr/bin:/usr/sbin

case "$1" in
  powersave)
    ;;
  custom)
    ;;
  performance)
    ;;
  suspend)
    invoke-rc.d --quiet dbus-1 stop
    ;;
  resume)
    invoke-rc.d --quiet dbus-1 start
    ;;
esac

exit 0


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to