Millions upon Millions of "xhci_hcd 0000:03:00.0: ERROR no room on ep ring" messages?

[phands]

I hope this is in the right forum…please say if not.

I’m getting literally millions of messages in dmesg and /var/log/messages and /var/log/warn…

** [161556.292615] xhci_hcd 0000:03:00.0: ERROR no room on ep ring

**The number of entries in /var/log, messages and warn, is increasing rapidly, and will soon overfill the root partition
It’s not clear to me where they’re coming from, but I think it’s the USB subsystem, although I don’t know which component/device.

The machine is an Intel GA-Z68AP-D3 mobo with a quad i5-2300 CPU @ 2.80GHz and 16G RAM.

lspci returns…

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:02.0 Display controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1d.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: nVidia Corporation GF106 [GeForce 450 GTS] (rev a1)
01:00.1 Audio device: nVidia Corporation GF106 High Definition Audio Controller (rev a1)
03:00.0 USB Controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
05:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 30)

and lsusb returns…

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless keyboard/mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 07d1:3c09 D-Link System DWA-140 RangeBooster N Adapter(rev.B1) [Ralink RT2870]

Anyone have any pointers?

Thanks,

Paul

[lwfinger]

On 07/31/2012 04:46 PM, phands wrote:
>
> I hope this is in the right forum…please say if not.
>
> I’m getting literally millions of messages in dmesg and
> /var/log/messages and /var/log/warn…
>
>
> * [161556.292615] xhci_hcd 0000:03:00.0: ERROR no room on ep ring
>
> *The number of entries in /var/log, messages and warn, is increasing
> rapidly, and will soon overfill the root partition
> It’s not clear to me where they’re coming from, but I think it’s the
> USB subsystem, although I don’t know which component/device.
>
> The machine is an Intel GA-Z68AP-D3 mobo with a quad i5-2300 CPU @
> 2.80GHz and 16G RAM.
>
>
> lspci returns…
>
>
> 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
> Family DRAM Controller (rev 09)
> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core
> Processor Family PCI Express Root Port (rev 09)
> 00:02.0 Display controller: Intel Corporation 2nd Generation Core
> Processor Family Integrated Graphics Controller (rev 09)
> 00:16.0 Communication controller: Intel Corporation 6 Series/C200
> Series Chipset Family MEI Controller #1 (rev 04)
> 00:1a.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset
> Family USB Enhanced Host Controller #2 (rev 05)
> 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
> Family High Definition Audio Controller (rev 05)
> 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
> Family PCI Express Root Port 1 (rev b5)
> 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
> Family PCI Express Root Port 2 (rev b5)
> 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
> Family PCI Express Root Port 3 (rev b5)
> 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
> 00:1d.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset
> Family USB Enhanced Host Controller #1 (rev 05)
> 00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC
> Controller (rev 05)
> 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset
> Family 6 port SATA AHCI Controller (rev 05)
> 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family
> SMBus Controller (rev 05)
> 01:00.0 VGA compatible controller: nVidia Corporation GF106 [GeForce
> 450 GTS] (rev a1)
> 01:00.1 Audio device: nVidia Corporation GF106 High Definition Audio
> Controller (rev a1)
> 03:00.0 USB Controller: Etron Technology, Inc. EJ168 USB 3.0 Host
> Controller (rev 01)
> 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
> 05:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892
> (rev 30)
>
> and lsusb returns…
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
> Hub
> Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
> Hub
> Bus 002 Device 003: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless
> keyboard/mouse
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 005: ID 07d1:3c09 D-Link System DWA-140 RangeBooster N
> Adapter(rev.B1) [Ralink RT2870]
>
>
> Anyone have any pointers?

Driver xhci-hcd is for USB 3.0 devices. I would guess that the DWA-140 is
plugged into that 3.0 root hub. If you are not using anything on the 3.0 root
hub, the messages should go away with “sudo /sbin/modprobe -rv xhci-hcd”. If it
says it is busy, then blacklist that module.

You did not say what openSUSE version you are using. A newer kernel is likely to
have fixed them. I remember a discussion on the Linux Kernel Mailing List about
such an issue about 6 months ago.

[phands]

Thanks for the fast response! It’s 12.1…

uname -aLinux Rincewind 3.1.10-1.16-desktop #1 SMP PREEMPT Wed Jun 27 05:21:40 UTC 2012 (d016078) x86_64 x86_64 x86_64 GNU/Linux

So, a fairly recent kernel…I think?

I’ll try moving the DWA-140 to another USB socket on a 2.0 hub, try the module unload, and let you know.

Thanks again,

Paul

[phands]

Flux Capacitor Penguin,

You are brilliant! I swapped the DWA-140 to a USB 2.0 port, and the messages stopped instantly - didn’t even need to unload the module - should I do it anyway? Does that revert the USB 3 hub to 2.0?

Thanks again,

Paul

[jdmcdaniel3]

@phands

Flux Capacitor Penguin,

You are brilliant! I swapped the DWA-140 to a USB 2.0 port, and the messages stopped instantly - didn’t even need to unload the module - should I do it anyway? Does that revert the USB 3 hub to 2.0?

Thanks again,

Paul

USB 3 inputs are compatible with USB 2 devices but there is no benefit in putting a USB 2 device into a USB 3 port. Its best at present to not mix USB 2 and 3 devices unless you are out of USB port options. You might report the issue, but you will likely be told the very same thing to not mix devices. As time goes forth with USB 3, compatibility will get better for sure.

Thank You,

[lwfinger]

On 07/31/2012 05:26 PM, phands wrote:
>
> Flux Capacitor Penguin,
>
> You are brilliant! I swapped the DWA-140 to a USB 2.0 port, and the
> messages stopped instantly - didn’t even need to unload the module -
> should I do it anyway? Does that revert the USB 3 hub to 2.0?

No, it does not change the 3.0 hub to 2.0. It just doesn’t use the 3.0 hub.

Yes, kernel 3.1 is recent; however, 3.5 is now released. As new versions are
released roughly every 3 months, 3.1 is over a year old, and far behind in the
drivers for new technology such as USB 3.0.

For now, just leave your wireless device on the 2.0 hub. When 12.2 is released,
the problem might be fixed in kernel 3.4. If not, file a bug report.

[phands]

@lwfinger

On 07/31/2012 05:26 PM, phands wrote:
>
> Flux Capacitor Penguin,
>
> You are brilliant! I swapped the DWA-140 to a USB 2.0 port, and the
> messages stopped instantly - didn’t even need to unload the module -
> should I do it anyway? Does that revert the USB 3 hub to 2.0?

No, it does not change the 3.0 hub to 2.0. It just doesn’t use the 3.0 hub.

Yes, kernel 3.1 is recent; however, 3.5 is now released. As new versions are
released roughly every 3 months, 3.1 is over a year old, and far behind in the
drivers for new technology such as USB 3.0.

For now, just leave your wireless device on the 2.0 hub. When 12.2 is released,
the problem might be fixed in kernel 3.4. If not, file a bug report.

Understood, thanks.

Paul

[hcvv]

Please @phands,

Make your next postings better readabale/understandable by putting the computer text parts of it between CODE tags. And here is how to do this: http://forums.opensuse.org/english/information-new-users/advanced-how-faq-read-only/451526-posting-code-tags-guide.html

And please do copy/paste then all that matters on the terminal screen: the prompt, the command and the output including next prompt. Then you do not need to tell strories like: lspci returns … Because you have it all there between the CODE tags.