On Saturday 08 January 2005 12:09 pm, Alan Stern wrote:
> Time to go look at those logs again...
Another complication here is that a serial console will give a much more
complete set of logs than "dmesg" after swsusp resumes ... below, I
summarize log contents, with CAPS SHOWING WHAT DMESG WILL OMIT:
boot
swsusp suspend
SWSUSP MESSAGES AFTER IMAGE WAS WRITTEN
(RE)BOOT
SWSUSP MESSAGES SWITCHING TO OLD IMAGE
swsusp resume
I've certainly found cases where the the "MISSING LOG DATA" had some
information that was essential to figuring things out. But then, it's
also true that I found Linux sometimes inconveniently "forgot" that
it was supposed to be using a serial console at some point in that
sequence ... so I've had to debug swsusp resume problems with two
sets of logs, serial console and dmesg.
- Dave
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
