vasos wrote: > > Hello, > > i wish to report a strange issue that my machine experiences with a > NEC USB 3.0 PCI-Express (x1 slot) controller. Normally the controller > uses the xhci (usb3) kernel driver. > Now the machine is running > > Linux xxxx 2.6.35.4 #2 SMP Wed Sep 1 10:15:04 UTC 2010 x86_64 GNU/Linux > > Note that this issue was present in 2.6.34 and 2.6.33 but i though that > it might get fixed in the meantime. > > > > The issue > ---------- > The controller is sometimes detected and some times not. I mean that at > some boots it > is present as a PCI device (listed in pci -v as > 05:00.0 USB Controller: NEC Corporation Device 0194 (rev 03) (prog-if 30) > Flags: bus master, fast devsel, latency 0, IRQ 16 > Memory at febfe000 (64-bit, non-prefetchable) [size=8K] > Capabilities: [50] Power Management version 3 > Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+ > Capabilities: [90] MSI-X: Enable- Count=8 Masked- > Capabilities: [a0] Express Endpoint, MSI 00 > Capabilities: [100] Advanced Error Reporting > Capabilities: [140] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff > Capabilities: [150] #18 > Kernel driver in use: xhci_hcd > ) > > and some other times it just does not exist. > Maybe it is PCIe express related. Also people on linux-usb mailing list > suggested this. > I include 2 full dmesg logs ziped due to the size as well a unified diff > of them. > > NOTE that "echo 1> /sys/bus/pci/rescan" does not do anything. > > > Please cc the replies if any to the sender email (noxelia ...) > > Is this x1 device in a x4 (or higher xN) slot? I've seen x4 slots not lane-(width) sync with x1 NICs in some systems (even though the PCIe spec says it should), esp. if one resets the device after boot (i.e., flr reset). If so, try the card in a x1 slot & see if the problem goes away. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
