Re: Resume after hibernation regression in 2.6.29

[Pavel Machek]

On Thu 2009-03-26 20:55:23, Tvrtko A. Ursulin 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.

Ok, I guess you need to talk to forcedeth maintainers then... sounds
like a forcedeth problem to me.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/