Skip to contentSkip to conversation

Resume after hibernation regression in 2.6.29

DISCUSSION Robby Workman 1 participant 1 message Mar 27, 2009 3 messages not in the archive

lore
Share & tools
lore
#3 lore raw
In reply to a message not in the archive
Quoted 21 lines · you
Quoted 20 lines · On Thursday 26 March 2009 20:18:40 Pavel Machek wrote:
Quoted 18 lines · Tvrtko A. Ursulin

Hi guys,
I have been running custom compiled 2.6.28.7 in OpenSUSE 11.1 and using hiberation/resume daily as configured by the distro. Yesterday I upgraded to 2.6.29 (make oldconfig from 2.6.28.7, attached) and after resume networking (at least) does not work. Reboot at this point takes very long because of timeouts on CIFS and whatelse.

Below is how /var/log/messagess looks for one cycle (hibernate-resume-reboot) and I am also attaching kernel config and /var/log/pm-suspend.log.

You will probably notice evil nvidia.ko in there but don't panic, it all happens without it as well. Tested from runlevel 3 and by running pm-hibernate. After resume from that NIC LEDs were off. I tried /etc/init.d/network restart but that hung so I ^C and tried rmmod forcedeth && modprobe forcedeth && ifup eth0 and after some time network went live again. Haven't had time to test further though, so this is all pretty rough.

Quoted 7 lines
Quoted 2 lines

Ok, can you try to rmmod forcedeth before hibernation, then insmod it after resume?

Sure, after insmod and /etc/init.d/network start following resume network was fine. Guess I could kludge that sequence into pm scripts somehow but would rather avoid that since it slows down the cycle and would make scripts non-stock.

No need to modify the system pm scripts; it has support for this sort of thing built-in. Create /etc/pm/config.d/defaults with this line:
SUSPEND_MODULES="forcedeth"

Obviously this is just a workaround until a real fix goes into the kernel, but it should do what you need for now.

-RW