Messages in this thread | | | Date | Fri, 18 Apr 2008 11:42:21 +0200 | From | Pavel Machek <> | Subject | Re: 2.6.25-mm1: not looking good |
| |
On Fri 2008-04-18 00:53:23, Andrew Morton wrote: > On Fri, 18 Apr 2008 00:50:34 -0700 Andrew Morton <akpm@linux-foundation.org> wrote: > > > dmesg: http://userweb.kernel.org/~akpm/x.txt > > config: http://userweb.kernel.org/~akpm/config-t61p.txt > > oop, there's more: > > > sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > firewire_core: created device fw0: GUID 00016c2000174bad, S400 > PM: Device usb4 failed to restore: error -113 > eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX > eth0: 10/100 speed: disabling TSO > PM: Device usb5 failed to restore: error -113 > PM: Device usb7 failed to restore: error -113 > sd 0:0:0:0: [sda] Starting disk > PM: Image restored successfully. > Restarting tasks ... done. > PM: Basic memory bitmaps freed > > Those USB restore failures are new. They're similar to the ones on the > doesnt-resume-properly-any-more Vaio. They came out from the machine's > second (successful) resume-from-disk.
Try rmmod usb / insmod usb around suspend to see if it is usb-specific, or if something went seriously wrong in core.
Or you might just bisect it ;-). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
| |