On Fri, 12 Jan 2007, Vasudevan S wrote: > > > If I just restart the machine instead of shutdown, I see one more usb > > > error: > > > usb 5-1.2: device descriptor read/64, error -32 > > > > > > which would appear like some reset/close operation wasn't done in the > > > restart. > > > > Again, if the message appears only once then you can ignore it. Restart > > does re-initialize all USB devices. > > Restart still shows this 'device descriptor' error, though.
It appears that the device itself is failing to initialize correctly. It's hard to say anything more definite since you haven't provided any more log messages. > > The 'suspend-to-disk' (using 'swsusp'/'software suspend 2') are not > > > working on this laptop and I am thinking these errors might be > > > contributing to the problem. > > > > I doubt that very much. But if you want anybody to help solve the swsusp > > problem then you have to post a dmesg log showing what goes wrong when you > > try to do it. > > Ok, you may be right here as well. > > When I start the hibernation using 'swsusp', I see the following > messages on the console: > [ I cannot paste the contents to a file when this happens, so sending > excerpts..] > > [I have also enabled the PM debug messages in the config] > " > Shrinking memory > swsusp: Need to copy 108345 pages > swsusp: critical region/: done (108345 pages copied) > swsusp: Restoring Highmem > > PCI: Enabling device 0000:00:1d.7 (0000 -> 0002) > usb usb1: root hub lost power or was reset > usbdev1.2_ep00: PM: resume from 0, parent 1-1 still 1 > > [followed by the similar usb messages, but for different hubs] > " Those messages are normal. They indicate that the USB controllers weren't powered while the machine was shut off. > Today, I decided to wait for some time after seeing these messages. > Then the console started spitting the following messages: > " > sd 0:0:0:0: timing out command, waited 360s > end_request: I/O error, dev sda, sector 152121693 > Read-error on swap-device (253:1:24) > " > > So, it may not really be the 'usb' problem, but rather something to do > with this 'sd' driver or even the sata driver.? I would assume it has something to do with SATA, which is a lot newer than sd. > Also, when I try to power down the box when this happens, I also see > an ACPI error: > > ACPI error (evevent-0314): No installed handler for fixed event > [00000002] [20060707] > > Perhaps, I should forward all this to the 'linux-kernel' list? Since none of your problems appear to be related to the USB stack, that seems like a good idea. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
