hci_queue_intr_tx callbacks suppressed

dbfontes · 06-28-2013, 09:51 AM

Hi,

I've read several posts on google about bugs but I'm not confident. Does anyone have any idea what can be?

Quote:

/var/log/syslog
Jun 28 11:49:33 WRX kernel: xhci_queue_intr_tx: 73 callbacks suppressed
Jun 28 11:49:38 WRX kernel: xhci_queue_intr_tx: 72 callbacks suppressed
Jun 28 11:49:48 WRX last message repeated 2 times
Jun 28 11:49:53 WRX kernel: xhci_queue_intr_tx: 73 callbacks suppressed
Jun 28 11:49:58 WRX kernel: xhci_queue_intr_tx: 72 callbacks suppressed
Jun 28 11:50:14 WRX last message repeated 3 times
Jun 28 11:50:19 WRX kernel: xhci_queue_intr_tx: 73 callbacks suppressed
Jun 28 11:50:24 WRX kernel: xhci_queue_intr_tx: 72 callbacks suppressed
Jun 28 11:50:34 WRX last message repeated 2 times
Jun 28 11:50:39 WRX kernel: xhci_queue_intr_tx: 73 callbacks suppressed

Quote:

dmesg -x
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 71 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed
kern :warn : xhci_queue_intr_tx: 72 callbacks suppressed

Quote:

version:
slackware64-current

Quote:

uname -a
Linux WRX 3.9.7 #1 SMP Sat Jun 22 02:37:32 CDT 2013 x86_64 Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz GenuineIntel GNU/Linux

Quote:

lspci
00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04)
00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04)
01:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)

Quote:

lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 0bda:0129 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 8087:07da Intel Corp.
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 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 2232:1053

Thanks.

Didier Spaier · 06-29-2013, 03:04 AM

According to this thread it could be a bug in module rts5139, whode description is:
Realtek RTS5139/29 USB card reader driver

Please check that this module be in use with 'lsmod|grep 5139' 'lspci -k|grep -B3 5139'

If yes, as root do:

Code:

rmmod rts5139

to to unload the module.

If that works, blacklist it. as root:

Code:

echo "blacklist rts5139" > /etc/modprobe.d/blacklist_5139

If you need to use your card reader, type as root

Code:

modprobe rts5139

to load the module.

Of course this is (possibly) a temporary fix. Real fix should come from upstream developer of the module.

dbfontes · 07-02-2013, 07:47 AM

Thank you very much, Didier Spaier.