[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: iBook2 doesn't resume properly after sleep

In-reply-to: <20040401102152.GA1577@osiris>

I have also recently had a persistent problem resuming my iBook2 after sleep. The problem came with one of the upgrade to 2.6.8 and has continued into 2.6.9. As reported by the previous people, the system must be rebooted. Not only doesn't it resume X, but you cannot switch consoles. I haven't tested whether ethernet access is enabled.

I suspected X when the system also froze after logout, when it recycled gdm. However, the sleep problem happens just the same when X is not running (/etc/init.d/gdm stop).

Under 2.6.8, when resuming it shows the usual text screen and gets this far:
   aty128fb: resumed!
   enable_irq(27) unbalanced
   enable_irq(28) unbalanced
   eth0: resuming
   PHY ID: 4061e4, addr: 0
   eth0: Link is up [etc]
   eth0: Pause is disabled
That's as far as it gets. Somewhere during that sequence, it starts fiddling with the cdrom. That might be significant, because someone else reported that their problem went away when they stopped running wmcdplay. I'll note that on my system, it finds the cdrom fine as hdb, but udev neglects to provde the /dev/cdrom link. So something might be up. However, I get the same error when I manually insert the cdrom symlink (which is what I need to do (each boot) to use my cd/dvd drive).

Under 2.6.9, the text is slightly different, including an interesting bit on going to sleep.
    usbhid 2-1:1.0: resume is unsafe!     [1]
ohci_hcd 0001:10:18.0: unlink after no-IRQ? Different ACPI or APIC settings may help.
    eth0: suspending....                  [same as 2.6.8]
cpufreq: resume failed to assert current frequency is what timing core thinks it is
    aty128fb: resumed!                    [matches 2.6.8 from here on]

I presume the cpufreq message is because it doesn't load the cpufreq modules. Don't know why. I also have to manually modprobe the sound modules.

Before I file a bug report, does this info help anyone pin down WHERE the problem is? (Kernel? Udev? User? CPUfreq?) I'm not currently subscribed, but I'll check the web.

Charles R. Twardy                    www.csse.monash.edu.au/~ctwardy
Monash University                    sarbayes.org
Computer Sci. & Software Eng.
+61(3) 9905 5823 (w)  5146 (fax)     Carpe data. Caveat computor.

Reply to: