> > [ 77.734791] usb_hcd_poll_rh_status start > > [ 77.786476] usb_hcd_poll_rh_status: uses_new_polling=1, status_urb=fffff8006e1778c0 > > [ 77.888373] usb_hcd_poll_rh_status before hub_status_data > > [ 77.959314] ohci_hub_status_data before spin_lock_irqsave > > [ 78.030299] ohci_hub_status_data after spin_lock_irqsave > > [ 78.100117] ohci_hub_status_data return > > [ 78.150496] usb_hcd_poll_rh_status after hub_status_data > > At first glance there's nothing wrong. But looking more closely, it's > obvious that the time values are extremely peculiar. > > For example, look at the time difference between the "start" line and > the "uses_new_polling" line. Those are practically adjacent in your > code, right? How could there possibly be a gap of 50 ms between the > two? Your CPU isn't running at a clock speed of 0.1 MHz, is it? > Could something be monopolizing the PCI or memory bus beyond all > reasonable bounds? It might be the 9600 baud serial console that I'm using to get these messages. Should I just remove most of the debugging printks and see if it works? -- Meelis Roos (mroos@xxxxx) http://www.cs.ut.ee/~mroos/ -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
