2.6.20-rc3 regression: suspend to RAM broken on Mac mini Core Duo
Hi folks,
I tried 2.6.20-rc3 and suspend to RAM is now broken. The screen stays dark after resume, the same with the network link. It worked with 2.6.18 (I skipped 2.6.19 because of a regression in the sky2 driver).
I enabled pm_trace and did a echo mem > /sys/power/state in single user mode.
After the reboot, all I got from pm_trace is this:
ACPI: (supports S0 S3 S4 S5)
Magic number: 0:798:636
hash matches drivers/base/power/resume.c:46
Freeing unused kernel memory: 228k freed
This is line 46 in resume.c:
TRACE_RESUME(error);
No information about the device/driver that refuses to resume.
I think that this is a regression, as it worked with 2.6.18 and the kernel config is the same. The hardare is a Mac mini Core Duo.
Regards,
Tino
Quoted 1 line · Tino Keitel
No information about the device/driver that refuses to resume.
You should be able to identify the problematic driver by removing each driver manually before suspending.
Lee
Quoted 5 lines · Lee Revell
Quoted 1 line · Tino Keitel
No information about the device/driver that refuses to resume.
You should be able to identify the problematic driver by removing each driver manually before suspending.
I can not reproduce it anymore, resume now works. I really hope that it will stay so.
Regards,
Tino
Quoted 9 lines · Tino Keitel
Quoted 5 lines · Lee Revell
Quoted 1 line · Tino Keitel
No information about the device/driver that refuses to resume.
You should be able to identify the problematic driver by removing each driver manually before suspending.
I can not reproduce it anymore, resume now works. I really hope that it will stay so.
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
Regards,
Tino
Quoted 5 lines · Tino Keitel
Quoted 4 lines · Tino Keitel
Quoted 3 lines · Lee Revell
Quoted 1 line · Tino Keitel
No information about the device/driver that refuses to resume.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
You should be able to identify the problematic driver by removing each driver manually before suspending.
I can not reproduce it anymore, resume now works. I really hope that it will stay so.
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
Is this issue still present in -rc4?
Quoted 2 lines
Regards,
Tino
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 9 lines · Adrian Bunk
Quoted 8 lines · Tino Keitel
Quoted 7 lines · Tino Keitel
Quoted 5 lines · Lee Revell
Quoted 1 line · Tino Keitel
No information about the device/driver that refuses to resume.
You should be able to identify the problematic driver by removing each driver manually before suspending.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
I can not reproduce it anymore, resume now works. I really hope that it will stay so.
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
Is this issue still present in -rc4?
I used 2.6.20-rc4 in single user mode, and applied 2 patches from netdev to get wake on LAN support. This way I was able to set up an automatic suspend/resume loop. It looked good, but after e.g. 20 minutes, the resume hang. So it is reproduceable with 2.6.20-rc4. Unfortunately, I can not test the same with 2.6.18, as the wake on LAN patches need 2.6.20-rc.
Regards,
Tino
Quoted 11 lines
Quoted 4 lines
Quoted 2 lines
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
Is this issue still present in -rc4?
I used 2.6.20-rc4 in single user mode, and applied 2 patches from netdev to get wake on LAN support. This way I was able to set up an automatic suspend/resume loop. It looked good, but after e.g. 20 minutes, the resume hang. So it is reproduceable with 2.6.20-rc4. Unfortunately, I can not test the same with 2.6.18, as the wake on LAN patches need 2.6.20-rc.
Hmm, do you mean this is the first time of this kind of testing? Is this issue related to LAN driver?
I guess you should be able to set up an automatic suspend/resume loop with /proc/acpi/alarm, and test similar with 2.6.18.
--Luming
Quoted 12 lines · Luming Yu
Quoted 11 lines
Quoted 4 lines
Quoted 2 lines
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
Is this issue still present in -rc4?
I used 2.6.20-rc4 in single user mode, and applied 2 patches from netdev to get wake on LAN support. This way I was able to set up an automatic suspend/resume loop. It looked good, but after e.g. 20 minutes, the resume hang. So it is reproduceable with 2.6.20-rc4. Unfortunately, I can not test the same with 2.6.18, as the wake on LAN patches need 2.6.20-rc.
Quoted 4 lines
Hmm, do you mean this is the first time of this kind of testing? Is this issue related to LAN driver?
I guess you should be able to set up an automatic suspend/resume loop with/proc/acpi/alarm, and test similar with 2.6.18.
Thanks for the hint. I just used /proc/acpi/alarm to set up a suspend/resume loop and did ca. 100 cycles in a row with 2.6.18.2 in single user mode, without a failure.
Regards,
Tino
Hi!
Quoted 12 lines
Quoted 12 lines
Quoted 11 lines
Quoted 4 lines
Quoted 2 lines
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
Is this issue still present in -rc4?
I used 2.6.20-rc4 in single user mode, and applied 2 patches from netdev to get wake on LAN support. This way I was able to set up an automatic suspend/resume loop. It looked good, but after e.g. 20 minutes, the resume hang. So it is reproduceable with 2.6.20-rc4. Unfortunately, I can not test the same with 2.6.18, as the wake on LAN patches need 2.6.20-rc.
Quoted 8 lines
Quoted 4 lines
Hmm, do you mean this is the first time of this kind of testing? Is this issue related to LAN driver?
I guess you should be able to set up an automatic suspend/resume loop with/proc/acpi/alarm, and test similar with 2.6.18.Thanks for the hint. I just used
/proc/acpi/alarmto set up a suspend/resume loop and did ca. 100 cycles in a row with 2.6.18.2 in single user mode, without a failure.
Can you do similar test on 2.6.20 -- w/o network driver loaded (and generaly minimum drivers?)
Pavel
Signature · 1 line
Thanks for all the (sleeping) penguins.
Quoted 19 lines · Pavel Machek
Hi!
Quoted 17 lines
Quoted 16 lines
Quoted 11 lines
Quoted 4 lines
Quoted 2 lines
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
Is this issue still present in -rc4?
I used 2.6.20-rc4 in single user mode, and applied 2 patches from netdev to get wake on LAN support. This way I was able to set up an automatic suspend/resume loop. It looked good, but after e.g. 20 minutes, the resume hang. So it is reproduceable with 2.6.20-rc4. Unfortunately, I can not test the same with 2.6.18, as the wake on LAN patches need 2.6.20-rc.
Hmm, do you mean this is the first time of this kind of testing? Is this issue related to LAN driver?
I guess you should be able to set up an automatic suspend/resume loop with/proc/acpi/alarm, and test similar with 2.6.18.
Quoted 6 lines
Quoted 3 lines
Thanks for the hint. I just used
/proc/acpi/alarmto set up a suspend/resume loop and did ca. 100 cycles in a row with 2.6.18.2 in single user mode, without a failure.Can you do similar test on 2.6.20 -- w/o network driver loaded (and generaly minimum drivers?)
I think I found the problem. In 2.6.18, I had a slightly different config. With 2.6.20-rc4, I had sucessful suspend/resume cycles without the USB DVB-T box attached. I tweaked the USB options a bit and activated some options (CONFIG_USB_SUSPEND, CONFIG_USB_MULTITHREAD_PROBE, CONFIG_USB_EHCI_SPLIT_ISO, CONFIG_USB_EHCI_ROOT_HUB_TT, CONFIG_USB_EHCI_TT_NEWSCHED) and now I can suspend/resume without hangs. At least I haven't seen one until now.
Thanks for you patience and regards,
Tino
On Sat, Jan 13, 2007 at 04:05:28 +0100, Tino Keitel wrote:
[...]
Quoted 7 lines
I think I found the problem. In 2.6.18, I had a slightly different config. With 2.6.20-rc4, I had sucessful suspend/resume cycles without the USB DVB-T box attached. I tweaked the USB options a bit and activated some options (
CONFIG_USB_SUSPEND,CONFIG_USB_MULTITHREAD_PROBE,CONFIG_USB_EHCI_SPLIT_ISO,CONFIG_USB_EHCI_ROOT_HUB_TT,CONFIG_USB_EHCI_TT_NEWSCHED) and now I can suspend/resume without hangs. At least I haven't seen one until now.
Just after I sent the mail, I had 2 failures again. :-(
Regards,
Tino
Quoted 12 lines · Tino Keitel
On Sat, Jan 13, 2007 at 04:05:28 +0100, Tino Keitel wrote:
[...]
Quoted 7 lines
I think I found the problem. In 2.6.18, I had a slightly different config. With 2.6.20-rc4, I had sucessful suspend/resume cycles without the USB DVB-T box attached. I tweaked the USB options a bit and activated some options (
CONFIG_USB_SUSPEND,CONFIG_USB_MULTITHREAD_PROBE,CONFIG_USB_EHCI_SPLIT_ISO,CONFIG_USB_EHCI_ROOT_HUB_TT,CONFIG_USB_EHCI_TT_NEWSCHED) and now I can suspend/resume without hangs. At least I haven't seen one until now.
Quoted 1 line
Just after I sent the mail, I had 2 failures again. :-(
CONFIG_USB_MULTITHREAD_PROBE is known bad.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 12 lines · Tino Keitel
On Sat, Jan 13, 2007 at 04:05:28 +0100, Tino Keitel wrote:
[...]
Quoted 7 lines
I think I found the problem. In 2.6.18, I had a slightly different config. With 2.6.20-rc4, I had sucessful suspend/resume cycles without the USB DVB-T box attached. I tweaked the USB options a bit and activated some options (
CONFIG_USB_SUSPEND,CONFIG_USB_MULTITHREAD_PROBE,CONFIG_USB_EHCI_SPLIT_ISO,CONFIG_USB_EHCI_ROOT_HUB_TT,CONFIG_USB_EHCI_TT_NEWSCHED) and now I can suspend/resume without hangs. At least I haven't seen one until now.
Quoted 1 line
Just after I sent the mail, I had 2 failures again. :-(
PM_TRACE revealed that the Ethernet driver (sky2) failed to resume. I removed the patches for wake on LAN and hope that it works now.
Regards,
Tino
Quoted 5 lines · Tino Keitel
Quoted 4 lines · Tino Keitel
Quoted 3 lines · Lee Revell
Quoted 1 line · Tino Keitel
No information about the device/driver that refuses to resume.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
You should be able to identify the problematic driver by removing each driver manually before suspending.
I can not reproduce it anymore, resume now works. I really hope that it will stay so.
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
What was last working version? Can you pinpoint driver breaking it?
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 9 lines · Pavel Machek
Quoted 8 lines · Tino Keitel
Quoted 7 lines · Tino Keitel
Quoted 5 lines · Lee Revell
Quoted 1 line · Tino Keitel
No information about the device/driver that refuses to resume.
You should be able to identify the problematic driver by removing each driver manually before suspending.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
I can not reproduce it anymore, resume now works. I really hope that it will stay so.
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
What was last working version? Can you pinpoint driver breaking it?
I just used 2.6.18.2 with a manual driven suspend/resume loop and fully loaded userspace for ca. 40 minutes, without a failure.
I tried to pinpoint the driver with pm_trace, without success (see my original posting).
Regards,
Tino
Quoted 16 lines · Tino Keitel
Quoted 15 lines · Pavel Machek
Quoted 13 lines · Tino Keitel
Quoted 9 lines · Tino Keitel
Quoted 5 lines · Lee Revell
Quoted 1 line · Tino Keitel
No information about the device/driver that refuses to resume.
You should be able to identify the problematic driver by removing each driver manually before suspending.
I can not reproduce it anymore, resume now works. I really hope that it will stay so.
It didn't. It looks like it is unusable, becuase it isn't reliable in 2.6.20-rc3.
Quoted 7 lines
Quoted 1 line
What was last working version? Can you pinpoint driver breaking it?
I just used 2.6.18.2 with a manual driven suspend/resume loop and fully loaded userspace for ca. 40 minutes, without a failure.
I tried to pinpoint the driver with
pm_trace, without success (see my original posting).
Could you please verify if the issue is reproducible when you boot with init=/bin/bash and suspend with the minimal list of modules loaded?
Rafael
Signature · 3 lines
If you don't have the time to read, you don't have the time or the tools to write. - Stephen King