linux-kernel - Re: Resume after hibernation regression in 2.6.29

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20090327043546.EB310B9@cardinal.lizella.net>
Date:	Fri, 27 Mar 2009 04:35:46 +0000
From:	rworkman@...dinal.lizella.net (Robby Workman)
To:	"Tvrtko A. Ursulin" <tvrtko@...ulin.net>
Cc:	pavel@....cz, linux-kernel@...r.kernel.org
Subject: Re: Resume after hibernation regression in 2.6.29

In linux.kernel, you wrote:
> On Thursday 26 March 2009 20:18:40 Pavel Machek wrote:
>> On Thu 2009-03-26 19:20:32, Tvrtko A. Ursulin wrote:
>> > 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.
>>
>> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/