Power Management Update
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hello,
I have been testing swsusp to disk on my computer using kernel 2.6.0-test4 + Patrick Mochel's main PM patch (posted on lkml on aug 31) + IDE PM fix from benh (posted on lkml by P. Mochel on sep 2)
I found that my computer is able to suspend to disk if I boot with init=/bin/sh, but not with a normal boot. I tried swsusp with a normal boot (Xfree, kde, ...) but after removing several modules form /lib/modules, to see which modules make problems. What I found:
* swsusp doesn't like accelerated graphics. If the following modules are loaded:
i830 68120 20
intel_agp 14744 1
agpgart 25640 3 intel_agpresuming fails. (Different kind of failures, from spontaneous reboot to kernel panic.) I could try to pinpoint more precisely which module causes trouble.
* Apart from that, the computer can suspend and come back to life ! Modules loaded:
snd_mixer_oss 16768 3
binfmt_misc 8200 1
autofs 12928 0
ne2k_pci 8288 0
8390 8576 1 ne2k_pci
snd_virmidi 3584 2
snd_seq_virmidi 5632 1 snd_virmidi
ipchains 48080 15
ide_cd 36736 0
cdrom 33312 1 ide_cd
loop 13192 14
hid 30272 0
ehci_hcd 21120 0
uhci_hcd 27656 0
usbcore 91348 5 hid,ehci_hcd,uhci_hcd However, the mouse is not working anymore (mouse is usb, the only usb
device connected) nor network on eth1 (I haven't tried eth0.)
Here are the last lines of the log after resuming:
Restarting tasks...<6>usb 1-1: USB disconnect, address 2 done
PM: Removing info for usb:1-1:0
PM: Removing info for usb:1-1
hub 1-0:0: debounce: port 1: delay 100ms stable 4 status 0x301
eth1: mismatched read page pointers 3c vs 66.
eth1: mismatched read page pointers 4c vs d7.
eth1: mismatched read page pointers 4c vs d7.
eth1: mismatched read page pointers 4c vs d7.
eth1: mismatched read page pointers 4c vs d7.
eth1: mismatched read page pointers 4c vs d7.
eth1: mismatched read page pointers 4c vs d7.
eth1: mismatched read page pointers 4c vs d7.
eth1: mismatched read page pointers 4c vs d7.
hub 1-0:0: new USB device on port 1, assigned address 3
usb 1-1: control timeout on ep0out
eth1 is
01:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 20
Region 0: I/O ports at c800 [size=32]
A last point; lates patch from P. Mochel (posted on Sep 3, supposed to fix configuration with preempt enabled) completely prevents me from suspending to disk.
Many data on my computer (.config, lspci, dsdt) available on
http://perso.nerim.net/~tudia/bug-reports/
Éric Brunet
Quoted 9 lines
I have been testing swsusp to disk on my computer using kernel 2.6.0-test4 + Patrick Mochel's main PM patch (posted on lkml on aug 31) + IDE PM fix from benh (posted on lkml by P. Mochel on sep 2)
I found that my computer is able to suspend to disk if I boot with init=/bin/sh, but not with a normal boot. I tried swsusp with a normal boot (Xfree, kde, ...) but after removing several modules form
/lib/modules, to see which modules make problems. What I found:
Wow. Thanks a lot for taking the time to test this.
Quoted 8 lines
* swsusp doesn't like accelerated graphics. If the following modules are loaded:
i830 68120 20 intel_agp 14744 1 agpgart 25640 3 intel_agpresuming fails. (Different kind of failures, from spontaneous reboot to kernel panic.) I could try to pinpoint more precisely which module causes trouble.
This is not suprising, and likely something that many people will run into. There is a lot of driver work that needs to be done, especially WRT video devices, as many of them are not tied into the new driver model at all.
For now, the best I can say is to manually unload those modules before suspending and reloading them after resume. We'll work on getting the drivers fixed up, but it will probably take a while.
Quoted 17 lines
* Apart from that, the computer can suspend and come back to life ! Modules loaded:
snd_mixer_oss 16768 3 binfmt_misc 8200 1 autofs 12928 0 ne2k_pci 8288 0 8390 8576 1 ne2k_pci snd_virmidi 3584 2 snd_seq_virmidi 5632 1 snd_virmidi ipchains 48080 15 ide_cd 36736 0 cdrom 33312 1 ide_cd loop 13192 14 hid 30272 0 ehci_hcd 21120 0 uhci_hcd 27656 0 usbcore 91348 5 hid,ehci_hcd,uhci_hcd
Quoted 2 lines
However, the mouse is not working anymore (mouse is usb, the only usb device connected) nor network on eth1 (I haven't tried eth0.)
For both the mouse and eth1, will they work if you unload the modules first, and reload them after resuming?
Thanks,
Pat
Quoted 11 lines · Patrick Mochel
Quoted 6 lines
* swsusp doesn't like accelerated graphics. If the following modules are loaded:
i830 68120 20 intel_agp 14744 1 agpgart 25640 3 intel_agpresuming fails. (Different kind of failures, from spontaneous reboot to
This is not suprising, and likely something that many people will run into. There is a lot of driver work that needs to be done, especially WRT video devices, as many of them are not tied into the new driver model at all.
If you want more testers and interesting bug reports, that should be some kinfd of priority, no ? Everybody is running with accelerated graphics modules, nowadays.
Quoted 10 lines
For now, the best I can say is to manually unload those modules before suspending and reloading them after resume. We'll work on getting the drivers fixed up, but it will probably take a while.
Quoted 2 lines
However, the mouse is not working anymore (mouse is usb, the only usb device connected) nor network on eth1 (I haven't tried eth0.)
For both the mouse and eth1, will they work if you unload the modules first, and reload them after resuming?
Ok, I tried this: after a normal boot, I went back to runlevel 3, ifconfig'ed down eth1, unloaded modules i830, hid, ehci-hcd, uhcd-hcd ne2K-pci and 8390 and echoed 4 to /proc/sleep/acpi. Note that intel_agp, agpgart and usbcore were still there, those modules can't be removed once loaded.
The system suspended and resumed correctly.
I ifconfig'ed up eth1 (which loaded automagically the two modules), and network was working. I loaded hid, ehci-hcd and uhcd-hcd, and mouse was working. I telinit'ed 5, X started, went back to runlevel 3 to load i830 which I had forgotten, went back again to runlevel 5. X was working fine, and video acceleration too. (I think I saw a little glitch on screen; a little gray line, there, that diseapeared quickly.)
Then I tried to pinpoint more precisely what was wrong. Back to telinit
3. ifconfig down eth1, but keep the modules loaded. rmmod i830, hid, but keep ehci-hcd and uhci-hcd. I expected that, at least, the computer would suspend and resume, and I wanted to see if I could recover my mouse and network interface. I got a black screen at suspend time, and had to reboot with magic sysrq. I thought that the computer wouldn't suspend twice in a row.
After a clean boot, I tried again my latest experiment: telinit 3, rmmod i830, rmmod hid, ifconfig eth1 down, echo 4 > /proc/acpi/sleep. As I said, the computer should be able to suspend/resume in that configuration. This time, it failed at resuming. Beautifull kernel panic, tried to kill init, etc.
It isn't logical. To sum up:
agpgart i830 hid+uhci+ehci eth1 | suspend+resume
+intel_agp |
----------------------------------------------------------+--
unloaded unloaded loaded loaded+up | works but
| mouse+eth1 fail
loaded unloaded unloaded unloaded | works and
| mouse+eth1 can be | recovered
loaded unloaded partially loaded | does not work.
loaded but down
What this probably means is that one of my succes was a piece of luck, non reliably reproducible. Unfortunately, my wife came back from her trip, and I now have much less time for testing...
If, anyway, I decide to try test5, what patches should be applied ?
Éric
Quoted 8 lines · Éric Brunet
Quoted 7 lines · Patrick Mochel
Quoted 6 lines
* swsusp doesn't like accelerated graphics. If the following modules are loaded:
i830 68120 20 intel_agp 14744 1 agpgart 25640 3 intel_agpresuming fails. (Different kind of failures, from spontaneous reboot to
Quoted 8 lines
Quoted 4 lines
This is not suprising, and likely something that many people will run into. There is a lot of driver work that needs to be done, especially WRT video devices, as many of them are not tied into the new driver model at all.
If you want more testers and interesting bug reports, that should be some kinfd of priority, no ? Everybody is running with accelerated graphics modules, nowadays.
It is a priority, but they pose a stiff challenge that not many know how to resolve, including yours truly. We'll get there..
Quoted 10 lines
agpgart i830 hid+uhci+ehci eth1 | suspend+resume
+intel_agp |
----------------------------------------------------------+--
unloaded unloaded loaded loaded+up | works but
| mouse+eth1 failloaded unloaded unloaded unloaded | works and
| mouse+eth1 can be | recovered
Quoted 6 lines
loaded unloaded partially loaded | does not work.
loaded but downWhat this probably means is that one of my succes was a piece of luck, non reliably reproducible. Unfortunately, my wife came back from her trip, and I now have much less time for testing...
Heh, thanks for testing this so far. This is definitely helpful in pointing out some trouble areas.
Pat