On Wed, 22 Nov 2006, Matt Price wrote: > > Turn on CONFIG_USB_DEBUG and see what shows up in the kernel log. > > > so I've done that and theaoutput is very verbose as you doubtless > expected. much of it is uninterpretable to me I'm afraid. This is what > I think is the relevant part, covering a period in the boot process > roughly similar to what I described in my last post:
This log is from when you are booting? What point is there in doing a suspend (or hibernate) as part of the boot procedure? Or is this from the resume following a successful suspend? What happens before this in the log? Doesn't the suspend (or resume) procedure begin by freezing all your threads? Maybe you should try using swsusp instead of suspend2. > [ 5.788000] Suspend2 2.2.8: Resuming enabled. > [ 5.788000] Failed to launch userspace program > '/usr/bin/suspend2ui_text': Error -1 > [ 5.788000] Launch userspace program failed. > [ 5.808000] hub 1-0:1.0: debounce: port 3: total 100ms stable 100ms > status 0x501 > [ 5.824000] Reading kernel & process data... > [ 5.864000] ehci_hcd 0000:00:1d.7: port 3 full speed --> companion > [ 5.864000] ehci_hcd 0000:00:1d.7: GetStatus port 3 status 003801 > POWER OWNER sig=j CONNECT > [ 5.864000] hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0004 > [ 5.864000] uhci_hcd 0000:00:1d.0: port 2 portsc 0082,00 > [ 5.864000] hub 2-0:1.0: port 2, status 0100, change 0001, 12 Mb/s > [ 5.868000] ehci_hcd 0000:00:1d.7: fatal command 010011 (park)=0 > ithresh=1 Periodic period=1024 RUN > [ 5.868000] ehci_hcd 0000:00:1d.7: fatal status 6000 Periodic Recl It's not clear exactly what these errors mean -- at least not to me -- but they don't look good. You might want to see what happens if you avoid loading ehci-hcd, or rmmod it before starting the suspend. > [ 5.992000] hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms > status 0x100 > [ 5.992000] hub 3-0:1.0: state 7 ports 2 chg 0000 evt 0002 > [ 5.992000] uhci_hcd 0000:00:1d.1: port 1 portsc 009b,00 > [ 5.992000] hub 3-0:1.0: port 1, status 0101, change 0003, 12 Mb/s > [ 6.040000] 20%...<7>hub 3-0:1.0: debounce: port 1: total 100ms > stable 100ms status 0x101 > [ 6.180000] 40%...<6>usb 3-1: new full speed USB device using > uhci_hcd and address 2 > [ 6.308000] 60%...<7>usb 3-1: ep0 maxpacket = 8 > [ 6.384000] usb 3-1: new device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 6.384000] usb 3-1: uevent > [ 6.384000] usb 3-1: configuration #1 chosen from 1 choice > [ 6.388000] usb 3-1: adding 3-1:1.0 (config #1, interface 0) > [ 6.388000] usb 3-1:1.0: uevent > [ 6.388000] hub 3-1:1.0: usb_probe_interface > [ 6.388000] hub 3-1:1.0: usb_probe_interface - got id > [ 6.388000] hub 3-1:1.0: USB hub found > [ 6.388000] hub 3-1:1.0: 3 ports detected > [ 6.388000] hub 3-1:1.0: compound device; port removable status: RFR > [ 6.388000] hub 3-1:1.0: individual port power switching > [ 6.388000] hub 3-1:1.0: individual port over-current protection > [ 6.388000] hub 3-1:1.0: power on to power good time: 100ms > [ 6.392000] hub 3-1:1.0: hub controller current requirement: 100mA > [ 6.392000] hub 3-1:1.0: 100mA bus power budget for each child > [ 6.392000] hub 3-1:1.0: enabling power on all ports > [ 6.420000] 80%...<7>drivers/usb/core/inode.c: creating file '002' > [ 6.500000] hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0000 > [ 6.500000] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 6.500000] hub 5-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 6.500000] hub 1-2:1.0: state 7 ports 4 chg 0000 evt 0008 > [ 6.500000] hub 1-2:1.0: port 3, status 0101, change 0001, 12 Mb/s > [ 6.520000] usb usb4: suspend_rh (auto-stop) > [ 6.568000] 100%...done. > [ 6.624000] usb usb5: suspend_rh (auto-stop) > [ 6.628000] hub 1-2:1.0: debounce: port 3: total 100ms stable 100ms > status 0x101 > [ 6.700000] usb 1-2.3: new full speed USB device using ehci_hcd and > address 4 > [ 6.720000] hub 1-2:1.0: port 3 not reset yet, waiting 10ms > [ 6.844000] usb 1-2.3: skipped 1 descriptor after interface > [ 6.844000] usb 1-2.3: new device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 6.844000] usb 1-2.3: uevent > [ 6.844000] usb 1-2.3: configuration #1 chosen from 1 choice > [ 6.844000] usb 1-2.3: adding 1-2.3:1.0 (config #1, interface 0) > [ 6.844000] usb 1-2.3:1.0: uevent > [ 6.844000] usb 1-2.3: adding 1-2.3:1.1 (config #1, interface 1) > [ 6.844000] usb 1-2.3:1.1: uevent > [ 6.844000] usb 1-2.3: adding 1-2.3:1.2 (config #1, interface 2) > [ 6.844000] usb 1-2.3:1.2: uevent > [ 6.844000] drivers/usb/core/inode.c: creating file '004' > [ 6.844000] hub 3-1:1.0: state 7 ports 3 chg 0000 evt 0004 > [ 6.848000] hub 3-1:1.0: port 2, status 0101, change 0001, 12 Mb/s > [ 6.888000] Atomic restore preparation > [ 6.892000] Freezing cpus ... > [ 6.952000] ieee1394: Host added: ID:BUS[0-00:1023] > GUID[374fc00018700941] > [ 6.980000] hub 3-1:1.0: debounce: port 2: total 100ms stable 100ms > status 0x101 > [ 7.008000] CPU 1 is now offline > [ 7.008000] SMP alternatives: switching to UP code > [ 7.020000] CPU1 is down > [ 7.020000] usbdev1.4_ep83: PM: suspend 0->1, parent 1-2.3:1.1 > already 1 > [ 7.020000] usbdev1.4_ep03: PM: suspend 0->1, parent 1-2.3:1.1 > already 1 > [ 7.020000] usbdev1.4_ep82: PM: suspend 0->1, parent 1-2.3:1.0 > already 1 > [ 7.020000] usbdev1.4_ep02: PM: suspend 0->1, parent 1-2.3:1.0 > already 1 > [ 7.020000] usbdev1.4_ep81: PM: suspend 0->1, parent 1-2.3:1.0 > already 1 > [ 7.024000] usb 1-2.3: usb suspend > [ 7.052000] usb 3-1.2: new full speed USB device using uhci_hcd and > address 3 This shouldn't happen. It's probably suspend2's fault. That last message was sent by khubd, which is supposed to be frozen in preparation for the upcoming suspend or restore. As it is you've got new USB devices being detected while others are being suspended -- not a good combination. > [ 7.068000] usb usb2: suspend_rh (auto-stop) > [ 7.160000] usb 3-1.2: skipped 1 descriptor after endpoint > [ 7.164000] usb 3-1.2: default language 0x0409 > [ 7.172000] usb 3-1.2: new device strings: Mfr=1, Product=2, > SerialNumber=0 > [ 7.172000] usb 3-1.2: Product: O2Micro CCID SC Reader > [ 7.172000] usb 3-1.2: Manufacturer: O2 > [ 7.172000] usb 3-1.2: uevent > [ 7.172000] usb 3-1.2: configuration #1 chosen from 1 choice > [ 7.176000] usb 3-1.2: adding 3-1.2:1.0 (config #1, interface 0) > [ 7.176000] usb 3-1.2:1.0: uevent > [ 7.176000] drivers/usb/core/inode.c: creating file '003' > [ 7.176000] hub 3-1:1.0: 400mA power budget left > [ 7.176000] hub 3-1:1.0: state 7 ports 3 chg 0000 evt 0004 > [ 7.176000] suspend_device(): usb_generic_suspend+0x0/0x120 > [usbcore]() returns -16 > [ 7.176000] Could not suspend device 3-1: error -16 Of course it couldn't be suspended, not with a new unsuspended device just created beneath it. > ----------------------------------- > some of the stuff at the end is from suspend2 I guess. I see a bunch of > references to usb 3-1 and 3-1.2 -- are these the culprits? If so, 3-1.2 > seems to be just the smartcard reader which I don't use at all. can I > somehow blacklist the device? and if this is the culprit is there any > way to figure out WHY it would suddenly and unpredictably get all > screwed up when the device has never been used at all? The devices aren't the culprits. Although it's hard to tell what's really going on here, it sure looks like suspend2 is doing things it shouldn't be. 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
