On Thu, 22 Nov 2007, Kirill A. Shutemov wrote: > > > uhci_hcd 0000:00:1d.3: UHCI Host Controller > > > uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4 > > > uhci_hcd 0000:00:1d.3: irq 7, io base 0x0000bf20 > > > usb usb4: configuration #1 chosen from 1 choice > > > hub 4-0:1.0: USB hub found > > > hub 4-0:1.0: 2 ports detected > > > usb usb4: new device found, idVendor=0000, idProduct=0000 > > > usb usb4: new device strings: Mfr=3, Product=2, SerialNumber=1 > > > usb usb4: Product: UHCI Host Controller > > > usb usb4: Manufacturer: Linux 2.6.24-kas-alt1 uhci_hcd > > > usb usb4: SerialNumber: 0000:00:1d.3 > > > uhci_hcd 0000:00:1d.3: FGR not stopped yet! > > > > > > > I've had some strangenesses with USB lately. Sometimes running `lsusb' > > makes the USB system notice a newly attached device. > > No. But I have new messages in dmesg: > > uhci_hcd 0000:00:1d.3: FGR not stopped yet! > uhci_hcd 0000:00:1d.2: FGR not stopped yet! > uhci_hcd 0000:00:1d.1: FGR not stopped yet! > uhci_hcd 0000:00:1d.0: FGR not stopped yet! > > > > Is that "FGR not stopped yet!" messgae new behaviour? > > It is a new message since 2.6.24-rc3. I have never try -mm tree before.
These messages could indicate a timing problem. You can see the code that writes the messages near the end of wakeup_rh() in drivers/usb/host/uhci-hcd.c. The message gets written if the controller hardware hasn't turned off a particular bit after a 4-us delay. If the udelay() function wasn't working right, it could cause this problem. Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/