On Mon, 29 Mar 2010, Justin Piszcz wrote: > bus pci, device 0000:00:0b.0 > OHCI Host Controller > ohci_hcd > OHCI 1.0, NO legacy support registers > control 0x68f RWE RWC HCFS=operational IE PLE CBSR=3 > cmdstatus 0x00000 SOC=0 > intrstatus 0x00000020 FNO > intrenable 0x8000004e MIE RHSC RD SF WDH > ed_controlhead 7bef1b90 > hcca frame 0x4657 > fmintvl 0xa7782edf FIT FSMPS=0xa778 FI=0x2edf > fmremaining 0x80002b76 FRT FR=0x2b76 > periodicstart 0x2a2f > lsthresh 0x0628 > hub poll timer off > roothub.a 01000208 POTPGT=1 NPS NDP=8(8) > roothub.b 00000000 PPCM=0000 DR=0000 > roothub.status 00008000 DRWE > roothub.portstatus [0] 0x00000100 PPS > roothub.portstatus [1] 0x00000100 PPS > roothub.portstatus [2] 0x00000100 PPS > roothub.portstatus [3] 0x00000100 PPS > roothub.portstatus [4] 0x00000303 LSDA PPS PES CCS > roothub.portstatus [5] 0x00000303 LSDA PPS PES CCS > roothub.portstatus [6] 0x00000100 PPS > roothub.portstatus [7] 0x00000100 PPS I don't notice anything suspicious there. > > At the same time, just to be increase my level of certainty, you should > > apply the following debugging patch for ohci-hcd. Let's see both the > > usbmon trace and the dmesg log for the same event. The trace and the > > debugging patch will generate plenty of output during normal operation, > > but don't worry about that. Only the part starting from shortly before > > the mouse quits really matters. > Yes, I've done this before for a bug in the Intel USB controller (P55) on > another motherboard.. Should be doable, always funny though how it does not > happen when you are trying to make it happen. > > For your patch, what does this patch against? It does not apply cleanly > for 2.6.33. Yes it does. Maybe there's something wrong with the way your email client extracted the patch from the message. > It also fails against 2.6.34-rc2, can you diff -u and show the patch so > I can patch manually or include a patch against 2.6.33 or 2.6.34-rc2? That _was_ a "diff -u"-style patch. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
