On Wed, 22 Nov 2006, Matt Price wrote: > Hi, > > i run a basically ubuntu-edgy system with a custom kernel, 2.6.18 based > on debian sources but patched with the suspend2 patches and with one > external module (ipw3945) added in. > > For about a month everything worked fine with this kernel. However 7 or > 8 days ago, I stopped being able to hibernate the system (it's a laptop, > so that's a drag). I hibernate using the hibernate package and the > suspend2 capabilities built in to the kernel. > > anyway, the error message from suspend2 reads: > > [ 5.812000] usb 5-2.3: new full speed USB device using ehci_hcd and > address 4
This looks like you plugged a full-speed device into a high-speed hub just as the computer was trying to shut down. > [ 5.812000] CPU1 is down > [ 5.956000] usb 5-2.3: configuration #1 chosen from 1 choice > [ 5.960000] suspend_device(): usb_generic_suspend+0x0/0x120 > [usbcore]() returns -16 > [ 5.960000] Could not suspend device 5-2: error -16 > [ 5.980000] Some devices failed to suspend > [ 5.980000] ------------[ cut here ]------------ > [ 5.980000] kernel BUG at kernel/power/atomic_copy.c:496! > [ 5.980000] invalid opcode: 0000 [#1] > [ 5.980000] SMP > > not sure this helps you very much, but something is happening with a > usb-related device that doesn't allow the hibernation resume to be > completed properly. > > To confirm that usb was the underlying issue, I built an identical > kernel with no usb support and found t suspends and resumes fine. > > now for the odd part: this problem showed up after many successsful > cycles suspending & resuming this machine flawlessly. No usb devices > have been attached to it for some time. Also I can suspend to ram > without any trouble (unfortunately, my battery sucks and I really need > to use suspend 2 disk in many circumstances). My uninformed guess is > that at some point something happened to one of the internal usb devices > that set some variable in a persistent way that interferes with > suspend2. but what could it be? > > I should also say that I have been trying to unload usbcore in order to > suspend, but am unable to do it, even after umounting /proc/bus/usb/. > In order to umount, though , I need to add the "-l" switch, which may > account for my trouble. Could be that some process like hald is holding the directory open. Did you remember to rmmod ohci-hcd and usb-storage? > so, sorry if that's not especially coherent. very grateful for any > ideas on how to proceed! Turn on CONFIG_USB_DEBUG and see what shows up in the kernel log. 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-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
