On Mon, Mar 11, 2013 at 05:04:05PM -0700, Stephen Hemminger wrote: > On Mon, 11 Mar 2013 14:48:01 -0700 > Sarah Sharp <sarah.a.sh...@linux.intel.com> wrote: > > > On Sun, Mar 10, 2013 at 12:04:40PM -0700, Stephen Hemminger wrote: > > > My test kernel is screaming with xHCI messages into kernel log. > > > [ 76.117016] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 1 ep 0 with > > > no TDs queued? > > > > > > > > > This is using kernel based on net-next which is based on 3.9.0-rc1. > > > > Please send `sudo lspci -vvv -n` output as well. > > > > Do you have any USB devices that have auto-suspend turned on? I'm aware > > that the message above gets printed when a device auto-suspends, and it > > really shouldn't in that case. > > > > Sarah Sharp > > I don't explicitly turn on auto-suspend, but maybe some sysctl is doing it > (powertop?).
Well, let's find out. Can you please run the following command as root? for f in /sys/bus/usb/devices/*; do if [ -e $f/power/control ]; then echo "Filename: $f"; cat "$f/power/control"; fi done > 00:14.0 0c03: 8086:1e31 (rev 04) (prog-if 30 [XHCI]) > Subsystem: 1043:84ca > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin A routed to IRQ 44 > Region 0: Memory at f7d00000 (64-bit, non-prefetchable) [size=64K] > Capabilities: [70] Power Management version 2 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA > PME(D0-,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Address: 00000000fee002f8 Data: 0000 > Kernel driver in use: xhci_hcd All right. You've got a Intel Panther Point xHCI host then. Did you notice these messages on older kernels, or just with the 3.9-rc1 kernel? Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
