On Wednesday, 7 February 2007 15:28, Jeremie Bouttier wrote:
> Rafael J. Wysocki a écrit :
> > You can try to figure out which one by booting into runlevel 2 and unloading
> > 1/2 of the modules. Then you run s2ram twice and if it works, the offending
> > module is in the unloaded half. Then, you can narrow it down by loading 1/2
> > of the modules you previously unloaded etc.
>
> Thanks for your suggestion. I booted in single-user mode and tried
> unloading half of the modules, then reloading them back progressively.
> To my great surprise, s2ram was still working when I had reloaded back
> all the modules. It turns out that the condition for the bug to occur
> seems to be that eth0 is up. If I boot in single-user mode, then s2ram
> twice, system does not resume. If I boot in single-user mode, then
> "ifconfig eth0 down" (eth0 is up by default), then I can s2ram
> indefinitely. Under X, things are a bit more tricky since I use
> NetworkManager with its KDE applet, which enjoys reactivating eth0 in my
> back. But basically, can I conclude to a bug in the Ethernet driver ?
> (module tg3, BCM5752)
Yes. Please open a kernel bugzilla entry for the problem and put all of the
relevant information in there (please add [EMAIL PROTECTED] to the entry's Cc
list).
As a workaround, you can try to unload the offending module every time before
the suspend.
Greetings,
Rafael
--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Suspend-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/suspend-devel
