Bug #1749961 “xhci_hcd: TRB DMA errors reported with ASMedia ASM...” : Bugs : linux package : Ubuntu

Guilherme G. Piccoli (gpiccoli) on 2018-02-16

no longer affects:	linux-meta (Ubuntu)
description:	updated

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2018-02-16: Missing required logs.

#1

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1749961

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status:	New → Incomplete

Rafael David Tinoco (rafaeldtinoco) on 2018-02-16

Changed in linux (Ubuntu):
status:	Incomplete → In Progress
importance:	Undecided → Medium
assignee:	nobody → Guilherme G. Piccoli (gpiccoli)

Guilherme G. Piccoli (gpiccoli) on 2018-02-16

Changed in linux (Ubuntu Trusty):
importance:	Undecided → Medium
status:	New → In Progress
assignee:	nobody → Guilherme G. Piccoli (gpiccoli)
Changed in linux (Ubuntu Xenial):
assignee:	nobody → Guilherme G. Piccoli (gpiccoli)
importance:	Undecided → Medium
status:	New → In Progress
Changed in linux (Ubuntu Artful):
assignee:	nobody → Guilherme G. Piccoli (gpiccoli)
importance:	Undecided → Medium
status:	New → In Progress

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2018-02-20:

#2

Patch was modified (by adding the PCI_ID of device 1142A, which confusingly is 1242!) and still the problem reproduces.

New approaches to be tried soon.

Joseph Salisbury (jsalisbury) on 2018-02-20

tags:

added: kernel-da-key

Revision history for this message

imperia (imperia777) wrote on 2018-03-28:

#3

Hello,
Looks like I am having the same problem.

After some hours(random time) my USB 3.1 asmedia controller crashes the driver with following error:
[ 873.661534] xhci_hcd 0000:00:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 0 comp_code 3
[ 873.661629] xhci_hcd 0000:00:00.0: Looking for event-dma 00000002722ed630 trb-start 00000002722ed9b0 trb-end 00000002722ed9d0 seg-start 00000002722ed000 seg-end 00000002722edff0
[ 875.673409] xhci_hcd 0000:00:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
I am struggling with this error for more than year. Its very annoying to have to restart the PC every few hours. USB tuner card is connected to the port.
I would like to provide whatever information and support is necessary to fix this damn bug. Logs, ssh access to the affected box and everything else what is needed.

Please ask me here or write to my e mail imperia777_yahoo.com
Thanks.

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2018-03-28:

#4

Nice imperia, thanks for the report here. First we need to be sure it's exactly the same adapter.
Can you provide the the output of "lspci -nn" ?

Then, if it's the same adapter:

0) Which Ubuntu version are you running? Which kernel version are you using? Can you try in the latest 4.13 for Xenial? (or even better, the hwe-edge 4.15)
Instructions to run the latest 4.15 version: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable?field.series_filter=xenial

1) You said "after some hours" - can you provide some details? You've been using the USB tuner for like 2 hours? 12 hours? The tuner is in constant use and suddenly the issue happens?

2) If possible, enable xhci dynamic debug and provide logs after the issue; in order to do this, run the following command as root:
echo "module xhci_hcd +flpt" > /sys/kernel/debug/dynamic_debug/control

After issue reproduces, collect the /var/log/kern.log file.

Thanks,

Guilherme

Revision history for this message

imperia (imperia777) wrote on 2018-03-29:

#5

Hello,

00:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]

Actually I am on debian buster. I am running kernel 4.16-rc6 from experimental repository.

I am running program for watching satellite channels called vdr.
When I am not watching TV, while idle, every few minutes vdr scans for channel list updates from satellites. It is safe to say that tuner is occupied every few minutes for a scan, but not occupied with bandwidth like when watching TV. While in this mode vdr is able to crash the driver in ~6-30 hours.

There is program that you use to initially create your channels list for vdr. When I use it I am able to crash the driver in ~1-2 hours.

But when I just watch one channel and don't change it for hours, driver is least likely to crash.

I think something in consecutive opening (initializing) of the usb port/driver forces this error.
Because the program that scans for channels crash it much faster.
This program work like this:

:go
open port
scan some frequency
write to file new channels
close port
goto go

I made this script that I will use to capture the log.

echo "module xhci_hcd +flpt" > /sys/kernel/debug/dynamic_debug/control
(tail -F -n0 /var/log/kern.log &) | grep -q "TRB DMA"
cp /var/log/kern.log /home/imperia/log1.log

And I will run initial channels list scan to force it faster.

I will be back later with the logs.
Thanks for your help.

Revision history for this message

imperia (imperia777) wrote on 2018-03-29:

#6

Download full text (8.6 KiB)

Mar 29 20:20:03 vdr kernel: [119370.230528] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c590 (dma).
Mar 29 20:20:03 vdr kernel: [119370.230533] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.230537] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.230542] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.230547] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5a0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.230553] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 0000000041e92668 (0x2ae36c5a0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.230558] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230631] [27868] xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cancel URB 0000000060641c50, dev 2, ep 0x82, starting at offset 0x2ae36c5a0
Mar 29 20:20:03 vdr kernel: [119370.230638] [27868] xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230650] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5a0
Mar 29 20:20:03 vdr kernel: [119370.230700] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c5a0 (dma).
Mar 29 20:20:03 vdr kernel: [119370.230705] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.230710] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.230715] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.230719] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5b0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.230725] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 0000000050070757 (0x2ae36c5b0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.230730] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230798] [27868] xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cancel URB 00000000588cca08, dev 2, ep 0x82, starting at offset 0x2ae36c5b0
Mar 29 20:20:03 vdr kernel: [119370.230805] [27868] xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230816] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5b0
Mar 29 20:20:03 vdr kernel: [119370.230865] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c5b0 (dma).
Mar 29 20:20:03 vdr kernel: [119370.230870] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.230874] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:...

Mar 29 20:20:03 vdr kernel: [119370.230528] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c590 (dma).
Mar 29 20:20:03 vdr kernel: [119370.230533] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.230537] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.230542] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.230547] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5a0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.230553] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 0000000041e92668 (0x2ae36c5a0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.230558] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230631] [27868] xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cancel URB 0000000060641c50, dev 2, ep 0x82, starting at offset 0x2ae36c5a0
Mar 29 20:20:03 vdr kernel: [119370.230638] [27868] xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230650] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5a0
Mar 29 20:20:03 vdr kernel: [119370.230700] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c5a0 (dma).
Mar 29 20:20:03 vdr kernel: [119370.230705] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.230710] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.230715] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.230719] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5b0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.230725] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 0000000050070757 (0x2ae36c5b0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.230730] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230798] [27868] xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cancel URB 00000000588cca08, dev 2, ep 0x82, starting at offset 0x2ae36c5b0
Mar 29 20:20:03 vdr kernel: [119370.230805] [27868] xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230816] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5b0
Mar 29 20:20:03 vdr kernel: [119370.230865] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c5b0 (dma).
Mar 29 20:20:03 vdr kernel: [119370.230870] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.230874] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.230879] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.230884] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5c0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.230910] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 00000000a598b646 (0x2ae36c5c0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.230918] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.231023] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5c0
Mar 29 20:20:03 vdr kernel: [119370.231041] [27868] xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cancel URB 000000006bc9f6cb, dev 2, ep 0x82, starting at offset 0x2ae36c5c0
Mar 29 20:20:03 vdr kernel: [119370.231051] [27868] xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.231121] <intr> handle_tx_event:2385: xhci_hcd 0000:00:00.0: Babble error for slot 1 ep 0 on endpoint
Mar 29 20:20:03 vdr kernel: [119370.231126] xhci_hcd 0000:00:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 0 comp_code 3
Mar 29 20:20:03 vdr kernel: [119370.231211] xhci_hcd 0000:00:00.0: Looking for event-dma 00000002afce2120 trb-start 00000002afce2380 trb-end 00000002afce23a0 seg-start 00000002afce2000 seg-end 00000002afce2ff0
Mar 29 20:20:03 vdr kernel: [119370.231327] <intr> handle_tx_event:2358: xhci_hcd 0000:00:00.0: Stopped on Transfer TRB for slot 1 ep 4
Mar 29 20:20:03 vdr kernel: [119370.231340] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c5c0 (dma).
Mar 29 20:20:03 vdr kernel: [119370.231356] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.231373] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.231390] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.231408] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5d0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.231425] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 000000007a204533 (0x2ae36c5d0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.231435] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.231513] [27868] xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cancel URB 00000000eedcc495, dev 2, ep 0x82, starting at offset 0x2ae36c5d0
Mar 29 20:20:03 vdr kernel: [119370.231520] [27868] xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.231532] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5d0
Mar 29 20:20:03 vdr kernel: [119370.231582] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c5d0 (dma).
Mar 29 20:20:03 vdr kernel: [119370.231587] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.231592] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.231597] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.231601] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5e0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.231607] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 0000000062fadf9e (0x2ae36c5e0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.231612] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.231682] [27868] xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cancel URB 0000000017950d25, dev 2, ep 0x82, starting at offset 0x2ae36c5e0
Mar 29 20:20:03 vdr kernel: [119370.231689] [27868] xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.231700] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5e0
Mar 29 20:20:03 vdr kernel: [119370.231750] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c5e0 (dma).
Mar 29 20:20:03 vdr kernel: [119370.231755] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.231759] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.231764] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.231769] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5f0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.231775] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 000000002857f382 (0x2ae36c5f0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.231780] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.231857] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5f0

http://imperia.mine.nu/log.tar.xz
full log

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2018-03-29:

#7

Thanks a lot Imperia! It's indeed the same PCI adapter, and it's even better you're running an upstream kernel like this.

I'll analyze your logs in order to match with the ones I have here.
I might need some xhci traces to understand the TRBs operations (like the enqueue and completion of TRBs). I'll comment here in case I need it.

Cheers,

Guilherme

Revision history for this message

imperia (imperia777) wrote on 2018-03-29:

#8

echo xhci-hcd >> /sys/kernel/debug/tracing/set_event
(tail -F -n0 /var/log/kern.log &) | grep -q "TRB DMA"
cp /var/log/kern.log /home/imperia/log1.log

Is this correct command to get traces?
I will run it in advance.

Somebody told me to run this before when I was looking for help.

BTW did you download the full logs so I can remove it from web page?

I will can provide ssh access to box affected if needed.

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2018-03-29:

#9

Wow Imperia, you're being really helpful here, thank you very much!

To enable traces, these are the instructions I've provided to other people affected so far:

0) Reboot the machine in order to put it in a consistent state;
1) echo "module xhci_hcd +flpt" > /sys/kernel/debug/dynamic_debug/control
2) echo nop > /sys/kernel/debug/tracing/current_tracer
3) echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb
4) echo 0 > /sys/kernel/debug/tracing/trace
5) echo 1 > /sys/kernel/debug/tracing/tracing_on
6) echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable

After reproduce the issue, you should collect /sys/kernel/debug/tracing/trace. Problem is that the file might be huge, much larger than the kernel log you provided for instance.

About the SSH access, I'm interested in getting it next week, if it doesn't annoy you too much. It'll be really helpful, but I might need to reboot the machine.

Oh, I've downloaded the logs from your website, so you can delete it now.
Cheers,

Guilherme

Revision history for this message

imperia (imperia777) wrote on 2018-04-02:

#10

Hello,

I think I am ready with the trace log. Hopefully it is full, because machine run out of disk space :)
http://imperia.mine.nu/trace1.log.bz2
Interesting is that it took ~12 hours to crash it this time.

The problem with ssh access is that this is virtual machine under XEN and when you reboot it, the USB controller is gone(not assigned to virtual machine anymore). I have to re-assign the USB controller for passthrough from xen host. (this is xen bug I think, it wasn't like this before).

This is what I do when I have to restart vdr virtual machine:
xl pci-assignable-remove 03:00.0
xl pci-assignable-add 03:00.0
xl create /etc/xen/vdr.cfg

Anyway we can get in touch on irc and I can do restarts for you.

BTW, I shutdown the whole xen server. Then I turn off the power button on PSU and pressed the power button on the case to discharge any electricity left and put it in consistent state before getting the trace logs.

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2018-04-02:

#11

Thanks again Imperia, the traces are fine. They're only 25MB, shouldn't have caused any kind of disk issues, like out of space condition. Also, I'd like to see the correlated kernel log to match the problematic TRBs from the kernel log with trace information. Can you provide me the relevant kern.log file?

I've already downloaded the traces from your server, in case you want to remove the file.

About the SSH, thanks for the offering and let's talk on IRC in case I need it. I'll try the logs first, not sure they're enough for me to understand the issue completely.

Cheers,

Guilherme

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2018-04-10:

#12

Hi Imperia, I built a mainline kernel (version 4.16) with a different quirk that I think might help here. Can you test it? Thanks in advance!

Instructions (run all as root):

1) wget people.canonical.com/~gpiccoli/imperia416.tgz
2) mv imperia416.tgz /
3) tar -zxf imperia416.tgz
4) update-initramfs -c -k 4.16.0-imperia+

Now that's important: if you have access to some serial console in the machine (or if you have physical access), you can reboot into this new kernel. In case _you only have ssh_, I'd suggest to remove the kernel boot entry from grub, and boot through kexec for safety reasons:

a) Remove boot entries from grub.cfg (you can copy away vmlinuz-4.16-imperia+ to some place outside /boot and run "update-grub" for this)
b) apt-get install kexec-tools
c) kexec vmlinuz-4.16-imperia+ --initrd initrd.img-4.16-imperia+ --append="$(cat /proc/cmdline)"
----

After machine (hopefully!) boot to the new kernel, check in dmesg if the quirk is there:
#$ dmesg|grep QUIRK
[0.813486] QUIRK: XHCI_AVOID_BEI

If you can see that output ("QUIRK: XHCI_AVOID_BEI"), then the quirk was applied.
Now, just need to try to reproduce the issue again.

Thanks a lot,

Guilherme

Revision history for this message

imperia (imperia777) wrote on 2018-04-11:

#13

Hello,

I am unable to test with the kernel you provided, because my tuner card doesn't have driver in mainline kernel tree. So I have to compile it myself and I need kernel headers for this.

So I compiled kernel 4.16 from debian linux-source-4.16 package and applied the patch you provided:

From dd0375ffba55172194999d40b35344e9dc2682df Mon Sep 17 00:00:00 2001
From: "Guilherme G. Piccoli" <email address hidden>
Date: Wed, 11 Apr 2018 11:04:13 +0000
Subject: [PATCH] xhci: Add quirk to ASMedia 0x1242 adapter to avoid BEI

Signed-off-by: Guilherme G. Piccoli <email address hidden>
---
drivers/usb/host/xhci-pci.c | 6 ++++++
1 file changed, 6 insertions(+)

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index d9f831b..0654461 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -213,6 +213,12 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)
xhci->quirks |= XHCI_TRUST_TX_LENGTH;

        if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
+ pdev->device == 0x1242) {
+ xhci->quirks |= XHCI_AVOID_BEI;
+ pr_warn("QUIRK: XHCI_AVOID_BEI");
+ }
+
+ if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
                pdev->device == PCI_DEVICE_ID_ASMEDIA_1042A_XHCI)
                xhci->quirks |= XHCI_ASMEDIA_MODIFY_FLOWCONTROL;

--
2.7.4

Compiled my tuner card driver now and I am testing.

Revision history for this message

Andy Whitcroft (apw) wrote on 2018-07-24: Closing unsupported series nomination.

#14

This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Artful):
status:	In Progress → Won't Fix

Revision history for this message

imperia (imperia777) wrote on 2018-08-27:

#15

dmidecode.out Edit (11.7 KiB, text/plain)

this is dmidecode output of my machine, in case the fix is FW related, it may be useful in order to contact the motherboard vendor

Revision history for this message

Roy Thompson (royt77) wrote on 2018-10-04:

#16

I am running into this same issue with an ASMedia 2142 USB board. Was a fix ever identified?

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2018-10-05:

#17

Hi Roy, thanks for the report. What is your motherboard? What kernel are you running? And what tests are triggering this issue for you?
If you have logs, it'll be pretty useful.

Maybe it's a similar but different case..or the logs may help to confirm it's exact the same issue.

ASMedia seems to have a FW fix but that depends on your motherboard vendor to provide it. They don't provide the fix themselves...it needs some cooking from the vendor, to match subsystem IDs and whatnot.

Cheers,

Guilherme

Changed in linux (Debian):
assignee:	nobody → Guilherme G. Piccoli (gpiccoli)
status:	New → Confirmed

Revision history for this message

Roy Thompson (royt77) wrote on 2018-10-05:

#18

Hi Guilherme,

Thanks for the response. I have several (3) quad port ASMedia 2142 PCIe/USB 3.1 cards installed in a Dell R740 rack server. I am using the standard Ubuntu 18.04 kernel (Linux dell-PowerEdge-R740 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux).

For one of my applications, it runs a loop that opens and closes a high speed connection to a USB device connected through the ASMedia board. After this goes on for several minutes without any issues, I see this in dmesg:

[Oct 5 10:12] xhci_hcd 0000:be:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ +3.418076] xhci_hcd 0000:be:00.0: WARN Successful completion on short TX
[ +0.000035] xhci_hcd 0000:be:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 12 comp_code 1
[ +0.000003] xhci_hcd 0000:be:00.0: Looking for event-dma 0000001fe9759610 trb-start 0000001fe9759620 trb-end 0000001fe9759620 seg-start 0000001fe9759000 seg-end 0000001fe9759ff0

This is then followed shortly after by several kernel dump messages, and then the whole system starts behaving erratically, requiring a hard reboot to recover.

The condition is easy for me to reproduce and I will happily provide any logs that may be of use to help debug this. Please just let me know what you would like and how to get them (as I am not a kernel expert).

Thanks,
Roy

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2018-10-05:

#19

Hi Roy, thanks for your quick response. First thing, I'd like to ask you to attach the output of "lspci -vvv" and "dmidecode" in this LP so we can validate the adapters and be sure they are exactly the same, and also the motherboard type. Run both commands as root user.

After that, i'll ask you to reproduce the issue and attach the output of "dmesg" command right after reproduction. If you can also elaborate more about the test you're running, I'd really be glad.

I'll then provide you custom commands to use the kernel trace system to infer more about the issue. One final thing: are you willing to test with mainline kernel in order to check if there's some upstream fix for your instance of the issue?
If so, you can get it here: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
This PPA provides a build from kernel 4.18.

Thanks in advance,

Guilherme

Revision history for this message

Bryan Walsh (yetanotherbryan) wrote on 2019-04-25:

#20

Download full text (4.0 KiB)

Hello,

I think I am seeing the same or related issue with the ASM1142 controller on my Razer Core Chroma EGPU enclosure. I'm running Ubuntu 19.04, kernel version 5.0.0-13-generic. Ethernet on the enclosure stops working while downloading large files. Dmesg produces the following error messages:

[ 569.641475] xhci_hcd 0000:0f:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13
[ 569.641487] xhci_hcd 0000:0f:00.0: Looking for event-dma 000000048d9c5770 trb-start 000000048d9c5750 trb-end 000000048d9c5750 seg-start 000000048d9c5000 seg-end 000000048d9c5ff0

lspci output:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V (rev 21)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
05:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
06:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
06:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
06:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
06:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
07:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02)
08:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
09:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
09:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
0a:00....

Hello,

I think I am seeing the same or related issue with the ASM1142 controller on my Razer Core Chroma EGPU enclosure.  I'm running Ubuntu 19.04, kernel version 5.0.0-13-generic.  Ethernet on the enclosure stops working while downloading large files.  Dmesg produces the following error messages:

[  569.641475] xhci_hcd 0000:0f:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13
[  569.641487] xhci_hcd 0000:0f:00.0: Looking for event-dma 000000048d9c5770 trb-start 000000048d9c5750 trb-end 000000048d9c5750 seg-start 000000048d9c5000 seg-end 000000048d9c5ff0

lspci output:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V (rev 21)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
05:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
06:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
06:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
06:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
06:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
07:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02)
08:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
09:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
09:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
0a:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
0a:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
0b:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
0c:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
0c:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
0c:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
0d:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
0e:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
0f:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller

Thanks,

Bryan

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2019-04-25:

#21

Hi Bryan, thanks for the report. It could be the same issue, can you provide the full dmesg, and also the outputs of the following commands: "lspci -nnvvv", "lspci -t" and "ls -l /sys/class/net"?

The issue was fixed for the first reporter via a FW update in the ASMedia adapter; unfortunately this FW update comes from the vendor, so the way of getting it varies according to the HW presenting the problem.

Cheers,

Guilherme

Revision history for this message

Bryan Walsh (yetanotherbryan) wrote on 2019-04-26:

#22

egpu_debug.txt Edit (26.8 KiB, text/plain)

Please see attached log for the outputs that you requested.

Revision history for this message

Bryan Walsh (yetanotherbryan) wrote on 2019-04-26:

#23

egpu_debug.txt Edit (26.8 KiB, text/plain)

Please see attached log for the outputs that you requested.

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2019-04-29:

#24

Great Bryan, the model of your USB controller is the same reported in this LP; also, given the outputs you provided, the network interface "enx90203a19dcb6" in under one of those USB controllers - you mentioned you see the TRB DMA errors and the interface stops responding. Is the problematic interface that one, "enx90203a19dcb6" ?

Who is the vendor of your device? I'd suggest you to seek help from them, mentioning this LP and that ASMedia may have a potential firmware fix for the issue.

Thanks,

Guilherme

Revision history for this message

Gabe Esposito (gabespo) wrote on 2019-05-04:

#25

I'm also experiencing the same issue with the ASM1142 controller on the Core X Chroma and can reproduce consistently. I'm running kernel 5.0.9.

Guilherme, thanks for your work diagnosing this. This device is sold by Razer. I will try and reach out but they do not claim Linux support on any of their devices so I worry this may go unfixed. Barring a firmware fix, is there any hope of this being fixed with a quirk, as the other controller was? I realize this LP is not the ideal place for such a fix to take place, but I am happy to participate in finding a solution.

Revision history for this message

Bryan Walsh (yetanotherbryan) wrote on 2019-05-04:

#26

In attempt to update the firmware I installed the razer software on my newly created windows partition, to see if it could be updated through there. No luck.

I emailed Razer support to ask about obtaining updated firmware. I'll let everyone know what I hear back.

And yes, "enx90203a19dcb6" is the problematic interface.

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2019-05-06:

#27

Thanks Gabe! I agree with you, would be really nice to have a quirk for that. It would be more easy to analyze that possibility with a datasheet for this adapter, which unfortunately I don't have.
I'm on vacation until next week, I'll try to discuss that in linux-usb when I'm back, and pursue a kernel quirk instead of firmware-only fix.

@Bryan, thanks for checking with the vendor, let us know the outcome.
Cheers,

Guilherme

Revision history for this message

Alex Lourenco (nyb-2017) wrote on 2019-05-26:

#28

I am experiencing the exact same issue first reported in this LP (ASMedia ASM1142 USB 3.1 Controller with a Logitech Brio 4k, ERROR Transfer event TRB DMA ptr not part of current TD ...). In my case the controller is provided by a StarTech.com 4 Port USB 3.1 PCIe Card 3x USB-A and 1x USB-C [PEXUS313AC2V].

While searching online I found a couple of LP's and forum posts with similar issues. The common factor seems to be high speed usb devices (e.g 4k webcam, usb ethernet adapters) connected to ASMedia controllers.

I have compiled 5.0.0 with a variety of existing quirks but nothing has done the trick so far. There are a couple of ASMedia firmwares posted on station-drivers. Unfortunately none of them seem to fix the issue either.

Revision history for this message

Felix Moreno (felix-justdust) wrote on 2019-09-28:

#29

having same problem with Bus 002 Device 004: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2019-09-30:

#30

So Felix, can you provide more details like the machine or device you're using, a dmesg showing the problem, and a bit more information about the device itself? I guess you're the first reporter with a "SATA" device showing that.

Thanks,

Guilherme

Revision history for this message

Erik Davidson (aphistic) wrote on 2019-12-08:

#31

egpu_debug.txt Edit (142.9 KiB, text/plain)

I'm also seeing this issue on a fresh install of Ubuntu 19.10 with a Razer Core X Chroma and a Lenovo X1 Extreme Gen2. I was seeing it on a fully updated Arch Linux install and installed Ubuntu in hopes it would fix the issue. Here's some info from my current install. Let me know if you need anything else!

uname:
Linux fate 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I've attached all the same info you were asking for earlier.

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2019-12-13:

#32

Hi Erik, thanks for your report! Can you attach a dmesg right after the issue reproduces?
Also, are you willing to run debug kernels in your machine?

The problem was narrowed down to a FW issue fixed by ASMedia in form of firmware upgrade but this seems to not be available from ASMedia themselves; instead, the motherboard vendor usually is the path for obtaining such fix.

That said, I'd be really glad if we could quirk this from kernel perspective to get the fix to a wider audience, not relying on unresponsive motherboard vendors. So let me know if you (also applies to anybody that reported the issue) are willing to run debug kernels.

Cheers,

Guilherme

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2019-12-13:

#33

For reference, here's the analysis from xHCI maintainer:
https://<email address hidden>/

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2019-12-13:

#34

Thanks a lot @kaihengfeng! Quite great discussion with Mathias - it seems there's a potential quirk for IN packets, but the right approach indeed is getting the HW fixed by ASMedia.

Cheers,

Guilherme

Revision history for this message

Bryan Walsh (yetanotherbryan) wrote on 2019-12-13:

#35

I would be willing to try a debug kernel.

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2019-12-14:

#36

Thank you Bryan! We can try the "hackish" approach proposed by Mathias in that thread..let me study the code and get back to you in next few weeks!

Cheers,

Guilherme

Revision history for this message

Bryan Walsh (yetanotherbryan) wrote on 2019-12-15:

#37

Sounds good. I'm not sure if matters or not but, I'm now on Ubuntu 19.10. I'm seeing the exact same behavior as before.

Revision history for this message

Erik Davidson (aphistic) wrote on 2019-12-21:

#38

egpu_debug.txt Edit (127.4 KiB, text/plain)

Guilherme, I've attached a dmesg that ends as soon as my ethernet in the egpu disconnects. It's just a matter of running something like "fast.com" a couple times to trigger it.

I'd also be willing to try a debug kernel or whatever else I can do to help get this fixed!

Revision history for this message

Erik Davidson (aphistic) wrote on 2019-12-21:

#39

I also wanted to mention that in my case after the issue is triggered I can unplug the cable from the ethernet jack on the eGPU I have, then plug it back in and it'll work again for a little bit until I trigger it again.

Revision history for this message

Danny Pacheco (vfdb67) wrote on 2020-02-28:

#40

Download full text (6.3 KiB)

I am seeing this same issue on my system. Any help would be greatly appreciated. I am using Ubuntu 16.04 with the 4.15.0-88-generic kernel. I have seen it on both host controllers on the motherboard.

Here is the info for the host controllers.

00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af] (prog-if 30 [XHCI])
        Subsystem: ASRock Incorporation Device [1849:a2af]
        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 32
        Region 0: Memory at 92f30000 (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: 00000000fee00278 Data: 0000
        Kernel driver in use: xhci_hcd

b3:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:2142] (prog-if 30 [XHCI])
        Subsystem: ASRock Incorporation Device [1849:2142]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 33
        Region 0: Memory at fbe00000 (64-bit, non-prefetchable) [size=32K]
        Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
                Address: 0000000000000000 Data: 0000
        Capabilities: [68] MSI-X: Enable+ Count=8 Masked-
                Vector table: BAR=0 offset=00002000
                PBA: BAR=0 offset=00002080
        Capabilities: [78] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME+
        Capabilities: [80] Express (v2) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <2us
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 256 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <2us, L1 unlimited
                        ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 8GT/s, Width x2, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Not Supp...

I am seeing this same issue on my system. Any help would be greatly appreciated. I am using Ubuntu 16.04 with the 4.15.0-88-generic kernel. I have seen it on both host controllers on the motherboard.

Here is the  info for the host controllers.

00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af] (prog-if 30 [XHCI])
        Subsystem: ASRock Incorporation Device [1849:a2af]
        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 32
        Region 0: Memory at 92f30000 (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: 00000000fee00278  Data: 0000
        Kernel driver in use: xhci_hcd

b3:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:2142] (prog-if 30 [XHCI])
        Subsystem: ASRock Incorporation Device [1849:2142]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 33
        Region 0: Memory at fbe00000 (64-bit, non-prefetchable) [size=32K]
        Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [68] MSI-X: Enable+ Count=8 Masked-
                Vector table: BAR=0 offset=00002000
                PBA: BAR=0 offset=00002080
        Capabilities: [78] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME+
        Capabilities: [80] Express (v2) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <2us
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 256 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <2us, L1 unlimited
                        ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 8GT/s, Width x2, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
                LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+
                         EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap- ChkEn-
        Capabilities: [200 v1] #19
        Capabilities: [300 v1] Latency Tolerance Reporting
                Max snoop latency: 0ns
                Max no snoop latency: 0ns
        Kernel driver in use: xhci_hcd

Here is the kernel logs around the issues.

ASMedia host controller

[79349.641660] xhci_hcd 0000:b3:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
[79349.641787] xhci_hcd 0000:b3:00.0: Looking for event-dma 000000067614d5e0 trb-start 000000067614d5f0 trb-end 000000067614d630 seg-start 000000067614d000 seg-end 000000067614dff0

Intel Host controller

[ 1155.942954] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 1155.942982] xhci_hcd 0000:00:14.0: bad transfer trb length 16384 in event trb
[ 1155.943029] xhci_hcd 0000:00:14.0: bad transfer trb length 16384 in event trb
[ 1155.943102] xhci_hcd 0000:00:14.0: bad transfer trb length 16384 in event trb
[ 1155.943142] xhci_hcd 0000:00:14.0: bad transfer trb length 16384 in event trb
[ 1155.943221] xhci_hcd 0000:00:14.0: bad transfer trb length 16384 in event trb
[ 1155.943261] xhci_hcd 0000:00:14.0: bad transfer trb length 16384 in event trb
[ 1155.943341] xhci_hcd 0000:00:14.0: bad transfer trb length 16384 in event trb
[ 1155.943382] xhci_hcd 0000:00:14.0: bad transfer trb length 16384 in event trb
[ 1155.943462] xhci_hcd 0000:00:14.0: bad transfer trb length 16384 in event trb
[ 1199.812033] xhci_hcd 0000:00:14.0: bad transfer trb length 16332 in event trb
[ 1199.952143] xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1
[ 1199.952501] xhci_hcd 0000:00:14.0: Looking for event-dma 0000000387c3da40 trb-start 0000000387c3da50 trb-end 0000000000000000 seg-start 0000000387c3d000 seg-end 0000000387c3dff0
[ 1199.952502] xhci_hcd 0000:00:14.0: Looking for event-dma 0000000387c3da40 trb-start 00000003d44a8000 trb-end 00000003d44a8d70 seg-start 00000003d44a8000 seg-end 00000003d44a8ff0

Guilherme G. Piccoli (gpiccoli) on 2020-05-04

no longer affects:	linux (Ubuntu Artful)
Changed in linux (Ubuntu Trusty):
status:	In Progress → Won't Fix

Guilherme G. Piccoli (gpiccoli) on 2020-05-05

Changed in linux (Ubuntu Focal):
status:	New → Confirmed
importance:	Undecided → Medium
assignee:	nobody → Guilherme G. Piccoli (gpiccoli)

Guilherme G. Piccoli (gpiccoli) on 2020-07-14

Changed in linux (Ubuntu Bionic):
status:	In Progress → Confirmed
Changed in linux (Ubuntu Xenial):
status:	In Progress → Confirmed

Revision history for this message

In Linux Kernel Bug Tracker #202541, ZeroBeat (zerobeat-linux-kernel-bugs) wrote on 2021-01-22:

#237

Stanislaw, and you're not the only one. I doubt it, too.
Maybe I patched my kernel to death and it is time for me to compile a fresh one.
But anyway, thanks for your effort an for your patience.

Revision history for this message

In Linux Kernel Bug Tracker #202541, ZeroBeat (zerobeat-linux-kernel-bugs) wrote on 2021-01-22:

#238

Stanislaw, short notice for you. Now, I'm running the fresh kernel (the RYZEN is really fast compiling it). Patch v2 is applied.
Everything is working fine and all Bogus messages are gone.
Thanks again.

Revision history for this message

In Linux Kernel Bug Tracker #202541, wgh (wgh-linux-kernel-bugs) wrote on 2021-01-29:

#239

(In reply to Mathias Nyman from comment #139)
> rewritten URB cancel, endpoint stop and set trb deq can be found in my tree
> in rewrite_halt_stop_handling branch
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git
> rewrite_halt_stop_handling
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/log/
> ?h=rewrite_halt_stop_handling
>
> Does that help?

I applied the patch to 5.10.11-gentoo, and it did help with my HackRF One (see comment #136 for details and hardware)! No ill effects so far.

Revision history for this message

In Linux Kernel Bug Tracker #202541, stf_xl (stfxl-linux-kernel-bugs) wrote on 2021-02-03:

#240

After discussion on my posted patch here:

https://<email address hidden>/t/#u

it was concluded that this should be rather be xhci quirk instead of rt2800usb driver flag.

If change from comment 147 help for you with the problem, please provide PCI-id of your xHCI controller. This can be done by command:

lspci -k -nn | grep -B2 xhci

If you have more than one xHCI controller please assure you provide PCI-id's of one that actually has the problem ('lspci -t' command can be useful as well)

Revision history for this message

In Linux Kernel Bug Tracker #202541, stf_xl (stfxl-linux-kernel-bugs) wrote on 2021-02-03:

#241

(In reply to Stanislaw Gruszka from comment #173)
> If you have more than one xHCI controller please assure you provide PCI-id's
> of one that actually has the problem ('lspci -t' command can be useful as
> well)

I meant 'lsusb -t'

Revision history for this message

In Linux Kernel Bug Tracker #202541, ZeroBeat (zerobeat-linux-kernel-bugs) wrote on 2021-02-03:

#242

USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller [1022:43b9] (rev 02)
Subsystem: ASMedia Technology Inc. Device [1b21:1142]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

Revision history for this message

In Linux Kernel Bug Tracker #202541, stf_xl (stfxl-linux-kernel-bugs) wrote on 2021-02-03:

#243

Created attachment 295055
0001-usb-xhci-do-not-perform-Soft-Retry-for-some-xHCI-hos.patch

This is next proposed fix. It suppose to disable Soft Retry for affected xHCI controllers. Currently only for xHCI device reported by Michael:
PCI_VENDOR_ID_AMD = 0x1022 , PCI_DEVICE_ID_AMD_PROMONTORYA_4 = 0x43b9

If you want to test and have different xHCI host you need to add your PCI-id's to
drivers/usb/host/xhci-pci.c part of the patch.

Revision history for this message

In Linux Kernel Bug Tracker #202541, ZeroBeat (zerobeat-linux-kernel-bugs) wrote on 2021-02-03:

#244

@Stanislaw, I followed the discussion you mentioned here:
https://bugzilla.kernel.org/show_bug.cgi?id=202541#c173

Other devices than rt2800usb devices are affected, too.
Tested this one before applying your patch:
ID 7392:7710 Edimax Technology Co., Ltd Edimax Wi-Fi
and running into the same xhci issue on USB controller mentioned here:
https://bugzilla.kernel.org/show_bug.cgi?id=202541#c175

[10214.423508] usb 1-2: new high-speed USB device number 3 using xhci_hcd
[10214.602833] usb 1-2: New USB device found, idVendor=7392, idProduct=7710, bcdDevice= 0.00
[10214.602838] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10214.602841] usb 1-2: Product: Edimax Wi-Fi
[10214.602843] usb 1-2: Manufacturer: MediaTek
[10214.602845] usb 1-2: SerialNumber: 1.0
[10214.931553] usb 1-2: reset high-speed USB device number 3 using xhci_hcd
[10215.102895] mt7601u 1-2:1.0: ASIC revision: 76010001 MAC revision: 76010500
[10215.132670] mt7601u 1-2:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146____
[10216.101346] mt7601u 1-2:1.0: EEPROM ver:0d fae:00
[10216.111983] mt7601u 1-2:1.0: EEPROM country region 01 (channels 1-13)
[10217.189574] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[10217.190361] usbcore: registered new interface driver mt7601u
[10217.199429] mt7601u 1-2:1.0 wlp3s0f0u2: renamed from wlan0
[10296.419053] xhci_hcd 0000:03:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[10296.419228] xhci_hcd 0000:03:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.

Revision history for this message

In Linux Kernel Bug Tracker #202541, jg.staffel (jg.staffel-linux-kernel-bugs) wrote on 2021-02-03:

#245

The same problem (with ID 04a9:220d Canon, Inc. CanoScan N670U/N676U/LiDE 20):

Feb 03 09:48:54 [kernel] [34974.104606] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Feb 03 09:49:49 [kernel] [35029.419748] usb 1-6: USB disconnect, device number 3
Feb 03 09:49:52 [kernel] [35031.994403] usb 1-6: new full-speed USB device number 6 using xhci_hcd
Feb 03 09:50:45 [kernel] [35085.400634] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Feb 03 09:50:45 [kernel] [35085.404278] xhci_hcd 0000:01:00.0: WARN Successful completion on short TX
Feb 03 09:50:45 [kernel] [35085.404398] xhci_hcd 0000:01:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 1
Feb 03 09:50:45 [kernel] [35085.404401] xhci_hcd 0000:01:00.0: Looking for event-dma 00000008146ff050 trb-start 00000008146ff060 trb-end 00000008146ff060 seg-start 00000008146ff000 seg-end 00000008146ffff0

$ lspci -k -nn | grep -B2 xhci
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467]
01:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01)
Subsystem: ASMedia Technology Inc. 400 Series Chipset USB 3.1 XHCI Controller [1b21:1142]
Kernel driver in use: xhci_hcd
--
09:00.2 USB controller [0c03]: NVIDIA Corporation TU116 USB 3.1 Host Controller [10de:1aec] (rev a1)
Subsystem: NVIDIA Corporation TU116 USB 3.1 Host Controller [10de:139d]
Kernel driver in use: xhci_hcd
--
0a:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller [1022:145f]
Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller [1022:7914]
Kernel driver in use: xhci_hcd

$ uname -a
Linux Gentoo 5.4.92-gentoo #1 SMP PREEMPT Thu Jan 28 20:45:52 MSK 2021 x86_64 AMD Ryzen 5 2600 Six-Core Processor AuthenticAMD GNU/Linux

The same problem (with ID 04a9:220d Canon, Inc. CanoScan N670U/N676U/LiDE 20):

Feb 03 09:48:54 [kernel] [34974.104606] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Feb 03 09:49:49 [kernel] [35029.419748] usb 1-6: USB disconnect, device number 3
Feb 03 09:49:52 [kernel] [35031.994403] usb 1-6: new full-speed USB device number 6 using xhci_hcd
Feb 03 09:50:45 [kernel] [35085.400634] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Feb 03 09:50:45 [kernel] [35085.404278] xhci_hcd 0000:01:00.0: WARN Successful completion on short TX
Feb 03 09:50:45 [kernel] [35085.404398] xhci_hcd 0000:01:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 1
Feb 03 09:50:45 [kernel] [35085.404401] xhci_hcd 0000:01:00.0: Looking for event-dma 00000008146ff050 trb-start 00000008146ff060 trb-end 00000008146ff060 seg-start 00000008146ff000 seg-end 00000008146ffff0

$  lspci -k -nn | grep -B2 xhci
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467]
01:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01)
	Subsystem: ASMedia Technology Inc. 400 Series Chipset USB 3.1 XHCI Controller [1b21:1142]
	Kernel driver in use: xhci_hcd
--
09:00.2 USB controller [0c03]: NVIDIA Corporation TU116 USB 3.1 Host Controller [10de:1aec] (rev a1)
	Subsystem: NVIDIA Corporation TU116 USB 3.1 Host Controller [10de:139d]
	Kernel driver in use: xhci_hcd
--
0a:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller [1022:145f]
	Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller [1022:7914]
	Kernel driver in use: xhci_hcd

$  uname -a
Linux Gentoo 5.4.92-gentoo #1 SMP PREEMPT Thu Jan 28 20:45:52 MSK 2021 x86_64 AMD Ryzen 5 2600 Six-Core Processor AuthenticAMD GNU/Linux

Revision history for this message

In Linux Kernel Bug Tracker #202541, stf_xl (stfxl-linux-kernel-bugs) wrote on 2021-02-03:

#246

(In reply to Michael from comment #177)
> Other devices than rt2800usb devices are affected, too.
> Tested this one before applying your patch:
> ID 7392:7710 Edimax Technology Co., Ltd Edimax Wi-Fi
> and running into the same xhci issue on USB controller mentioned here:
> https://bugzilla.kernel.org/show_bug.cgi?id=202541#c175

Ok, so it makes sense to disable Soft Retry per xHCI.

Revision history for this message

In Linux Kernel Bug Tracker #202541, stf_xl (stfxl-linux-kernel-bugs) wrote on 2021-02-03:

#247

(In reply to alpir from comment #178)
> The same problem (with ID 04a9:220d Canon, Inc. CanoScan N670U/N676U/LiDE
> 20):
>
> Feb 03 09:48:54 [kernel] [34974.104606] xhci_hcd 0000:01:00.0: WARN Set TR
> Deq Ptr cmd failed due to incorrect slot or ep state.

alpir, does the change from comment 147 help for you ?

Revision history for this message

In Linux Kernel Bug Tracker #202541, stf_xl (stfxl-linux-kernel-bugs) wrote on 2021-02-03:

#248

alpir, you have different device-id than Michael, but you both have the same subsytem device: ASMedia 1b21:1142. So perhaps patch should be based on subdevice id's. Let's wait for other users reports regarding xHCI controller, we will see then.

Revision history for this message

In Linux Kernel Bug Tracker #202541, jg.staffel (jg.staffel-linux-kernel-bugs) wrote on 2021-02-03:

#249

Download full text (9.5 KiB)

I tried patch from comment 147. The error "WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state" has gone. But behavior USDB3.1 still the same.

Why did I even start looking for the reason for the strange behavior of OSD ports: two my JetFlash Transcend 8GB flash drives connected to the USB3 port is sometimes not detected by the system as being mountable (fat32). When I run a disk check (8 Gb) with the command badblocks -nvs / dev / sdd, then after a while the check ends with the following error: Pass completed, 5662144 bad blocks found. (5662144/0/0 errors). And both flash drives.

But if you connect them to USB2, then there are no errors at all.

At the same time, when looking at the logs, I found errors: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.

Now, after patch, i get next in logs:

Feb 03 17:47:14 [kernel] [ 52.603587] usb 2-3: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:47:14 [kernel] [ 52.636130] usb-storage 2-3:1.0: USB Mass Storage device detected
Feb 03 17:47:14 [kernel] [ 52.636242] scsi host11: usb-storage 2-3:1.0
Feb 03 17:47:14 [kernel] [ 52.651996] usbcore: registered new interface driver uas
Feb 03 17:47:16 [kernel] [ 54.013780] scsi 11:0:0:0: Direct-Access JetFlash Transcend 8GB 1100 PQ: 0 ANSI: 6
Feb 03 17:47:16 [kernel] [ 54.014688] sd 11:0:0:0: [sdd] 15425536 512-byte logical blocks: (7.90 GB/7.36 GiB)
Feb 03 17:47:16 [kernel] [ 54.015150] sd 11:0:0:0: [sdd] Write Protect is off
Feb 03 17:47:16 [kernel] [ 54.015156] sd 11:0:0:0: [sdd] Mode Sense: 43 00 00 00
Feb 03 17:47:16 [kernel] [ 54.015625] sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 03 17:47:16 [kernel] [ 54.028165] sdd: sdd1
Feb 03 17:47:16 [kernel] [ 54.045687] sd 11:0:0:0: [sdd] Attached SCSI removable disk
Feb 03 17:48:04 [kernel] [ 102.221862] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:51:52 [kernel] [ 330.009696] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:55:55 [kernel] [ 573.644576] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:01 [kernel] [ 579.149875] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:01 [kernel] [ 579.254204] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:06 [kernel] [ 584.781836] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:07 [kernel] [ 585.073435] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:12 [kernel] [ 590.413816] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:12 [kernel] [ 590.518146] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:18 [kernel] [ 596.046034] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:18 [kernel] [ 596.336445] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:23 [kernel] [ 601.677932] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:23 [kernel] [ 601.782091] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:29 [kernel] [ 607.309722] usb 2-3: device descr...

I tried patch from comment 147. The error "WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state" has gone. But behavior USDB3.1 still the same.

Why did I even start looking for the reason for the strange behavior of OSD ports: two my JetFlash Transcend 8GB flash drives connected to the USB3 port is sometimes not detected by the system as being mountable (fat32). When I run a disk check (8 Gb) with the command badblocks -nvs / dev / sdd, then after a while the check ends with the following error: Pass completed, 5662144 bad blocks found. (5662144/0/0 errors). And both flash drives.

But if you connect them to USB2, then there are no errors at all.

At the same time, when looking at the logs, I found errors: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.

Now, after patch, i get next in logs:

Feb 03 17:47:14 [kernel] [   52.603587] usb 2-3: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:47:14 [kernel] [   52.636130] usb-storage 2-3:1.0: USB Mass Storage device detected
Feb 03 17:47:14 [kernel] [   52.636242] scsi host11: usb-storage 2-3:1.0
Feb 03 17:47:14 [kernel] [   52.651996] usbcore: registered new interface driver uas
Feb 03 17:47:16 [kernel] [   54.013780] scsi 11:0:0:0: Direct-Access     JetFlash Transcend 8GB    1100 PQ: 0 ANSI: 6
Feb 03 17:47:16 [kernel] [   54.014688] sd 11:0:0:0: [sdd] 15425536 512-byte logical blocks: (7.90 GB/7.36 GiB)
Feb 03 17:47:16 [kernel] [   54.015150] sd 11:0:0:0: [sdd] Write Protect is off
Feb 03 17:47:16 [kernel] [   54.015156] sd 11:0:0:0: [sdd] Mode Sense: 43 00 00 00
Feb 03 17:47:16 [kernel] [   54.015625] sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 03 17:47:16 [kernel] [   54.028165]  sdd: sdd1
Feb 03 17:47:16 [kernel] [   54.045687] sd 11:0:0:0: [sdd] Attached SCSI removable disk
Feb 03 17:48:04 [kernel] [  102.221862] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:51:52 [kernel] [  330.009696] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:55:55 [kernel] [  573.644576] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:01 [kernel] [  579.149875] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:01 [kernel] [  579.254204] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:06 [kernel] [  584.781836] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:07 [kernel] [  585.073435] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:12 [kernel] [  590.413816] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:12 [kernel] [  590.518146] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:18 [kernel] [  596.046034] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:18 [kernel] [  596.336445] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:23 [kernel] [  601.677932] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:23 [kernel] [  601.782091] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:29 [kernel] [  607.309722] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:29 [kernel] [  607.598490] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:35 [kernel] [  612.941883] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:35 [kernel] [  613.046062] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Feb 03 17:56:40 [kernel] [  618.573664] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:40 [kernel] [  618.694297] usb 2-3: USB disconnect, device number 2
Feb 03 17:56:40 [kernel] [  618.702083] blk_update_request: I/O error, dev sdd, sector 4101248 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0
Feb 03 17:56:40 [kernel] [  618.702241] blk_update_request: I/O error, dev sdd, sector 4101248 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb 03 17:56:40 [kernel] [  618.702275] blk_update_request: I/O error, dev sdd, sector 4101248 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb 03 17:56:40 [kernel] [  618.702280] Buffer I/O error on dev sdd, logical block 512656, async page read
Feb 03 17:56:40 [kernel] [  618.702318] blk_update_request: I/O error, dev sdd, sector 4101248 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb 03 17:56:40 [kernel] [  618.702343] blk_update_request: I/O error, dev sdd, sector 4101248 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb 03 17:56:40 [kernel] [  618.702346] Buffer I/O error on dev sdd, logical block 512656, async page read
Feb 03 17:56:40 [kernel] [  618.702376] blk_update_request: I/O error, dev sdd, sector 4101248 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb 03 17:56:40 [kernel] [  618.702401] blk_update_request: I/O error, dev sdd, sector 4101248 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb 03 17:56:40 [kernel] [  618.702403] Buffer I/O error on dev sdd, logical block 512656, async page read
Feb 03 17:56:40 [kernel] [  618.702434] blk_update_request: I/O error, dev sdd, sector 4101248 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb 03 17:56:40 [kernel] [  618.702463] blk_update_request: I/O error, dev sdd, sector 4101256 op 0x0:(READ) flags 0x0 phys_seg 15 prio class 0
Feb 03 17:56:40 [kernel] [  618.702494] Buffer I/O error on dev sdd, logical block 512657, async page read
Feb 03 17:56:40 [kernel] [  618.702509] Buffer I/O error on dev sdd, logical block 512657, async page read
Feb 03 17:56:40 [kernel] [  618.702521] Buffer I/O error on dev sdd, logical block 512657, async page read
Feb 03 17:56:40 [kernel] [  618.702597] Buffer I/O error on dev sdd, logical block 512659, async page read
Feb 03 17:56:41 [kernel] [  618.892181] usb 2-3: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Feb 03 17:56:45 [kernel] [  623.702972] buffer_io_error: 2070133 callbacks suppressed
Feb 03 17:56:45 [kernel] [  623.702975] Buffer I/O error on dev sdd, logical block 1030195, async page read
Feb 03 17:56:45 [kernel] [  623.702979] Buffer I/O error on dev sdd, logical block 1030196, async page read
Feb 03 17:56:45 [kernel] [  623.702983] Buffer I/O error on dev sdd, logical block 1030196, async page read
Feb 03 17:56:45 [kernel] [  623.702986] Buffer I/O error on dev sdd, logical block 1030196, async page read
Feb 03 17:56:45 [kernel] [  623.702988] Buffer I/O error on dev sdd, logical block 1030196, async page read
Feb 03 17:56:45 [kernel] [  623.702991] Buffer I/O error on dev sdd, logical block 1030197, async page read
Feb 03 17:56:45 [kernel] [  623.702993] Buffer I/O error on dev sdd, logical block 1030197, async page read
Feb 03 17:56:45 [kernel] [  623.702995] Buffer I/O error on dev sdd, logical block 1030197, async page read
Feb 03 17:56:45 [kernel] [  623.702997] Buffer I/O error on dev sdd, logical block 1030197, async page read
Feb 03 17:56:45 [kernel] [  623.703000] Buffer I/O error on dev sdd, logical block 1030198, async page read
Feb 03 17:56:46 [kernel] [  624.205633] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:46 [kernel] [  624.309977] usb 2-3: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Feb 03 17:56:50 [kernel] [  628.703937] buffer_io_error: 2089117 callbacks suppressed
Feb 03 17:56:50 [kernel] [  628.703939] Buffer I/O error on dev sdd, logical block 1552477, async page read
Feb 03 17:56:50 [kernel] [  628.703942] Buffer I/O error on dev sdd, logical block 1552477, async page read
Feb 03 17:56:50 [kernel] [  628.703945] Buffer I/O error on dev sdd, logical block 1552478, async page read
Feb 03 17:56:50 [kernel] [  628.703948] Buffer I/O error on dev sdd, logical block 1552478, async page read
Feb 03 17:56:50 [kernel] [  628.703950] Buffer I/O error on dev sdd, logical block 1552478, async page read
Feb 03 17:56:50 [kernel] [  628.703953] Buffer I/O error on dev sdd, logical block 1552478, async page read
Feb 03 17:56:50 [kernel] [  628.703955] Buffer I/O error on dev sdd, logical block 1552479, async page read
Feb 03 17:56:50 [kernel] [  628.703958] Buffer I/O error on dev sdd, logical block 1552479, async page read
Feb 03 17:56:50 [kernel] [  628.703960] Buffer I/O error on dev sdd, logical block 1552479, async page read
Feb 03 17:56:50 [kernel] [  628.703963] Buffer I/O error on dev sdd, logical block 1552479, async page read
Feb 03 17:56:51 [kernel] [  629.838589] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:52 [kernel] [  630.129112] usb 2-3: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
Feb 03 17:56:57 [kernel] [  635.469561] usb 2-3: device descriptor read/8, error -110
Feb 03 17:56:57 [kernel] [  635.573925] usb 2-3: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
Feb 03 17:57:03 [kernel] [  641.101804] usb 2-3: device descriptor read/8, error -110
Feb 03 17:57:03 [kernel] [  641.214076] usb usb2-port3: attempt power cycle
Feb 03 17:57:04 [kernel] [  642.323012] usb 2-3: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
Feb 03 17:57:09 [kernel] [  647.757472] usb 2-3: device descriptor read/8, error -110
Feb 03 17:57:09 [kernel] [  647.861845] usb 2-3: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
Feb 03 17:57:15 [kernel] [  653.390427] usb 2-3: device descriptor read/8, error -110
Feb 03 17:57:15 [kernel] [  653.680943] usb 2-3: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
Feb 03 17:57:21 [kernel] [  659.022390] usb 2-3: device descriptor read/8, error -110
Feb 03 17:57:21 [kernel] [  659.125736] usb 2-3: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
Feb 03 17:57:26 [kernel] [  664.653379] usb 2-3: device descriptor read/8, error -110
Feb 03 17:57:26 [kernel] [  664.765744] usb usb2-port3: unable to enumerate USB device

Revision history for this message

In Linux Kernel Bug Tracker #202541, bernhard.gebetsberger (bernhard.gebetsberger-linux-kernel-bugs) wrote on 2021-02-03:

#250

My controller has the PCI ID 43bb, so I've added "PCI_DEVICE_ID_AMD_PROMONTORYA_2" to the patch from #176, and that fixed the issue for me.

Revision history for this message

In Linux Kernel Bug Tracker #202541, ZeroBeat (zerobeat-linux-kernel-bugs) wrote on 2021-02-03:

#251

@Stanislaw, I'm running an older mobo and a RYZEN 1700.
I don't need CPU power - GPU power is more important for me (crypto analysis).

Revision history for this message

In Linux Kernel Bug Tracker #202541, biopsin (biopsin-linux-kernel-bugs) wrote on 2021-02-04:

#252

[Continuing my first report in comment:https://bugzilla.kernel.org/show_bug.cgi?id=202541#c107]

$ lspci -k -nn | grep -B2 xhci
02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01)
Subsystem: ASMedia Technology Inc. Device [1b21:1142]
Kernel driver in use: xhci_hcd

I have adapted the patch by Mr. Gruszka [https://bugzilla.kernel.org/show_bug.cgi?id=202541#c176] for my current system and needs

$ uname -a
Linux voidx 5.4.95_1 #1 SMP PREEMPT 1612063540 x86_64 GNU/Linux

If someone has some spare time to glance at it or comment on my error ;)
(diff availible for 30 days) @
https://p.teknik.io/lIBbA

Revision history for this message

In Linux Kernel Bug Tracker #202541, stf_xl (stfxl-linux-kernel-bugs) wrote on 2021-02-04:

#253

(In reply to alpir from comment #182)
> I tried patch from comment 147. The error "WARN Set TR Deq Ptr cmd failed
> due to incorrect slot or ep state" has gone. But behavior USDB3.1 still the
> same.
[snip]
> But if you connect them to USB2, then there are no errors at all.

alpir, I think you experiencing different issue that can not be solved by simply disabling Soft Retry. Some more fixes are possibly needed for handing your xHCI/usb hardware. Maybe you can try patch from comment 139? If this is regression, maybe you can bisect to find offending commit? Anyway your problems, most likely will require expertise of Mathias Nyman - xhci driver maintainer.

Revision history for this message

In Linux Kernel Bug Tracker #202541, stf_xl (stfxl-linux-kernel-bugs) wrote on 2021-02-04:

#254

(In reply to biopsin from comment #185)
> [Continuing my first report in
> comment:https://bugzilla.kernel.org/show_bug.cgi?id=202541#c107]

Similarly like for as for alpir case this most likely will require some different fixes, but you can try if disabling Soft Retry works. You can just disable like showed in comment 147

> $ lspci -k -nn | grep -B2 xhci
> 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series
> Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01)
> Subsystem: ASMedia Technology Inc. Device [1b21:1142]
> Kernel driver in use: xhci_hcd
>
[snip]
> If someone has some spare time to glance at it or comment on my error ;)
> (diff availible for 30 days) @
> https://p.teknik.io/lIBbA

ASMedia is subsystem_{vendor,device) so most likely quirk flag is not set properly for you. You can print values by patch like this to see:

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index 906a0e08821e..0ec9c3637b7a 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -102,6 +102,9 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)

id = pci_match_id(pdev->driver->id_table, pdev);

+ printk("vendor: 0x%04x device 0x%04x subvendor 0x%04x subdevice 0x%04x\n",
+ pdev->vendor, pdev->device, pdev->subsystem_vendor, pdev->subsystem_device);
+
        if (id && id->driver_data) {
                driver_data = (struct xhci_driver_data *)id->driver_data;
                xhci->quirks |= driver_data->quirks;

If indeed those are subsystem ID's I think there is bug in existing xhci-pci.c quirks code:

        if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
                pdev->device == PCI_DEVICE_ID_ASMEDIA_1042_XHCI)
                xhci->quirks |= XHCI_BROKEN_STREAMS;
        if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
                pdev->device == PCI_DEVICE_ID_ASMEDIA_1042A_XHCI)
                xhci->quirks |= XHCI_TRUST_TX_LENGTH;
        if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
            (pdev->device == PCI_DEVICE_ID_ASMEDIA_1142_XHCI ||
             pdev->device == PCI_DEVICE_ID_ASMEDIA_2142_XHCI))
                xhci->quirks |= XHCI_NO_64BIT_SUPPORT

and those check should be replaced by pdev->subsystem_vendor and pdev->subsystem_device.

(In reply to biopsin from comment #185)
> [Continuing my first report in
> comment:https://bugzilla.kernel.org/show_bug.cgi?id=202541#c107]

Similarly like for as for alpir case this most likely will require some different fixes, but you can try if disabling Soft Retry works. You can just disable like showed in comment 147

> $ lspci -k -nn | grep -B2 xhci
> 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series
> Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01)
>         Subsystem: ASMedia Technology Inc. Device [1b21:1142]
>         Kernel driver in use: xhci_hcd
> 
[snip]
> If someone has some spare time to glance at it or comment on my error ;)
> (diff availible for 30 days) @
> https://p.teknik.io/lIBbA

ASMedia is subsystem_{vendor,device) so most likely quirk flag is not set properly for you. You can print values by patch like this to see:

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index 906a0e08821e..0ec9c3637b7a 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -102,6 +102,9 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)
 
        id = pci_match_id(pdev->driver->id_table, pdev);
 
+       printk("vendor: 0x%04x device 0x%04x subvendor 0x%04x subdevice 0x%04x\n",
+              pdev->vendor, pdev->device, pdev->subsystem_vendor, pdev->subsystem_device);
+
        if (id && id->driver_data) {
                driver_data = (struct xhci_driver_data *)id->driver_data;
                xhci->quirks |= driver_data->quirks;

If indeed those are subsystem ID's I think there is bug in existing xhci-pci.c quirks code:

if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
                pdev->device == PCI_DEVICE_ID_ASMEDIA_1042_XHCI)
                xhci->quirks |= XHCI_BROKEN_STREAMS;
        if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
                pdev->device == PCI_DEVICE_ID_ASMEDIA_1042A_XHCI)
                xhci->quirks |= XHCI_TRUST_TX_LENGTH;
        if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
            (pdev->device == PCI_DEVICE_ID_ASMEDIA_1142_XHCI ||
             pdev->device == PCI_DEVICE_ID_ASMEDIA_2142_XHCI))
                xhci->quirks |= XHCI_NO_64BIT_SUPPORT

and those check should be replaced by pdev->subsystem_vendor and pdev->subsystem_device.

Revision history for this message

In Linux Kernel Bug Tracker #202541, stf_xl (stfxl-linux-kernel-bugs) wrote on 2021-02-04:

#255

Created attachment 295065
asmedia_subsytem_quirks.patch

This patch apply existing xhci ASMedia quirks also for ASMedia subdevices .

Looking into changelog history those quirks helped with some usb disk issues, so perhaps patch could help with disk issues reported here i.e. alpir and biopsin cases. Please test.

Revision history for this message

In Linux Kernel Bug Tracker #202541, jg.staffel (jg.staffel-linux-kernel-bugs) wrote on 2021-02-04:

#256

None of the patches (comments 139, 147, 188) did not solve my problem.

Revision history for this message

In Linux Kernel Bug Tracker #202541, biopsin (biopsin-linux-kernel-bugs) wrote on 2021-02-05:

#257

@Gruszka
Your patch [https://bugzilla.kernel.org/show_bug.cgi?id=202541#c188] makes very mutch sense, thank you.
I'm currently testing it with my setup and kernel 5.4.95_x86_64.
Tested against one PATA and one SATA drives, so far I see no ill effects, but I also can't confirm or deny it does anything with this short timespan, and much have change since my initial post last year. I will at least continuing applying it now and then out this year and report any newsworthy. Thank you for your time and help!

Revision history for this message

In Linux Kernel Bug Tracker #202541, raulvior.bcn (raulvior.bcn-linux-kernel-bugs) wrote on 2021-02-09:

#258

Download full text (6.4 KiB)

Created attachment 295151
Dmesg of a Toshiba USB 3.0 HDD connected to USB 3.0 front port and back port.

I am having this error on Linux 5.10.10-051010 while trying to connect a USB 3.0 hard disk, Toshiba Touro 4TB (HitachiGST). If I connect the disk to a USB 2.0 port it works flawlessly.

The kernel shows a different kind of error depending on whether I connect the HDD to the front or back USB 3.0 ports of the motherboard MSI X470 Gaming Plus MAX.

lspci -vnnt:
> -[0000:00]-+-00.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-0fh) Root Complex [1022:1450]
> +-00.2 Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-0fh) I/O Memory Management Unit [1022:1451]
> +-01.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
> +-01.1-[01]----00.0 Samsung Electronics Co Ltd NVMe SSD
> Controller SM981/PM981/PM983 [144d:a808]
> +-01.3-[03-26]--+-00.0 Advanced Micro Devices, Inc. [AMD] Device
> [1022:43d0]
> | +-00.1 Advanced Micro Devices, Inc. [AMD] 400
> Series Chipset SATA Controller [1022:43c8]
> | \-00.2-[20-26]--+-00.0-[21]--
> | +-01.0-[22]----00.0 Realtek
> Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit
> Ethernet Controller [10ec:8168]
> | +-02.0-[23]--
> | +-03.0-[24]--
> | +-04.0-[25]--
> | \-08.0-[26]----00.0 ASMedia
> Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
> +-02.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
> +-03.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
> +-03.1-[27]--+-00.0 Advanced Micro Devices, Inc. [AMD/ATI]
> Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df]
> | \-00.1 Advanced Micro Devices, Inc. [AMD/ATI]
> Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] [1002:aaf0]
> +-04.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
> +-07.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
> +-07.1-[28]--+-00.0 Advanced Micro Devices, Inc. [AMD]
> Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a]
> | +-00.2 Advanced Micro Devices, Inc. [AMD] Family 17h
> (Models 00h-0fh) Platform Security Processor [1022:1456]
> | \-00.3 Advanced Micro Devices, Inc. [AMD] Zeppelin
> USB 3.0 Host controller [1022:145f]
> +-08.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
> +-08.1-[29]--+-00.0 Advance...

Created attachment 295151
Dmesg of a Toshiba USB 3.0 HDD connected to USB 3.0 front port and back port.

I am having this error on Linux 5.10.10-051010 while trying to connect a USB 3.0 hard disk, Toshiba Touro 4TB (HitachiGST). If I connect the disk to a USB 2.0 port it works flawlessly.

The kernel shows a different kind of error depending on whether I connect the HDD to the front or back USB 3.0 ports of the motherboard MSI X470 Gaming Plus MAX.

lspci -vnnt:
> -[0000:00]-+-00.0  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-0fh) Root Complex [1022:1450]
>            +-00.2  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-0fh) I/O Memory Management Unit [1022:1451]
>            +-01.0  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-1fh) PCIe Dummy Host Bridge [1022:1452]
>            +-01.1-[01]----00.0  Samsung Electronics Co Ltd NVMe SSD
>            Controller SM981/PM981/PM983 [144d:a808]
>            +-01.3-[03-26]--+-00.0  Advanced Micro Devices, Inc. [AMD] Device
>            [1022:43d0]
>            |               +-00.1  Advanced Micro Devices, Inc. [AMD] 400
>            Series Chipset SATA Controller [1022:43c8]
>            |               \-00.2-[20-26]--+-00.0-[21]--
>            |                               +-01.0-[22]----00.0  Realtek
>            Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit
>            Ethernet Controller [10ec:8168]
>            |                               +-02.0-[23]--
>            |                               +-03.0-[24]--
>            |                               +-04.0-[25]--
>            |                               \-08.0-[26]----00.0  ASMedia
>            Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
>            +-02.0  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-1fh) PCIe Dummy Host Bridge [1022:1452]
>            +-03.0  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-1fh) PCIe Dummy Host Bridge [1022:1452]
>            +-03.1-[27]--+-00.0  Advanced Micro Devices, Inc. [AMD/ATI]
>            Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df]
>            |            \-00.1  Advanced Micro Devices, Inc. [AMD/ATI]
>            Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] [1002:aaf0]
>            +-04.0  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-1fh) PCIe Dummy Host Bridge [1022:1452]
>            +-07.0  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-1fh) PCIe Dummy Host Bridge [1022:1452]
>            +-07.1-[28]--+-00.0  Advanced Micro Devices, Inc. [AMD]
>            Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a]
>            |            +-00.2  Advanced Micro Devices, Inc. [AMD] Family 17h
>            (Models 00h-0fh) Platform Security Processor [1022:1456]
>            |            \-00.3  Advanced Micro Devices, Inc. [AMD] Zeppelin
>            USB 3.0 Host controller [1022:145f]
>            +-08.0  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-1fh) PCIe Dummy Host Bridge [1022:1452]
>            +-08.1-[29]--+-00.0  Advanced Micro Devices, Inc. [AMD]
>            Zeppelin/Renoir PCIe Dummy Function [1022:1455]
>            |            +-00.2  Advanced Micro Devices, Inc. [AMD] FCH SATA
>            Controller [AHCI mode] [1022:7901]
>            |            \-00.3  Advanced Micro Devices, Inc. [AMD] Family 17h
>            (Models 00h-0fh) HD Audio Controller [1022:1457]
>            +-14.0  Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller
>            [1022:790b]
>            +-14.3  Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge
>            [1022:790e]
>            +-18.0  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1460]
>            +-18.1  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1461]
>            +-18.2  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1462]
>            +-18.3  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1463]
>            +-18.4  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1464]
>            +-18.5  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1465]
>            +-18.6  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466]
>            \-18.7  Advanced Micro Devices, Inc. [AMD] Family 17h (Models
>            00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467]

lsusb -vt:
> /:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>     ID 1d6b:0003 Linux Foundation 3.0 root hub
>     |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
>         ID 4971:1015 SimpleTech 
> /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
>     ID 1d6b:0002 Linux Foundation 2.0 root hub
> /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
>     ID 1d6b:0003 Linux Foundation 3.0 root hub
> /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
>     ID 1d6b:0002 Linux Foundation 2.0 root hub
> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 10000M
>     ID 1d6b:0003 Linux Foundation 3.0 root hub
> /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>     ID 1d6b:0002 Linux Foundation 2.0 root hub
>     |__ Port 4: Dev 2, If 0, Class=Vendor Specific Class,
>     Driver=dvb_usb_af9035, 480M
>         ID 07ca:1835 AVerMedia Technologies, Inc. 
>     |__ Port 12: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid,
>     1.5M
>         ID 04d9:1818 Holtek Semiconductor, Inc. Keyboard [Diatec Filco
>         Majestouch 2]
>     |__ Port 12: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid,
>     1.5M
>         ID 04d9:1818 Holtek Semiconductor, Inc. Keyboard [Diatec Filco
>         Majestouch 2]
>     |__ Port 13: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid,
>     12M
>         ID 046d:c066 Logitech, Inc. G9x Laser Mouse
>     |__ Port 13: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid,
>     12M
>         ID 046d:c066 Logitech, Inc. G9x Laser Mouse

Revision history for this message

In Linux Kernel Bug Tracker #202541, raulvior.bcn (raulvior.bcn-linux-kernel-bugs) wrote on 2021-02-10:

#259

Created attachment 295183
Dmesg of a OnePlus 7 Pro connecting in USB 3.1 gen1 mode. No errors.

(In reply to raul from comment #191)
Connecting a Oneplus 7 Pro smartphone does show any error. This phone has a USB 3.1 gen1 port and connects in that mode without errors. I can navigate the filesystem as one would expect.

Bug Watch Updater (bug-watch-updater) on 2021-03-22

Changed in linux:
importance:	Unknown → High
status:	Unknown → Confirmed

Revision history for this message

In Linux Kernel Bug Tracker #202541, tisaak (tisaak-linux-kernel-bugs) wrote on 2021-03-27:

#260

Same issue with a Seagate Portable 4 TB USB 3.0 drive that I connect with usb-storage quirks as its UAS implementation is problematic. Random hangs that flood dmesg with errors.

lsusb -tv
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
        ID 0bc2:231a Seagate RSS LLC Expansion Portable

Errors in dmesg start like this...

xhci_hcd 0000:00:10.0: WARN Cannot submit Set TR Deq Ptr
xhci_hcd 0000:00:10.0: A Set TR Deq Ptr command is pending.
usb 3-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
sd 5:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=31s
sd 5:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 a4 01 ed 78 00 00 00 10 00 00

After that:

task:usb-storage state:D stack: 0 pid: 286 ppid: 2 flags:0x00004000
Call Trace:
  __schedule+0x282/0x870
  ? usleep_range+0x80/0x80
  schedule+0x46/0xb0
  schedule_timeout+0xff/0x140
  ? __prepare_to_swait+0x4b/0x70
  __wait_for_common+0xae/0x160
  usb_sg_wait+0xe0/0x1a0 [usbcore]
  usb_stor_bulk_transfer_sglist.part.0+0x64/0xb0 [usb_storage]
  usb_stor_Bulk_transport+0x188/0x410 [usb_storage]
  usb_stor_invoke_transport+0x3a/0x520 [usb_storage]
  ? __prepare_to_swait+0x4b/0x70
  ? __wait_for_common+0xed/0x160
  usb_stor_control_thread+0x185/0x280 [usb_storage]
  ? storage_probe+0x2a0/0x2a0 [usb_storage]
  kthread+0x11b/0x140
  ? __kthread_bind_mask+0x60/0x60
  ret_from_fork+0x22/0x30

Revision history for this message

In Linux Kernel Bug Tracker #202541, mathias.nyman (mathias.nyman-linux-kernel-bugs) wrote on 2021-03-30:

#261

(In reply to Zak from comment #193)
>
>
> Errors in dmesg start like this...
>
> xhci_hcd 0000:00:10.0: WARN Cannot submit Set TR Deq Ptr
> xhci_hcd 0000:00:10.0: A Set TR Deq Ptr command is pending.

There are recent major changes in this area in the xhci driver.
The above message no longer exists, new message in this case is
"Set TR Deq already pending, don't submit for x"

Can you try this on a 5.12-rc kernel?

Thanks
Mathias

Revision history for this message

In Linux Kernel Bug Tracker #202541, mlkcampion (mlkcampion-linux-kernel-bugs) wrote on 2021-04-06:

#262

Created attachment 296259
xhci no soft retry for Intel xhci 8086:06ed and 8086:31a8

Hi

I am having this issue on 2 systems when I plug in
a Hoco Hub HB16. The Hoco Hub HB16 is a 6 in 1 adapter that
includes
Type-C to USB3.0 x3
Type-C to HDMI
Type-C to RJ45 Ethernet (RealTek RTL8153, linux loads driver rtl8153b-2)
Type-C to Type-C(PD2.0)
USB Billboard device

Also when the device is plugged into a Windows10 machine
for the first time it presents a disk that contains the RTL8153
drivers, the user is provided with an option to install these. This
"disk" is not visible later.

The 2 systems where this device failed both reported
"WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state."
Both systems have Ubuntu Mate 20.10

$ uname -a
5.8.0-48-generic #54-Ubuntu SMP Fri Mar 19 14:25:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

1. Dell XPS 9500 (Intel(R) Core(TM) i5-10300H CPU @ 2.50GHz)
$ sudo lspci -k -nn | grep -B2 xhci
00:14.0 USB controller [0c03]: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller [8086:06ed]
Subsystem: Dell Comet Lake USB 3.1 xHCI Host Controller [1028:097d]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
--
7:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
Subsystem: Dell JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [1028:097d]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

2. Seed Studio Odyssey J4105 (Intel(R) Celeron(R) J4105 CPU @ 1.50GHz)
$ sudo lspci -k -nn | grep -B3 xhci
00:15.0 USB controller [0c03]: Intel Corporation Device [8086:31a8] (rev 03)
DeviceName: Onboard - Other
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

I applied the changes in Stanislaw's patch at comment 176, I added the
PCI IDs to match both my systems.

I can confirm that with the patch applied both systems no longer reported the
issue ""WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state."

Just to note that on the Dell XPS I use the Dell DA20 Adapter which is a Type-C
to USB and HDMI adapter. This appears to have an ASIX Elec. Corp. AX88179
USB 3.0 to Gigabit Ethernet which I don't have any issues with.

Created attachment 296259
xhci no soft retry for Intel xhci 8086:06ed and 8086:31a8

Hi

I am having this issue on 2 systems when I plug in 
a Hoco Hub HB16. The Hoco Hub HB16 is a 6 in 1 adapter that
includes 
Type-C to USB3.0 x3
Type-C to HDMI
Type-C to RJ45 Ethernet (RealTek RTL8153, linux loads driver rtl8153b-2)
Type-C to Type-C(PD2.0)
USB Billboard device

Also when the device is plugged into a Windows10 machine
for the first time it presents a disk that contains the RTL8153
drivers, the user is provided with an option to install these. This
"disk" is not visible later.

The 2 systems where this device failed both reported
"WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state."
Both systems have Ubuntu Mate 20.10

$ uname -a
5.8.0-48-generic #54-Ubuntu SMP Fri Mar 19 14:25:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

1. Dell XPS 9500 (Intel(R) Core(TM) i5-10300H CPU @ 2.50GHz)
$ sudo lspci -k -nn | grep -B2 xhci
    00:14.0 USB controller [0c03]: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller [8086:06ed]
	Subsystem: Dell Comet Lake USB 3.1 xHCI Host Controller [1028:097d]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
--
    7:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
	Subsystem: Dell JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [1028:097d]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

2. Seed Studio Odyssey J4105 (Intel(R) Celeron(R) J4105 CPU @ 1.50GHz)
$ sudo lspci -k -nn | grep -B3 xhci 
    00:15.0 USB controller [0c03]: Intel Corporation Device [8086:31a8] (rev 03)
	DeviceName: Onboard - Other
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

I applied the changes in Stanislaw's patch at comment 176, I added the
PCI IDs to match both my systems.

I can confirm that with the patch applied both systems no longer reported  the 
issue ""WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state."

Just to note that on the Dell XPS I use the Dell DA20 Adapter which is a Type-C
to USB and HDMI adapter. This appears to have an ASIX Elec. Corp. AX88179 
USB 3.0 to Gigabit Ethernet which I don't have any issues with.

Revision history for this message

In Linux Kernel Bug Tracker #202541, luke-jr+linuxbugs (luke-jr+linuxbugs-linux-kernel-bugs) wrote on 2021-05-29:

#263

Encountered this with a PCI-e card using ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller

Moved to my native "Intel Corporation Device a3af" USB bus, this error disappeared (though other problems remain in my case)

Linux 5.10.33

Of potential noteworthiness: When I got my Talos II, I tried to move this ASMedia USB PCI-e card to it, and found it was immediately shutdown by the IOMMU whenever I would try to use it at all. It seems the firmware is garbage.

IIRC, someone was getting close to an open source firmware replacement without those issues... would be interesting to see if it helps with this bug as well.

Revision history for this message

In Linux Kernel Bug Tracker #202541, dront78 (dront78-linux-kernel-bugs) wrote on 2021-06-24:

#264

Download full text (16.3 KiB)

same problem
5.12.12-arch1-1 #1 SMP PREEMPT Fri, 18 Jun 2021 21:59:22 +0000 x86_64 GNU/Linux

GPD Pocket

00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 34)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 34)
DeviceName: Onboard IGD
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: i915
Kernel modules: i915
00:0b.0 Signal processing controller [1180]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller [8086:22dc] (rev 34)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] (rev 34)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:1a.0 Encryption controller [1080]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [8086:2298] (rev 34)
Subsystem: Intel Corporation Device [8086:7270]
Kernel modules: mei_txe
00:1c.0 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 [8086:22c8] (rev 34)
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU [8086:229c] (rev 34)
Subsystem: Intel Corporation Device [8086:7270]
Kernel modules: lpc_ich
01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
Subsystem: Gemtek Technology Co., Ltd Device [17f9:0036]
Kernel driver in use: brcmfmac
Kernel modules: brcmfmac

# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x5B8DE000.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 5.11
Release Date: 06/28/2017
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4 MB
Characteristics:
  PCI is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  BIOS ROM is socketed
  EDD is supported
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 kB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  BIOS boot specification is supported
  Targeted content distribution is supported
  UEFI is supported
BIOS Revision: 5.11

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Default string
Product Name: Default string
Version: Default string
Serial Number: Default string
UUID: 03000200-0400-0500-0006-000700080009
Wake-up ...

same problem
5.12.12-arch1-1 #1 SMP PREEMPT Fri, 18 Jun 2021 21:59:22 +0000 x86_64 GNU/Linux

GPD Pocket

00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 34)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 34)
	DeviceName:  Onboard IGD
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: i915
	Kernel modules: i915
00:0b.0 Signal processing controller [1180]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller [8086:22dc] (rev 34)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: proc_thermal
	Kernel modules: processor_thermal_device
00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] (rev 34)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:1a.0 Encryption controller [1080]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [8086:2298] (rev 34)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel modules: mei_txe
00:1c.0 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 [8086:22c8] (rev 34)
	Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU [8086:229c] (rev 34)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel modules: lpc_ich
01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
	Subsystem: Gemtek Technology Co., Ltd Device [17f9:0036]
	Kernel driver in use: brcmfmac
	Kernel modules: brcmfmac

# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x5B8DE000.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: American Megatrends Inc.
	Version: 5.11
	Release Date: 06/28/2017
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 4 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 5.11

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: Default string
	Product Name: Default string
	Version: Default string
	Serial Number: Default string
	UUID: 03000200-0400-0500-0006-000700080009
	Wake-up Type: Power Switch
	SKU Number: Default string
	Family: Default string

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: AMI Corporation
	Product Name: Default string
	Version: Default string
	Serial Number: Default string
	Asset Tag: Default string
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Default string
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
	Manufacturer: Default string
	Type: Desktop
	Lock: Not Present
	Version: Default string
	Serial Number: Default string
	Asset Tag: Default string
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0
	SKU Number: Default string

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J1A1
	Internal Connector Type: None
	External Reference Designator: PS2Mouse
	External Connector Type: PS/2
	Port Type: Mouse Port

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J1A1
	Internal Connector Type: None
	External Reference Designator: Keyboard
	External Connector Type: PS/2
	Port Type: Keyboard Port

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J2A1
	Internal Connector Type: None
	External Reference Designator: TV Out
	External Connector Type: Mini Centronics Type-14
	Port Type: Other

Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J2A2A
	Internal Connector Type: None
	External Reference Designator: COM A
	External Connector Type: DB-9 male
	Port Type: Serial Port 16550A Compatible

Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J2A2B
	Internal Connector Type: None
	External Reference Designator: Video
	External Connector Type: DB-15 female
	Port Type: Video Port

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J3A1
	Internal Connector Type: None
	External Reference Designator: USB1
	External Connector Type: Access Bus (USB)
	Port Type: USB

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J3A1
	Internal Connector Type: None
	External Reference Designator: USB2
	External Connector Type: Access Bus (USB)
	Port Type: USB

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J3A1
	Internal Connector Type: None
	External Reference Designator: USB3
	External Connector Type: Access Bus (USB)
	Port Type: USB

Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J9A1 - TPM HDR
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J9C1 - PCIE DOCKING CONN
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J2B3 - CPU FAN
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J6C2 - EXT HDMI
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J3C1 - GMCH FAN
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J1D1 - ITP
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J9E2 - MDC INTPSR
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J9E4 - MDC INTPSR
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0018, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J9E3 - LPC HOT DOCKING
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0019, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J9E1 - SCAN MATRIX
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x001A, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J9G1 - LPC SIDE BAND
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x001B, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J8F1 - UNIFIED
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x001C, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J6F1 - LVDS
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x001D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J2F1 - LAI FAN
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x001E, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J2G1 - GFX VID
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x001F, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: J1G6 - AC JACK
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0020, DMI type 9, 17 bytes
System Slot Information
	Designation: J6B2
	Type: x16 PCI Express
	Current Usage: In Use
	Length: Long
	ID: 0
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported
	Bus Address: 0000:00:01.0

Handle 0x0021, DMI type 9, 17 bytes
System Slot Information
	Designation: J6B1
	Type: x1 PCI Express
	Current Usage: In Use
	Length: Short
	ID: 1
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported
	Bus Address: 0000:00:1c.3

Handle 0x0022, DMI type 9, 17 bytes
System Slot Information
	Designation: J6D1
	Type: x1 PCI Express
	Current Usage: In Use
	Length: Short
	ID: 2
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported
	Bus Address: 0000:00:1c.4

Handle 0x0023, DMI type 9, 17 bytes
System Slot Information
	Designation: J7B1
	Type: x1 PCI Express
	Current Usage: In Use
	Length: Short
	ID: 3
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported
	Bus Address: 0000:00:1c.5

Handle 0x0024, DMI type 9, 17 bytes
System Slot Information
	Designation: J8B4
	Type: x1 PCI Express
	Current Usage: In Use
	Length: Short
	ID: 4
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported
	Bus Address: 0000:00:1c.6

Handle 0x0025, DMI type 10, 6 bytes
On Board Device Information
	Type: Video
	Status: Enabled
	Description:    To Be Filled By O.E.M.

Handle 0x0026, DMI type 11, 5 bytes
OEM Strings
	String 1: Default string

Handle 0x0027, DMI type 12, 5 bytes
System Configuration Options
	Option 1: Default string

Handle 0x0028, DMI type 16, 23 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: Multi-bit ECC
	Maximum Capacity: 8 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x0029, DMI type 19, 31 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x001FFFFFFFF
	Range Size: 8 GB
	Physical Array Handle: 0x0028
	Partition Width: 2

Handle 0x002A, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0028
	Error Information Handle: Not Provided
	Total Width: 8 bits
	Data Width: 64 bits
	Size: 4 GB
	Form Factor: DIMM
	Set: None
	Locator: A1_DIMM0
	Bank Locator: A1_BANK0
	Type: DDR3
	Type Detail: Unknown
	Speed: 1600 MT/s
	Manufacturer: Hynix Semiconductor
	Serial Number: 00000000
	Asset Tag: 00000000
	Part Number: 00000000
	Rank: Unknown
	Configured Memory Speed: 1600 MT/s
	Minimum Voltage: 1.5 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V

Handle 0x002B, DMI type 20, 35 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000FFFFFFFF
	Range Size: 4 GB
	Physical Device Handle: 0x002A
	Memory Array Mapped Address Handle: 0x0029
	Partition Row Position: Unknown
	Interleave Position: 1
	Interleaved Data Depth: 2

Handle 0x002C, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0028
	Error Information Handle: Not Provided
	Total Width: 8 bits
	Data Width: 64 bits
	Size: 4 GB
	Form Factor: DIMM
	Set: None
	Locator: A1_DIMM1
	Bank Locator: A1_BANK1
	Type: DDR3
	Type Detail: Unknown
	Speed: 1600 MT/s
	Manufacturer: Hynix Semiconductor
	Serial Number: 00000000
	Asset Tag: 00000000
	Part Number: 00000000
	Rank: Unknown
	Configured Memory Speed: 1600 MT/s
	Minimum Voltage: 1.5 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V

Handle 0x002D, DMI type 20, 35 bytes
Memory Device Mapped Address
	Starting Address: 0x00100000000
	Ending Address: 0x001FFFFFFFF
	Range Size: 4 GB
	Physical Device Handle: 0x002C
	Memory Array Mapped Address Handle: 0x0029
	Partition Row Position: Unknown
	Interleave Position: 2
	Interleaved Data Depth: 2

Handle 0x002E, DMI type 32, 20 bytes
System Boot Information
	Status: No errors detected

Handle 0x002F, DMI type 41, 11 bytes
Onboard Device
	Reference Designation:  Onboard IGD
	Type: Video
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:02.0

Handle 0x0030, DMI type 41, 11 bytes
Onboard Device
	Reference Designation:  Onboard LAN
	Type: Ethernet
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:19.0

Handle 0x0031, DMI type 41, 11 bytes
Onboard Device
	Reference Designation:  Onboard 1394
	Type: Other
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:03:1c.2

Handle 0x0032, DMI type 7, 19 bytes
Cache Information
	Socket Designation: CPU Internal L1
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 224 kB
	Maximum Size: 224 kB
	Supported SRAM Types:
		Unknown
	Installed SRAM Type: Unknown
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Other
	Associativity: Other

Handle 0x0033, DMI type 7, 19 bytes
Cache Information
	Socket Designation: CPU Internal L2
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 2 MB
	Maximum Size: 2 MB
	Supported SRAM Types:
		Unknown
	Installed SRAM Type: Unknown
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: 16-way Set-associative

Handle 0x0034, DMI type 4, 48 bytes
Processor Information
	Socket Designation: SOCKET 0
	Type: Central Processor
	Family: Atom
	Manufacturer: Intel
	ID: C4 06 04 00 FF FB EB BF
	Signature: Type 0, Family 6, Model 76, Stepping 4
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz
	Voltage: 1.2 V
	External Clock: 80 MHz
	Max Speed: 2400 MHz
	Current Speed: 1600 MHz
	Status: Populated, Enabled
	Upgrade: Socket BGA1155
	L1 Cache Handle: 0x0032
	L2 Cache Handle: 0x0033
	L3 Cache Handle: Not Provided
	Serial Number: Not Specified
	Asset Tag: Fill By OEM
	Part Number: Fill By OEM
	Core Count: 4
	Core Enabled: 4
	Thread Count: 4
	Characteristics:
		64-bit capable

Handle 0x0035, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 1
		en|US|iso8859-1
	Currently Installed Language: en|US|iso8859-1

Handle 0x0036, DMI type 127, 4 bytes
End Of Table

Guilherme G. Piccoli (gpiccoli) on 2021-07-20

Changed in linux (Debian):
assignee:	Guilherme G. Piccoli (gpiccoli) → nobody
Changed in linux (Ubuntu):
assignee:	Guilherme G. Piccoli (gpiccoli) → nobody
Changed in linux (Ubuntu Trusty):
assignee:	Guilherme G. Piccoli (gpiccoli) → nobody
Changed in linux (Ubuntu Bionic):
assignee:	Guilherme G. Piccoli (gpiccoli) → nobody
Changed in linux (Ubuntu Focal):
assignee:	Guilherme G. Piccoli (gpiccoli) → nobody
Changed in linux (Ubuntu Xenial):
assignee:	Guilherme G. Piccoli (gpiccoli) → nobody

Revision history for this message

In Linux Kernel Bug Tracker #202541, antdev66 (antdev66-linux-kernel-bugs) wrote on 2021-08-24:

#265

I have same problem with kernels 5.13.12 and 5.14.0-rc7:

dmesg:
xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.

journalctl:
ago 24 18:38:40 SERVER kernel: sd 4:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s

Revision history for this message

In Linux Kernel Bug Tracker #202541, stulluk (stulluk-linux-kernel-bugs) wrote on 2021-09-15:

#266

I also experience exactly same issue on multiple USB devices ( USB-WIFI or a USB-Webcam ) only on my brand new AMD Mainboard ( ASRock model: B550M-HDV)

I tried both ubuntu focal and hirsute with latest kernels on my OldPC (ASUSTeK model: M5A78L-M LX3) and on my IntelNUC (NUC8BEB) and this issue does not happen (Tried with same USB-WIFI and USB-Webcam devices).

Issue is easily reproducible by inserting USB-WIFI and then executing "ip a" on a shell.

Revision history for this message

In Linux Kernel Bug Tracker #202541, dion (dion-linux-kernel-bugs) wrote on 2021-09-18:

#267

Download full text (3.6 KiB)

I also have exactly same problem, but with a bit different HW.

Now it's USB DAC branded as "Qudelix-5K". As far as I understand it's USB1 device.

[ 174.358189] usb 5-2.3.2.2.1.1: new full-speed USB device number 17 using xhci_hcd
[ 174.475229] usb 5-2.3.2.2.1.1: New USB device found, idVendor=0a12, idProduct=4025, bcdDevice=19.70
[ 174.475232] usb 5-2.3.2.2.1.1: New USB device strings: Mfr=1, Product=8, SerialNumber=3
[ 174.475233] usb 5-2.3.2.2.1.1: Product: Qudelix-5K USB DAC/MIC 48KHz
[ 174.475234] usb 5-2.3.2.2.1.1: Manufacturer: QTIL
[ 174.475235] usb 5-2.3.2.2.1.1: SerialNumber: ABCDEF0123456789

It produces corrupted sound (actually some noise) just after a few seconds of playback if connected to Dell WD19TB thunderbolt dock station. Issue happens with USB-A ports on dock plus one Type-C port (front). Second Type-C port (named as "Type-C with Thunderbolt 3 port" works.

When such noise happens I'm getting followed in dmesg:

xhci_hcd 0000:3a:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 5 comp_code 1
xhci_hcd 0000:3a:00.0: Looking for event-dma 00000000ffe940f0 trb-start 00000000ffe94100 trb-end 00000000ffe94100 seg-start 00000000ffe94000 seg-end 00000000ffe94ff0
xhci_hcd 0000:3a:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 5 comp_code 1
xhci_hcd 0000:3a:00.0: Looking for event-dma 00000000ffe949b0 trb-start 00000000ffe949c0 trb-end 00000000ffe949c0 seg-start 00000000ffe94000 seg-end 00000000ffe94ff0

I've tried to add/remove extra USB hubs (originally Qudelix was plugged to internal USB3 hub of monitor). But even if plugged directly to dock, it produces corrupted sound.

Another important thing: this dock has built-in Ethernet with r8153 chipset like mentioned above.

After reading comments here I've tried to disable soft retry using followed patch:

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index 1c9a7957c45c..07cbcf50160c 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -189,10 +189,11 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)

        if (pdev->vendor == PCI_VENDOR_ID_INTEL) {
                xhci->quirks |= XHCI_LPM_SUPPORT;
                xhci->quirks |= XHCI_INTEL_HOST;
                xhci->quirks |= XHCI_AVOID_BEI;
+ xhci->quirks |= XHCI_NO_SOFT_RETRY;
        }
        if (pdev->vendor == PCI_VENDOR_ID_INTEL &&
                        pdev->device == PCI_DEVICE_ID_INTEL_PANTHERPOINT_XHCI) {
                xhci->quirks |= XHCI_EP_LIMIT_QUIRK;
                xhci->limit_active_eps = 64;

And it completely fixed issue for me. DAC produces clear sound even if connected through chain of two hubs!

PS.
lspci -k -nn | grep -B2 xhci
00:14.0 USB controller [0c03]: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller [8086:02ed]
        Subsystem: Hewlett-Packard Company Comet Lake PCH-LP USB 3.1 xHCI Host Controller [103c:8724]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
--
37:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
        Subsystem: Hewlett-P...

I also have exactly same problem, but with a bit different HW.

Now it's USB DAC branded as "Qudelix-5K". As far as I understand it's USB1 device.

[  174.358189] usb 5-2.3.2.2.1.1: new full-speed USB device number 17 using xhci_hcd
[  174.475229] usb 5-2.3.2.2.1.1: New USB device found, idVendor=0a12, idProduct=4025, bcdDevice=19.70
[  174.475232] usb 5-2.3.2.2.1.1: New USB device strings: Mfr=1, Product=8, SerialNumber=3
[  174.475233] usb 5-2.3.2.2.1.1: Product: Qudelix-5K USB DAC/MIC 48KHz
[  174.475234] usb 5-2.3.2.2.1.1: Manufacturer: QTIL
[  174.475235] usb 5-2.3.2.2.1.1: SerialNumber: ABCDEF0123456789

It produces corrupted sound (actually some noise) just after a few seconds of playback if connected to Dell WD19TB thunderbolt dock station. Issue happens with USB-A ports on dock plus one Type-C port (front). Second Type-C port (named as "Type-C with Thunderbolt 3 port" works.

When such noise happens I'm getting followed in dmesg:

xhci_hcd 0000:3a:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 5 comp_code 1
xhci_hcd 0000:3a:00.0: Looking for event-dma 00000000ffe940f0 trb-start 00000000ffe94100 trb-end 00000000ffe94100 seg-start 00000000ffe94000 seg-end 00000000ffe94ff0
xhci_hcd 0000:3a:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 5 comp_code 1
xhci_hcd 0000:3a:00.0: Looking for event-dma 00000000ffe949b0 trb-start 00000000ffe949c0 trb-end 00000000ffe949c0 seg-start 00000000ffe94000 seg-end 00000000ffe94ff0

I've tried to add/remove extra USB hubs (originally Qudelix was plugged to internal USB3 hub of monitor). But even if plugged directly to dock, it produces corrupted sound.

Another important thing: this dock has built-in Ethernet with r8153 chipset like mentioned above.

After reading comments here I've tried to disable soft retry using followed patch:

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index 1c9a7957c45c..07cbcf50160c 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -189,10 +189,11 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)
 
        if (pdev->vendor == PCI_VENDOR_ID_INTEL) {
                xhci->quirks |= XHCI_LPM_SUPPORT;
                xhci->quirks |= XHCI_INTEL_HOST;
                xhci->quirks |= XHCI_AVOID_BEI;
+               xhci->quirks |= XHCI_NO_SOFT_RETRY;
        }
        if (pdev->vendor == PCI_VENDOR_ID_INTEL &&
                        pdev->device == PCI_DEVICE_ID_INTEL_PANTHERPOINT_XHCI) {
                xhci->quirks |= XHCI_EP_LIMIT_QUIRK;
                xhci->limit_active_eps = 64;

And it completely fixed issue for me. DAC produces clear sound even if connected through chain of two hubs!

PS. 
lspci -k -nn | grep -B2 xhci 
00:14.0 USB controller [0c03]: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller [8086:02ed]
        Subsystem: Hewlett-Packard Company Comet Lake PCH-LP USB 3.1 xHCI Host Controller [103c:8724]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
--
37:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
        Subsystem: Hewlett-Packard Company JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [103c:8723]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
--
3a:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge DD 2018] [8086:15f0] (rev 06)
        Subsystem: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge DD 2018] [8086:0000]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci

5.14.6 kernel

Hope that this will help to fix it

Revision history for this message

In Linux Kernel Bug Tracker #202541, raulvior.bcn (raulvior.bcn-linux-kernel-bugs) wrote on 2022-06-21:

#268

Turns out the problem was the cable, it was too long. A shorter USB 3.0 cable (1.8m) allowed a stable connection. On the same Linux 5.13 (the previous dmesg was on Linux 5.10) the longer 3 meters cable kept failing while with the 1.8 meters cable the HDD works without issue.

(In reply to raul from comment #191)

Revision history for this message

In Linux Kernel Bug Tracker #202541, S.Braendlin (s.braendlin-linux-kernel-bugs) wrote on 2022-08-06:

#269

Hi,
I have also issues with USB3 on my Debian 10 with kernel 5.10.0-0.bpo.5-amd64 which is not appearing when using USB2 port:

Aug 6 13:20:14 media-server kernel: [ 964.069355] scsi host17: uas_eh_device_reset_handler start
Aug 6 13:20:14 media-server kernel: [ 964.197532] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Aug 6 13:20:14 media-server kernel: [ 964.219053] scsi host17: uas_eh_device_reset_handler success
Aug 6 13:20:18 media-server kernel: [ 968.137601] task:sync state:D stack: 0 pid:12237 ppid: 11291 flags:0x00004324
Aug 6 13:20:18 media-server kernel: [ 968.137607] Call Trace:
Aug 6 13:20:18 media-server kernel: [ 968.137621] __schedule+0x2be/0x770
Aug 6 13:20:18 media-server kernel: [ 968.137630] schedule+0x3c/0xa0
Aug 6 13:20:18 media-server kernel: [ 968.137635] io_schedule+0x12/0x40
Aug 6 13:20:18 media-server kernel: [ 968.137644] wait_on_page_bit+0x127/0x230
Aug 6 13:20:18 media-server kernel: [ 968.137651] ? __page_cache_alloc+0x80/0x80
Aug 6 13:20:18 media-server kernel: [ 968.137657] wait_on_page_writeback+0x25/0x70
Aug 6 13:20:18 media-server kernel: [ 968.137663] __filemap_fdatawait_range+0x89/0xf0
Aug 6 13:20:18 media-server kernel: [ 968.137673] ? sync_inodes_one_sb+0x20/0x20
Aug 6 13:20:18 media-server kernel: [ 968.137679] filemap_fdatawait_keep_errors+0x1a/0x40
Aug 6 13:20:18 media-server kernel: [ 968.137684] iterate_bdevs+0xad/0x150
Aug 6 13:20:18 media-server kernel: [ 968.137691] ksys_sync+0x7c/0xb0
Aug 6 13:20:18 media-server kernel: [ 968.137697] __do_sys_sync+0xa/0x10
Aug 6 13:20:18 media-server kernel: [ 968.137704] do_syscall_64+0x33/0x80
Aug 6 13:20:18 media-server kernel: [ 968.137709] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 6 13:20:18 media-server kernel: [ 968.137714] RIP: 0033:0x7fc4ec0529aa
Aug 6 13:20:18 media-server kernel: [ 968.137717] RSP: 002b:00007ffcddf49048 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
Aug 6 13:20:18 media-server kernel: [ 968.137723] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc4ec0529aa
Aug 6 13:20:18 media-server kernel: [ 968.137725] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 00000000a8002000
Aug 6 13:20:18 media-server kernel: [ 968.137728] RBP: 0000000000000000 R08: 0000555ba9703dcf R09: 00007ffcddf4afe2
Aug 6 13:20:18 media-server kernel: [ 968.137730] R10: 00007fc4ec01a201 R11: 0000000000000246 R12: 0000000000000001
Aug 6 13:20:18 media-server kernel: [ 968.137733] R13: 0000000000000001 R14: 00007ffcddf49158 R15: 0000000000000000

Hi,
I have also issues with USB3 on my Debian 10 with kernel 5.10.0-0.bpo.5-amd64 which is not appearing when using USB2 port:

Aug  6 13:20:14 media-server kernel: [  964.069355] scsi host17: uas_eh_device_reset_handler start
Aug  6 13:20:14 media-server kernel: [  964.197532] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Aug  6 13:20:14 media-server kernel: [  964.219053] scsi host17: uas_eh_device_reset_handler success
Aug  6 13:20:18 media-server kernel: [  968.137601] task:sync            state:D stack:    0 pid:12237 ppid: 11291 flags:0x00004324
Aug  6 13:20:18 media-server kernel: [  968.137607] Call Trace:
Aug  6 13:20:18 media-server kernel: [  968.137621]  __schedule+0x2be/0x770
Aug  6 13:20:18 media-server kernel: [  968.137630]  schedule+0x3c/0xa0
Aug  6 13:20:18 media-server kernel: [  968.137635]  io_schedule+0x12/0x40
Aug  6 13:20:18 media-server kernel: [  968.137644]  wait_on_page_bit+0x127/0x230
Aug  6 13:20:18 media-server kernel: [  968.137651]  ? __page_cache_alloc+0x80/0x80
Aug  6 13:20:18 media-server kernel: [  968.137657]  wait_on_page_writeback+0x25/0x70
Aug  6 13:20:18 media-server kernel: [  968.137663]  __filemap_fdatawait_range+0x89/0xf0
Aug  6 13:20:18 media-server kernel: [  968.137673]  ? sync_inodes_one_sb+0x20/0x20
Aug  6 13:20:18 media-server kernel: [  968.137679]  filemap_fdatawait_keep_errors+0x1a/0x40
Aug  6 13:20:18 media-server kernel: [  968.137684]  iterate_bdevs+0xad/0x150
Aug  6 13:20:18 media-server kernel: [  968.137691]  ksys_sync+0x7c/0xb0
Aug  6 13:20:18 media-server kernel: [  968.137697]  __do_sys_sync+0xa/0x10
Aug  6 13:20:18 media-server kernel: [  968.137704]  do_syscall_64+0x33/0x80
Aug  6 13:20:18 media-server kernel: [  968.137709]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug  6 13:20:18 media-server kernel: [  968.137714] RIP: 0033:0x7fc4ec0529aa
Aug  6 13:20:18 media-server kernel: [  968.137717] RSP: 002b:00007ffcddf49048 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
Aug  6 13:20:18 media-server kernel: [  968.137723] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc4ec0529aa
Aug  6 13:20:18 media-server kernel: [  968.137725] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 00000000a8002000
Aug  6 13:20:18 media-server kernel: [  968.137728] RBP: 0000000000000000 R08: 0000555ba9703dcf R09: 00007ffcddf4afe2
Aug  6 13:20:18 media-server kernel: [  968.137730] R10: 00007fc4ec01a201 R11: 0000000000000246 R12: 0000000000000001
Aug  6 13:20:18 media-server kernel: [  968.137733] R13: 0000000000000001 R14: 00007ffcddf49158 R15: 0000000000000000

Revision history for this message

In Linux Kernel Bug Tracker #202541, pupilla (pupilla-linux-kernel-bugs) wrote on 2022-09-02:

#270

Download full text (45.7 KiB)

Hello everyone,

I encountered the problem with kernel 6.0.0-rc3 on a lenovo t470 laptop and a usb3 axis card. The system was started with the parameter intel_idle.max_cstate=1 and this appears to affect the possibility of the bug appearing. I have now rebooted the system without this parameter.

I have another similar setup (same laptop and same usb3 network card, but with linux 6.0.0-rc2) that has been active for 8 days started without the parameter intel_idle.max_cstate=1 and the problem has not occurred to date.

The distribution is Slackware 15 (64 bit).

This is the full output of dmesg.

Any feedback is welcome.

Marco

[ 0.000000] Linux version 6.0.0-rc3 (root@Cherepakha) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP PREEMPT_DYNAMIC Tue Aug 30 16:07:18 CEST 2022
[ 0.000000] Command line: auto BOOT_IMAGE=Linux ro root=10303 intel_idle.max_cstate=1
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[ 0.000000] signal: max sigframe size: 1616
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009cfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009d000-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000040400000-0x000000008b79bfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000008b79c000-0x0000000090652fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000090653000-0x0000000090653fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000090654000-0x000000009b52cfff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000009b52d000-0x000000009b599fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000009b59a000-0x000000009b5fefff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000009b5ff000-0x000000009f7fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00...

Hello everyone,

I encountered the problem with kernel 6.0.0-rc3 on a lenovo t470 laptop and a usb3 axis card. The system was started with the parameter intel_idle.max_cstate=1 and this appears to affect the possibility of the bug appearing. I have now rebooted the system without this parameter.

I have another similar setup (same laptop and same usb3 network card, but with linux 6.0.0-rc2) that has been active for 8 days started without the parameter intel_idle.max_cstate=1 and the problem has not occurred to date.

The distribution is Slackware 15 (64 bit).

This is the full output of dmesg.

Any feedback is welcome.

Marco

[    0.000000] Linux version 6.0.0-rc3 (root@Cherepakha) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP PREEMPT_DYNAMIC Tue Aug 30 16:07:18 CEST 2022
[    0.000000] Command line: auto BOOT_IMAGE=Linux ro root=10303 intel_idle.max_cstate=1
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[    0.000000] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[    0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[    0.000000] signal: max sigframe size: 1616
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009cfff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009d000-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000040400000-0x000000008b79bfff] usable
[    0.000000] BIOS-e820: [mem 0x000000008b79c000-0x0000000090652fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000090653000-0x0000000090653fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000090654000-0x000000009b52cfff] reserved
[    0.000000] BIOS-e820: [mem 0x000000009b52d000-0x000000009b599fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000009b59a000-0x000000009b5fefff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000009b5ff000-0x000000009f7fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000045e7fffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 3.0.0 present.
[    0.000000] DMI: LENOVO 20HES0KW0J/20HES0KW0J, BIOS N1QET95W (1.70 ) 05/25/2022
[    0.000000] tsc: Detected 2700.000 MHz processor
[    0.000000] tsc: Detected 2699.909 MHz TSC
[    0.000825] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000828] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000835] last_pfn = 0x45e800 max_arch_pfn = 0x400000000
[    0.000956] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[    0.001753] last_pfn = 0x8b79c max_arch_pfn = 0x400000000
[    0.001759] Using GB pages for direct mapping
[    0.002199] ACPI: Early table checksum verification disabled
[    0.002201] ACPI: RSDP 0x00000000000F0140 000024 (v02 LENOVO)
[    0.002205] ACPI: XSDT 0x000000009B5C1188 000104 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002210] ACPI: FACP 0x000000009B5F5000 0000F4 (v05 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002215] ACPI: DSDT 0x000000009B5CF000 02151D (v02 LENOVO SKL      00000000 INTL 20160527)
[    0.002218] ACPI: FACS 0x000000009B53E000 000040
[    0.002220] ACPI: SSDT 0x000000009B5FC000 0003CC (v02 LENOVO Tpm2Tabl 00001000 INTL 20160527)
[    0.002223] ACPI: TPM2 0x000000009B5FB000 000034 (v03 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002226] ACPI: UEFI 0x000000009B553000 000042 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002229] ACPI: SSDT 0x000000009B5F7000 0030E4 (v02 LENOVO SaSsdt   00003000 INTL 20160527)
[    0.002232] ACPI: SSDT 0x000000009B5F6000 0005B6 (v02 LENOVO PerfTune 00001000 INTL 20160527)
[    0.002235] ACPI: HPET 0x000000009B5F4000 000038 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002238] ACPI: APIC 0x000000009B5F3000 0000BC (v03 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002240] ACPI: MCFG 0x000000009B5F2000 00003C (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002243] ACPI: ECDT 0x000000009B5F1000 000053 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002245] ACPI: SSDT 0x000000009B5CE000 00021C (v01 LENOVO Rmv_Batt 00001000 INTL 20160527)
[    0.002248] ACPI: SSDT 0x000000009B5CC000 00174F (v02 LENOVO ProjSsdt 00000010 INTL 20160527)
[    0.002251] ACPI: BOOT 0x000000009B5CB000 000028 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002254] ACPI: BATB 0x000000009B5CA000 00004A (v02 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002256] ACPI: SLIC 0x000000009B5C9000 000176 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002259] ACPI: SSDT 0x000000009B5C7000 0017AE (v02 LENOVO CpuSsdt  00003000 INTL 20160527)
[    0.002262] ACPI: SSDT 0x000000009B5C6000 00056D (v02 LENOVO CtdpB    00001000 INTL 20160527)
[    0.002264] ACPI: SSDT 0x000000009B5C5000 000634 (v02 LENOVO UsbCTabl 00001000 INTL 20160527)
[    0.002267] ACPI: WSMT 0x000000009B5C4000 000028 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002270] ACPI: SSDT 0x000000009B5C3000 000141 (v02 LENOVO HdaDsp   00000000 INTL 20160527)
[    0.002273] ACPI: SSDT 0x000000009B5C2000 0004C5 (v02 LENOVO TbtTypeC 00000000 INTL 20160527)
[    0.002275] ACPI: DBGP 0x000000009B5FD000 000034 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002278] ACPI: DBG2 0x000000009B5C0000 000054 (v00 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002281] ACPI: MSDM 0x000000009B5BF000 000055 (v03 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002283] ACPI: DMAR 0x000000009B5BE000 0000A8 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002286] ACPI: ASF! 0x000000009B5BD000 0000A0 (v32 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002289] ACPI: FPDT 0x000000009B5BC000 000044 (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002291] ACPI: UEFI 0x000000009B53B000 00013E (v01 LENOVO TP-N1Q   00001700 PTEC 00000002)
[    0.002294] ACPI: Reserving FACP table memory at [mem 0x9b5f5000-0x9b5f50f3]
[    0.002295] ACPI: Reserving DSDT table memory at [mem 0x9b5cf000-0x9b5f051c]
[    0.002297] ACPI: Reserving FACS table memory at [mem 0x9b53e000-0x9b53e03f]
[    0.002298] ACPI: Reserving SSDT table memory at [mem 0x9b5fc000-0x9b5fc3cb]
[    0.002299] ACPI: Reserving TPM2 table memory at [mem 0x9b5fb000-0x9b5fb033]
[    0.002300] ACPI: Reserving UEFI table memory at [mem 0x9b553000-0x9b553041]
[    0.002301] ACPI: Reserving SSDT table memory at [mem 0x9b5f7000-0x9b5fa0e3]
[    0.002302] ACPI: Reserving SSDT table memory at [mem 0x9b5f6000-0x9b5f65b5]
[    0.002303] ACPI: Reserving HPET table memory at [mem 0x9b5f4000-0x9b5f4037]
[    0.002304] ACPI: Reserving APIC table memory at [mem 0x9b5f3000-0x9b5f30bb]
[    0.002305] ACPI: Reserving MCFG table memory at [mem 0x9b5f2000-0x9b5f203b]
[    0.002306] ACPI: Reserving ECDT table memory at [mem 0x9b5f1000-0x9b5f1052]
[    0.002306] ACPI: Reserving SSDT table memory at [mem 0x9b5ce000-0x9b5ce21b]
[    0.002307] ACPI: Reserving SSDT table memory at [mem 0x9b5cc000-0x9b5cd74e]
[    0.002308] ACPI: Reserving BOOT table memory at [mem 0x9b5cb000-0x9b5cb027]
[    0.002309] ACPI: Reserving BATB table memory at [mem 0x9b5ca000-0x9b5ca049]
[    0.002310] ACPI: Reserving SLIC table memory at [mem 0x9b5c9000-0x9b5c9175]
[    0.002311] ACPI: Reserving SSDT table memory at [mem 0x9b5c7000-0x9b5c87ad]
[    0.002312] ACPI: Reserving SSDT table memory at [mem 0x9b5c6000-0x9b5c656c]
[    0.002313] ACPI: Reserving SSDT table memory at [mem 0x9b5c5000-0x9b5c5633]
[    0.002314] ACPI: Reserving WSMT table memory at [mem 0x9b5c4000-0x9b5c4027]
[    0.002315] ACPI: Reserving SSDT table memory at [mem 0x9b5c3000-0x9b5c3140]
[    0.002316] ACPI: Reserving SSDT table memory at [mem 0x9b5c2000-0x9b5c24c4]
[    0.002317] ACPI: Reserving DBGP table memory at [mem 0x9b5fd000-0x9b5fd033]
[    0.002319] ACPI: Reserving DBG2 table memory at [mem 0x9b5c0000-0x9b5c0053]
[    0.002320] ACPI: Reserving MSDM table memory at [mem 0x9b5bf000-0x9b5bf054]
[    0.002321] ACPI: Reserving DMAR table memory at [mem 0x9b5be000-0x9b5be0a7]
[    0.002322] ACPI: Reserving ASF! table memory at [mem 0x9b5bd000-0x9b5bd09f]
[    0.002323] ACPI: Reserving FPDT table memory at [mem 0x9b5bc000-0x9b5bc043]
[    0.002324] ACPI: Reserving UEFI table memory at [mem 0x9b53b000-0x9b53b13d]
[    0.002351] Zone ranges:
[    0.002352]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.002354]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.002356]   Normal   [mem 0x0000000100000000-0x000000045e7fffff]
[    0.002357] Movable zone start for each node
[    0.002358] Early memory node ranges
[    0.002358]   node   0: [mem 0x0000000000001000-0x000000000009cfff]
[    0.002360]   node   0: [mem 0x0000000000100000-0x000000003fffffff]
[    0.002361]   node   0: [mem 0x0000000040400000-0x000000008b79bfff]
[    0.002362]   node   0: [mem 0x0000000100000000-0x000000045e7fffff]
[    0.002363] Initmem setup node 0 [mem 0x0000000000001000-0x000000045e7fffff]
[    0.002368] On node 0, zone DMA: 1 pages in unavailable ranges
[    0.002405] On node 0, zone DMA: 99 pages in unavailable ranges
[    0.007574] On node 0, zone DMA32: 1024 pages in unavailable ranges
[    0.040119] On node 0, zone Normal: 18532 pages in unavailable ranges
[    0.040219] On node 0, zone Normal: 6144 pages in unavailable ranges
[    0.040235] Reserving Intel graphics memory at [mem 0x9d800000-0x9f7fffff]
[    0.040428] ACPI: PM-Timer IO Port: 0x1808
[    0.040433] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.040435] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.040436] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.040437] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.040438] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[    0.040438] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[    0.040439] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[    0.040440] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[    0.040474] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
[    0.040476] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.040478] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.040483] ACPI: Using ACPI (MADT) for SMP configuration information
[    0.040484] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.040487] TSC deadline timer available
[    0.040488] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[    0.040504] [mem 0x9f800000-0xefffffff] available for PCI devices
[    0.040507] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[    0.049020] setup_percpu: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
[    0.049147] percpu: Embedded 43 pages/cpu s138536 r8192 d29400 u524288
[    0.049154] pcpu-alloc: s138536 r8192 d29400 u524288 alloc=1*2097152
[    0.049156] pcpu-alloc: [0] 0 1 2 3 
[    0.049174] Built 1 zonelists, mobility grouping on.  Total pages: 4038701
[    0.049176] Kernel command line: auto BOOT_IMAGE=Linux ro root=10303 intel_idle.max_cstate=1
[    0.049205] Unknown kernel command line parameters "auto BOOT_IMAGE=Linux", will be passed to user space.
[    0.050068] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    0.050505] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    0.050547] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.050549] software IO TLB: area num 4.
[    0.100604] Memory: 16046964K/16411872K available (6144K kernel code, 1280K rwdata, 1324K rodata, 792K init, 692K bss, 364652K reserved, 0K cma-reserved)
[    0.100642] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.100895] Dynamic Preempt: none
[    0.100922] rcu: Preemptible hierarchical RCU implementation.
[    0.100923] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[    0.100947] NR_IRQS: 4352, nr_irqs: 1024, preallocated irqs: 16
[    0.101157] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.107390] Console: colour VGA+ 80x25
[    0.123413] printk: console [tty0] enabled
[    0.123511] ACPI: Core revision 20220331
[    0.123820] hpet: HPET dysfunctional in PC10. Force disabled.
[    0.123926] APIC: Switch to symmetric I/O mode setup
[    0.127852] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x26eae8729ef, max_idle_ns: 440795235156 ns
[    0.128000] Calibrating delay loop (skipped), value calculated using timer frequency.. 5399.81 BogoMIPS (lpj=2699909)
[    0.129000] pid_max: default: 32768 minimum: 301
[    0.129000] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.129000] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.129000] CPU0: Thermal monitoring enabled (TM1)
[    0.129000] process: using mwait in idle threads
[    0.129000] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[    0.129000] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[    0.129000] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.129000] Spectre V2 : Kernel not compiled with retpoline; no mitigation available!
[    0.129000] Spectre V2 : Vulnerable
[    0.129000] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.129000] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.129000] RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!
[    0.129000] RETBleed: Vulnerable
[    0.129000] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.129000] Spectre V2 : User space: Mitigation: STIBP via prctl
[    0.129000] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
[    0.129000] MDS: Mitigation: Clear CPU buffers
[    0.129000] TAA: Mitigation: TSX disabled
[    0.129000] MMIO Stale Data: Mitigation: Clear CPU buffers
[    0.129000] SRBDS: Mitigation: Microcode
[    0.129000] Freeing SMP alternatives memory: 12K
[    0.129000] smpboot: CPU0: Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz (family: 0x6, model: 0x8e, stepping: 0x9)
[    0.129000] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
[    0.129000] ... version:                4
[    0.129000] ... bit width:              48
[    0.129000] ... generic registers:      4
[    0.129000] ... value mask:             0000ffffffffffff
[    0.129000] ... max period:             00007fffffffffff
[    0.129000] ... fixed-purpose events:   3
[    0.129000] ... event mask:             000000070000000f
[    0.129081] Estimated ratio of average max frequency by base frequency (times 1024): 1327
[    0.129220] rcu: Hierarchical SRCU implementation.
[    0.129320] rcu:     Max phase no-delay instances is 400.
[    0.129527] smp: Bringing up secondary CPUs ...
[    0.129726] x86: Booting SMP configuration:
[    0.129825] .... node  #0, CPUs:      #1 #2
[    0.130609] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.131162] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
[    0.131479]  #3
[    0.131950] smp: Brought up 1 node, 4 CPUs
[    0.132097] smpboot: Max logical packages: 1
[    0.132190] smpboot: Total of 4 processors activated (21599.27 BogoMIPS)
[    0.133339] devtmpfs: initialized
[    0.133339] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    0.133339] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.134370] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.134577] thermal_sys: Registered thermal governor 'step_wise'
[    0.134578] thermal_sys: Registered thermal governor 'user_space'
[    0.134695] cpuidle: using governor ladder
[    0.134695] cpuidle: using governor menu
[    0.135030] Simple Boot Flag at 0x47 set to 0x1
[    0.135155] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.135509] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
[    0.135655] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
[    0.135772] PCI: Using configuration type 1 for base access
[    0.136003] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.136655] ACPI: Added _OSI(Module Device)
[    0.137002] ACPI: Added _OSI(Processor Device)
[    0.137099] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.137191] ACPI: Added _OSI(Processor Aggregator Device)
[    0.137286] ACPI: Added _OSI(Linux-Dell-Video)
[    0.137379] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.137473] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.171993] ACPI: 11 ACPI AML tables successfully acquired and loaded
[    0.172751] ACPI: EC: EC started
[    0.172846] ACPI: EC: interrupt blocked
[    0.173994] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.174001] ACPI: EC: Boot ECDT EC used to handle transactions
[    0.175150] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.183108] ACPI: Dynamic OEM Table Load:
[    0.183219] ACPI: SSDT 0xFFFF888100272000 0006B4 (v02 PmRef  Cpu0Ist  00003000 INTL 20160527)
[    0.184206] ACPI: \_PR_.PR00: _OSC native thermal LVT Acked
[    0.185139] ACPI: Dynamic OEM Table Load:
[    0.185244] ACPI: SSDT 0xFFFF8881000F8C00 0003FF (v02 PmRef  Cpu0Cst  00003001 INTL 20160527)
[    0.186199] ACPI: Dynamic OEM Table Load:
[    0.186303] ACPI: SSDT 0xFFFF88810091B3C0 0000BA (v02 PmRef  Cpu0Hwp  00003000 INTL 20160527)
[    0.187159] ACPI: Dynamic OEM Table Load:
[    0.187264] ACPI: SSDT 0xFFFF888100272800 000628 (v02 PmRef  HwpLvt   00003000 INTL 20160527)
[    0.188369] ACPI: Dynamic OEM Table Load:
[    0.188477] ACPI: SSDT 0xFFFF888100064000 000D14 (v02 PmRef  ApIst    00003000 INTL 20160527)
[    0.189891] ACPI: Dynamic OEM Table Load:
[    0.189995] ACPI: SSDT 0xFFFF8881000F9000 000317 (v02 PmRef  ApHwp    00003000 INTL 20160527)
[    0.190812] ACPI: Dynamic OEM Table Load:
[    0.190916] ACPI: SSDT 0xFFFF8881000F9400 00030A (v02 PmRef  ApCst    00003000 INTL 20160527)
[    0.192696] ACPI: Interpreter enabled
[    0.192801] ACPI: PM: (supports S0 S5)
[    0.192899] ACPI: Using IOAPIC for interrupt routing
[    0.193027] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.193170] PCI: Using E820 reservations for host bridge windows
[    0.193761] ACPI: Enabled 7 GPEs in block 00 to 7F
[    0.196761] ACPI: PM: Power Resource [PUBS]
[    0.213728] ACPI: PM: Power Resource [WRST]
[    0.214080] ACPI: PM: Power Resource [WRST]
[    0.224181] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[    0.224292] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[    0.224492] acpi PNP0A08:00: _OSC: platform does not support [PME AER PCIeCapability]
[    0.224654] acpi PNP0A08:00: _OSC: not requesting control; platform does not support [PCIeCapability]
[    0.224797] acpi PNP0A08:00: _OSC: OS requested [PME AER PCIeCapability LTR]
[    0.224900] acpi PNP0A08:00: _OSC: platform willing to grant [LTR]
[    0.225000] acpi PNP0A08:00: _OSC: platform retains control of PCIe features (AE_SUPPORT)
[    0.225665] PCI host bridge to bus 0000:00
[    0.225764] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.225866] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.225969] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.226001] pci_bus 0000:00: root bus resource [mem 0x9f800000-0xefffffff window]
[    0.226110] pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window]
[    0.226215] pci_bus 0000:00: root bus resource [bus 00-3e]
[    0.226338] pci 0000:00:00.0: [8086:5904] type 00 class 0x060000
[    0.226522] pci 0000:00:02.0: [8086:5916] type 00 class 0x030000
[    0.226637] pci 0000:00:02.0: reg 0x10: [mem 0xeb000000-0xebffffff 64bit]
[    0.226750] pci 0000:00:02.0: reg 0x18: [mem 0xa0000000-0xafffffff 64bit pref]
[    0.226862] pci 0000:00:02.0: reg 0x20: [io  0xe000-0xe03f]
[    0.226980] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.227206] pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330
[    0.227329] pci 0000:00:14.0: reg 0x10: [mem 0xec220000-0xec22ffff 64bit]
[    0.227504] pci 0000:00:14.0: PME# supported from D3hot D3cold
[    0.228067] pci 0000:00:14.2: [8086:9d31] type 00 class 0x118000
[    0.228190] pci 0000:00:14.2: reg 0x10: [mem 0xec248000-0xec248fff 64bit]
[    0.228439] pci 0000:00:16.0: [8086:9d3a] type 00 class 0x078000
[    0.228560] pci 0000:00:16.0: reg 0x10: [mem 0xec249000-0xec249fff 64bit]
[    0.228735] pci 0000:00:16.0: PME# supported from D3hot
[    0.229071] pci 0000:00:16.3: [8086:9d3d] type 00 class 0x070002
[    0.229185] pci 0000:00:16.3: reg 0x10: [io  0xe060-0xe067]
[    0.229290] pci 0000:00:16.3: reg 0x14: [mem 0xec24b000-0xec24bfff]
[    0.229544] pci 0000:00:1c.0: [8086:9d10] type 01 class 0x060400
[    0.229722] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    0.230166] pci 0000:00:1c.6: [8086:9d16] type 01 class 0x060400
[    0.230361] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
[    0.230783] pci 0000:00:1d.0: [8086:9d18] type 01 class 0x060400
[    0.230977] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[    0.231323] pci 0000:00:1d.2: [8086:9d1a] type 01 class 0x060400
[    0.231517] pci 0000:00:1d.2: PME# supported from D0 D3hot D3cold
[    0.231950] pci 0000:00:1f.0: [8086:9d4e] type 00 class 0x060100
[    0.232369] pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000
[    0.232484] pci 0000:00:1f.2: reg 0x10: [mem 0xec244000-0xec247fff]
[    0.232877] pci 0000:00:1f.3: [8086:9d71] type 00 class 0x040300
[    0.233000] pci 0000:00:1f.3: reg 0x10: [mem 0xec240000-0xec243fff 64bit]
[    0.233140] pci 0000:00:1f.3: reg 0x20: [mem 0xec230000-0xec23ffff 64bit]
[    0.233297] pci 0000:00:1f.3: PME# supported from D3hot D3cold
[    0.233688] pci 0000:00:1f.4: [8086:9d23] type 00 class 0x0c0500
[    0.233848] pci 0000:00:1f.4: reg 0x10: [mem 0xec24a000-0xec24a0ff 64bit]
[    0.234017] pci 0000:00:1f.4: reg 0x20: [io  0xefa0-0xefbf]
[    0.234432] pci 0000:00:1f.6: [8086:15d7] type 00 class 0x020000
[    0.234555] pci 0000:00:1f.6: reg 0x10: [mem 0xec200000-0xec21ffff]
[    0.234763] pci 0000:00:1f.6: PME# supported from D0 D3hot D3cold
[    0.235123] pci 0000:00:1c.0: PCI bridge to [bus 02]
[    0.235677] pci 0000:04:00.0: [8086:24fd] type 00 class 0x028000
[    0.236089] pci 0000:04:00.0: reg 0x10: [mem 0xec100000-0xec101fff 64bit]
[    0.236773] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
[    0.237777] pci 0000:00:1c.6: PCI bridge to [bus 04]
[    0.237877] pci 0000:00:1c.6:   bridge window [mem 0xec100000-0xec1fffff]
[    0.238021] pci 0000:00:1d.0: PCI bridge to [bus 05-3d]
[    0.238120] pci 0000:00:1d.0:   bridge window [mem 0xd4000000-0xea0fffff]
[    0.238225] pci 0000:00:1d.0:   bridge window [mem 0xb0000000-0xd1ffffff 64bit pref]
[    0.238563] pci 0000:3e:00.0: [17aa:0003] type 00 class 0x010802
[    0.238793] pci 0000:3e:00.0: reg 0x10: [mem 0xec000000-0xec003fff 64bit]
[    0.239147] pci 0000:3e:00.0: 15.752 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x2 link at 0000:00:1d.2 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[    0.239593] pci 0000:00:1d.2: PCI bridge to [bus 3e]
[    0.240005] pci 0000:00:1d.2:   bridge window [mem 0xec000000-0xec0fffff]
[    0.240137] pci_bus 0000:00: on NUMA node 0
[    0.241883] ACPI: PCI: Interrupt link LNKA configured for IRQ 11
[    0.242044] ACPI: PCI: Interrupt link LNKB configured for IRQ 10
[    0.242202] ACPI: PCI: Interrupt link LNKC configured for IRQ 11
[    0.242360] ACPI: PCI: Interrupt link LNKD configured for IRQ 11
[    0.242516] ACPI: PCI: Interrupt link LNKE configured for IRQ 11
[    0.242671] ACPI: PCI: Interrupt link LNKF configured for IRQ 11
[    0.242826] ACPI: PCI: Interrupt link LNKG configured for IRQ 11
[    0.242980] ACPI: PCI: Interrupt link LNKH configured for IRQ 11
[    0.243386] ACPI: EC: interrupt unblocked
[    0.243477] ACPI: EC: event unblocked
[    0.243576] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.243672] ACPI: EC: GPE=0x16
[    0.243758] ACPI: \_SB_.PCI0.LPCB.EC__: Boot ECDT EC initialization complete
[    0.243861] ACPI: \_SB_.PCI0.LPCB.EC__: EC: Used to handle transactions and events
[    0.244120] PCI: Using ACPI for IRQ routing
[    0.246478] PCI: pci_cache_line_size set to 64 bytes
[    0.247501] e820: reserve RAM buffer [mem 0x0009d000-0x0009ffff]
[    0.247503] e820: reserve RAM buffer [mem 0x8b79c000-0x8bffffff]
[    0.247504] e820: reserve RAM buffer [mem 0x45e800000-0x45fffffff]
[    0.247524] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[    0.247524] pci 0000:00:02.0: vgaarb: bridge control possible
[    0.247524] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    0.247524] vgaarb: loaded
[    0.248008] clocksource: Switched to clocksource tsc-early
[    0.248161] pnp: PnP ACPI init
[    0.248307] system 00:00: [mem 0x40000000-0x403fffff] has been reserved
[    0.248514] system 00:01: [mem 0xfd000000-0xfdabffff] has been reserved
[    0.248623] system 00:01: [mem 0xfdad0000-0xfdadffff] has been reserved
[    0.248724] system 00:01: [mem 0xfdb00000-0xfdffffff] has been reserved
[    0.248826] system 00:01: [mem 0xfe000000-0xfe01ffff] has been reserved
[    0.248927] system 00:01: [mem 0xfe036000-0xfe03bfff] has been reserved
[    0.249028] system 00:01: [mem 0xfe03d000-0xfe3fffff] has been reserved
[    0.249134] system 00:01: [mem 0xfe410000-0xfe7fffff] has been reserved
[    0.249461] system 00:02: [io  0xff00-0xfffe] has been reserved
[    0.250401] system 00:03: [io  0x0680-0x069f] has been reserved
[    0.250510] system 00:03: [io  0xffff] has been reserved
[    0.250606] system 00:03: [io  0xffff] has been reserved
[    0.250703] system 00:03: [io  0xffff] has been reserved
[    0.250799] system 00:03: [io  0x1800-0x18fe] has been reserved
[    0.250898] system 00:03: [io  0x164e-0x164f] has been reserved
[    0.251112] system 00:05: [io  0x1854-0x1857] has been reserved
[    0.251327] system 00:08: [io  0x1800-0x189f] could not be reserved
[    0.251434] system 00:08: [io  0x0800-0x087f] has been reserved
[    0.251532] system 00:08: [io  0x0880-0x08ff] has been reserved
[    0.251631] system 00:08: [io  0x0900-0x097f] has been reserved
[    0.251730] system 00:08: [io  0x0980-0x09ff] has been reserved
[    0.251829] system 00:08: [io  0x0a00-0x0a7f] has been reserved
[    0.251927] system 00:08: [io  0x0a80-0x0aff] has been reserved
[    0.252031] system 00:08: [io  0x0b00-0x0b7f] has been reserved
[    0.252135] system 00:08: [io  0x0b80-0x0bff] has been reserved
[    0.252234] system 00:08: [io  0x15e0-0x15ef] has been reserved
[    0.252333] system 00:08: [io  0x1600-0x167f] could not be reserved
[    0.252432] system 00:08: [io  0x1640-0x165f] could not be reserved
[    0.252533] system 00:08: [mem 0xf0000000-0xf3ffffff] has been reserved
[    0.252634] system 00:08: [mem 0xfed10000-0xfed13fff] has been reserved
[    0.252735] system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved
[    0.252836] system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved
[    0.252938] system 00:08: [mem 0xfeb00000-0xfebfffff] has been reserved
[    0.253042] system 00:08: [mem 0xfed20000-0xfed3ffff] has been reserved
[    0.253148] system 00:08: [mem 0xfed90000-0xfed93fff] has been reserved
[    0.253249] system 00:08: [mem 0xeffe0000-0xefffffff] has been reserved
[    0.254282] system 00:09: [mem 0xfdaf0000-0xfdafffff] has been reserved
[    0.254391] system 00:09: [mem 0xfdae0000-0xfdaeffff] has been reserved
[    0.254492] system 00:09: [mem 0xfdac0000-0xfdacffff] has been reserved
[    0.254999] system 00:0a: [mem 0xfed10000-0xfed17fff] could not be reserved
[    0.255113] system 00:0a: [mem 0xfed18000-0xfed18fff] has been reserved
[    0.255214] system 00:0a: [mem 0xfed19000-0xfed19fff] has been reserved
[    0.255315] system 00:0a: [mem 0xf0000000-0xf3ffffff] has been reserved
[    0.255417] system 00:0a: [mem 0xfed20000-0xfed3ffff] has been reserved
[    0.255519] system 00:0a: [mem 0xfed90000-0xfed93fff] has been reserved
[    0.255620] system 00:0a: [mem 0xfed45000-0xfed8ffff] could not be reserved
[    0.255723] system 00:0a: [mem 0xff000000-0xffffffff] could not be reserved
[    0.255825] system 00:0a: [mem 0xfee00000-0xfeefffff] could not be reserved
[    0.255928] system 00:0a: [mem 0xeffe0000-0xefffffff] has been reserved
[    0.256288] pnp 00:0b: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.256441] pnp 00:0b: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.256586] pnp 00:0b: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.256731] pnp 00:0b: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.256895] system 00:0b: [mem 0x00000000-0x0009ffff] could not be reserved
[    0.257008] system 00:0b: [mem 0x000e0000-0x000e3fff] could not be reserved
[    0.257115] system 00:0b: [mem 0x000e8000-0x000ebfff] could not be reserved
[    0.257218] system 00:0b: [mem 0x000f0000-0x000fffff] could not be reserved
[    0.257320] system 00:0b: [mem 0x00100000-0x9f7fffff] could not be reserved
[    0.257423] system 00:0b: [mem 0xfec00000-0xfed3ffff] could not be reserved
[    0.257526] system 00:0b: [mem 0xfed4c000-0xffffffff] could not be reserved
[    0.257729] pnp: PnP ACPI: found 12 devices
[    0.264215] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.264383] NET: Registered PF_INET protocol family
[    0.264686] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.268414] tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear)
[    0.268569] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.268683] TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.268910] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[    0.269140] TCP: Hash tables configured (established 131072 bind 65536)
[    0.269269] UDP hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    0.269407] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    0.269578] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.269696] pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 02] add_size 1000
[    0.269812] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000 add_align 100000
[    0.269963] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 02] add_size 200000 add_align 100000
[    0.270108] pci 0000:00:1d.0: bridge window [io  0x1000-0x0fff] to [bus 05-3d] add_size 1000
[    0.270227] pci 0000:00:1c.0: BAR 8: assigned [mem 0x9f800000-0x9f9fffff]
[    0.270339] pci 0000:00:1c.0: BAR 9: assigned [mem 0x9fa00000-0x9fbfffff 64bit pref]
[    0.270451] pci 0000:00:1c.0: BAR 7: assigned [io  0x2000-0x2fff]
[    0.270556] pci 0000:00:1d.0: BAR 7: assigned [io  0x3000-0x3fff]
[    0.270656] pci 0000:00:1c.0: PCI bridge to [bus 02]
[    0.270759] pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
[    0.270862] pci 0000:00:1c.0:   bridge window [mem 0x9f800000-0x9f9fffff]
[    0.270967] pci 0000:00:1c.0:   bridge window [mem 0x9fa00000-0x9fbfffff 64bit pref]
[    0.271079] pci 0000:00:1c.6: PCI bridge to [bus 04]
[    0.271177] pci 0000:00:1c.6:   bridge window [mem 0xec100000-0xec1fffff]
[    0.271285] pci 0000:00:1d.0: PCI bridge to [bus 05-3d]
[    0.271382] pci 0000:00:1d.0:   bridge window [io  0x3000-0x3fff]
[    0.271483] pci 0000:00:1d.0:   bridge window [mem 0xd4000000-0xea0fffff]
[    0.271586] pci 0000:00:1d.0:   bridge window [mem 0xb0000000-0xd1ffffff 64bit pref]
[    0.271694] pci 0000:00:1d.2: PCI bridge to [bus 3e]
[    0.271790] pci 0000:00:1d.2:   bridge window [mem 0xec000000-0xec0fffff]
[    0.271897] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    0.271997] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    0.272099] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    0.272205] pci_bus 0000:00: resource 7 [mem 0x9f800000-0xefffffff window]
[    0.272308] pci_bus 0000:00: resource 8 [mem 0xfd000000-0xfe7fffff window]
[    0.272410] pci_bus 0000:02: resource 0 [io  0x2000-0x2fff]
[    0.272508] pci_bus 0000:02: resource 1 [mem 0x9f800000-0x9f9fffff]
[    0.272608] pci_bus 0000:02: resource 2 [mem 0x9fa00000-0x9fbfffff 64bit pref]
[    0.272712] pci_bus 0000:04: resource 1 [mem 0xec100000-0xec1fffff]
[    0.272824] pci_bus 0000:05: resource 0 [io  0x3000-0x3fff]
[    0.272922] pci_bus 0000:05: resource 1 [mem 0xd4000000-0xea0fffff]
[    0.273023] pci_bus 0000:05: resource 2 [mem 0xb0000000-0xd1ffffff 64bit pref]
[    0.273132] pci_bus 0000:3e: resource 1 [mem 0xec000000-0xec0fffff]
[    0.274113] PCI: CLS 0 bytes, default 64
[    0.274220] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.274327] software IO TLB: mapped [mem 0x000000008779c000-0x000000008b79c000] (64MB)
[    0.274475] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
[    0.274590] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[    0.274688] RAPL PMU: hw unit of domain package 2^-14 Joules
[    0.274783] RAPL PMU: hw unit of domain dram 2^-14 Joules
[    0.274877] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[    0.274973] RAPL PMU: hw unit of domain psys 2^-14 Joules
[    0.275110] resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more than pnp 00:08 [mem 0xfed10000-0xfed13fff]
[    0.275266] caller snb_uncore_imc_init_box+0x73/0xbf mapping multiple BARs
[    0.276075] workingset: timestamp_bits=62 max_order=22 bucket_order=0
[    0.277117] SGI XFS with security attributes, no debug enabled
[    0.277485] io scheduler mq-deadline registered
[    0.277585] io scheduler kyber registered
[    0.278564] intel_idle: max_cstate 1 reached
[    0.279820] nvme nvme0: pci function 0000:3e:00.0
[    0.280170] rtc_cmos 00:04: RTC can wake from S4
[    0.281833] rtc_cmos 00:04: registered as rtc0
[    0.282073] rtc_cmos 00:04: setting system clock to 2022-08-30T15:06:59 UTC (1661872019)
[    0.282201] rtc_cmos 00:04: alarms up to one month, y3k, 242 bytes nvram
[    0.282383] intel_pstate: Intel P-state driver initializing
[    0.282659] intel_pstate: HWP enabled
[    0.282804] NET: Registered PF_PACKET protocol family
[    0.282919] IPI shorthand broadcast: enabled
[    0.283221] sched_clock: Marking stable (256459078, 26740767)->(299733087, -16533242)
[    0.283377] registered taskstats version 1
[    0.294710] nvme nvme0: 4/0/0 default/read/poll queues
[    0.296155]  nvme0n1: p1 p2 < p5 p6 p7 p8 p9 p10 p11 >
[    0.297108] XFS (nvme0n1p5): Mounting V5 Filesystem
[    0.305420] XFS (nvme0n1p5): Ending clean mount
[    0.309277] VFS: Mounted root (xfs filesystem) readonly on device 259:3.
[    0.309544] devtmpfs: mounted
[    0.309736] Freeing unused kernel image (initmem) memory: 792K
[    0.315005] Write protecting the kernel read-only data: 10240k
[    0.315448] Freeing unused kernel image (text/rodata gap) memory: 2044K
[    0.315646] Freeing unused kernel image (rodata/data gap) memory: 724K
[    0.315741] Run /sbin/init as init process
[    0.315823]   with arguments:
[    0.315823]     /sbin/init
[    0.315824]     auto
[    0.315824]   with environment:
[    0.315825]     HOME=/
[    0.315826]     TERM=linux
[    0.315826]     BOOT_IMAGE=Linux
[    0.369259] loop: module loaded
[    0.955010] random: crng init done
[    0.961765] udevd[281]: starting eudev-3.2.11
[    1.012260] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
[    1.012362] ACPI: button: Sleep Button [SLPB]
[    1.012485] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
[    1.012582] ACPI: button: Lid Switch [LID]
[    1.012702] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[    1.012796] ACPI: button: Power Button [PWRF]
[    1.051503] ACPI: AC: AC Adapter [AC] (on-line)
[    1.051825] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[    1.053852] serio: i8042 KBD port at 0x60,0x64 irq 1
[    1.053943] serio: i8042 AUX port at 0x60,0x64 irq 12
[    1.071720] ACPI: battery: Slot [BAT0] (battery present)
[    1.088539] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.088583] thermal LNXTHERM:00: registered as thermal_zone0
[    1.088729] ACPI: thermal: Thermal Zone [THM0] (48 C)
[    1.088783] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    1.089957] ACPI: bus type USB registered
[    1.090067] usbcore: registered new interface driver usbfs
[    1.090173] usbcore: registered new interface driver hub
[    1.090273] usbcore: registered new device driver usb
[    1.091221] ACPI: bus type drm_connector registered
[    1.091429] 0000:00:16.3: ttyS1 at I/O 0xe060 (irq = 19, base_baud = 115200) is a 16550A
[    1.092049] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.092147] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[    1.093319] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000081109810
[    1.093719] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.093809] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[    1.093905] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[    1.094147] hub 1-0:1.0: USB hub found
[    1.094245] hub 1-0:1.0: 12 ports detected
[    1.095875] hub 2-0:1.0: USB hub found
[    1.095968] hub 2-0:1.0: 6 ports detected
[    1.097087] usb: port power management may be unreliable
[    1.107360] pps_core: LinuxPPS API ver. 1 registered
[    1.107451] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.107925] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[    1.108066] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[    1.108185] PTP clock support registered
[    1.108201] pci 0000:00:1f.1: [8086:9d20] type 00 class 0x058000
[    1.108421] pci 0000:00:1f.1: reg 0x10: [mem 0xfd000000-0xfdffffff 64bit]
[    1.110176] e1000e: Intel(R) PRO/1000 Network Driver
[    1.110266] i2c i2c-0: 2/2 memory slots populated (from DMI)
[    1.110276] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.110649] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    1.110740] i2c i2c-0: Successfully instantiated SPD at 0x50
[    1.111254] i2c i2c-0: Successfully instantiated SPD at 0x51
[    1.134257] cryptd: max_cpu_qlen set to 1000
[    1.136637] AVX2 version of gcm_enc/dec engaged.
[    1.136736] AES CTR mode by8 optimization enabled
[    1.182882] i915 0000:00:02.0: vgaarb: deactivate vga console
[    1.184330] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
[    1.184933] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[    1.186926] Console: switching to colour dummy device 80x25
[    1.187505] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    1.188752] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[    1.245901] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 8c:16:45:b8:37:51
[    1.245907] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[    1.245985] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: 1000FF-0FF
[    1.246369] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[    1.248027] ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    1.248224] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
[    1.311027] tsc: Refined TSC clocksource calibration: 2712.009 MHz
[    1.311048] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x27178ec3e42, max_idle_ns: 440795287235 ns
[    1.311296] clocksource: Switched to clocksource tsc
[    1.342015] usb 1-4: new full-speed USB device number 2 using xhci_hcd
[    1.368949] fbcon: i915drmfb (fb0) is primary device
[    1.372185] Console: switching to colour frame buffer device 240x67
[    1.393806] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[    1.434467] Adding 6519124k swap on /dev/nvme0n1p11.  Priority:-2 extents:1 across:6519124k SS
[    1.473400] usbcore: registered new interface driver usbserial_generic
[    1.473464] usbserial: USB Serial support registered for generic
[    1.474497] usbcore: registered new interface driver pl2303
[    1.474626] usbserial: USB Serial support registered for pl2303
[    1.474701] pl2303 1-4:1.0: pl2303 converter detected
[    1.475356] usb 1-4: pl2303 converter now attached to ttyUSB0
[    1.582351] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[    1.632090] xfs filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)
[    1.675505] XFS (nvme0n1p1): Mounting V5 Filesystem
[    1.690308] XFS (nvme0n1p1): Ending clean mount
[    1.691584] xfs filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
[    1.692139] XFS (nvme0n1p6): Mounting V5 Filesystem
[    1.707886] XFS (nvme0n1p6): Ending clean mount
[    1.709007] xfs filesystem being mounted at /tmp supports timestamps until 2038 (0x7fffffff)
[    1.709663] XFS (nvme0n1p7): Mounting V5 Filesystem
[    1.710037] usb 1-7: new full-speed USB device number 3 using xhci_hcd
[    1.825119] XFS (nvme0n1p7): Ending clean mount
[    1.826263] xfs filesystem being mounted at /var supports timestamps until 2038 (0x7fffffff)
[    1.826976] XFS (nvme0n1p8): Mounting V5 Filesystem
[    1.840314] XFS (nvme0n1p8): Ending clean mount
[    1.843365] xfs filesystem being mounted at /root supports timestamps until 2038 (0x7fffffff)
[    1.845912] XFS (nvme0n1p9): Mounting V5 Filesystem
[    1.859042] XFS (nvme0n1p9): Ending clean mount
[    1.861951] xfs filesystem being mounted at /usr/src supports timestamps until 2038 (0x7fffffff)
[    1.864541] XFS (nvme0n1p10): Mounting V5 Filesystem
[    1.876070] XFS (nvme0n1p10): Ending clean mount
[    1.879264] xfs filesystem being mounted at /home supports timestamps until 2038 (0x7fffffff)
[    1.927793] ax88179_178a 2-1:1.0 eth1: register 'ax88179_178a' at usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c6:81:79:01
[    1.929052] usbcore: registered new interface driver ax88179_178a
[    1.950140] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd
[    1.981133] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.982922] SCSI subsystem initialized
[    1.984333] usb-storage 2-3:1.0: USB Mass Storage device detected
[    1.984439] scsi host0: usb-storage 2-3:1.0
[    1.984596] usbcore: registered new interface driver usb-storage
[    2.081009] usb 1-8: new high-speed USB device number 4 using xhci_hcd
[    3.043664] scsi 0:0:0:0: Direct-Access     Generic- SD/MMC           1.00 PQ: 0 ANSI: 6
[    3.052917] sd 0:0:0:0: [sda] Media removed, stopped polling
[    3.052998] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    5.776275] gre: GRE over IPv4 demultiplexor driver
[    5.776674] ip_gre: GRE over IPv4 tunneling driver
[    6.109040] br0: port 1(xs4mobile) entered blocking state
[    6.109052] br0: port 1(xs4mobile) entered disabled state
[    6.109165] device xs4mobile entered promiscuous mode
[    6.109275] br0: port 1(xs4mobile) entered blocking state
[    6.109281] br0: port 1(xs4mobile) entered forwarding state
[    6.114550] br0: port 2(eth1) entered blocking state
[    6.114560] br0: port 2(eth1) entered disabled state
[    6.114685] device eth1 entered promiscuous mode
[    7.405812] e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[    9.767378] ax88179_178a 2-1:1.0 eth1: ax88179 - Link status is: 1
[    9.773432] br0: port 2(eth1) entered blocking state
[    9.773442] br0: port 2(eth1) entered forwarding state
[154958.141754] usb 2-1: USB disconnect, device number 2
[154958.141939] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[154958.142062] ax88179_178a 2-1:1.0 eth1: unregister 'ax88179_178a' usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet
[154958.142101] ax88179_178a 2-1:1.0 eth1: Failed to read reg index 0x0002: -19
[154958.142111] ax88179_178a 2-1:1.0 eth1: Failed to write reg index 0x0002: -19
[154958.142163] br0: port 2(eth1) entered disabled state
[154958.142337] device eth1 left promiscuous mode
[154958.142343] br0: port 2(eth1) entered disabled state
[154958.159771] ax88179_178a 2-1:1.0 eth1 (unregistered): Failed to write reg index 0x0002: -19
[154958.159786] ax88179_178a 2-1:1.0 eth1 (unregistered): Failed to write reg index 0x0001: -19
[154958.159794] ax88179_178a 2-1:1.0 eth1 (unregistered): Failed to write reg index 0x0002: -19
[154958.381910] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
[154958.724429] ax88179_178a 2-1:1.0 eth1: register 'ax88179_178a' at usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c6:81:79:01

Revision history for this message

In Linux Kernel Bug Tracker #202541, pupilla (pupilla-linux-kernel-bugs) wrote on 2022-09-02:

#271

Hello everyone,

unfortunately it happened again (system started without parameters):

[ 9.561808] br0: port 2(eth1) entered forwarding state
[95735.974041] usb 2-1: USB disconnect, device number 2
[95735.974215] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[95735.974439] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[95735.974471] ax88179_178a 2-1:1.0 eth1: unregister 'ax88179_178a' usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet
[95735.974523] ax88179_178a 2-1:1.0 eth1: Failed to read reg index 0x0002: -19
[95735.974532] ax88179_178a 2-1:1.0 eth1: Failed to write reg index 0x0002: -19
[95735.974595] br0: port 2(eth1) entered disabled state
[95735.974783] device eth1 left promiscuous mode
[95735.974790] br0: port 2(eth1) entered disabled state
[95735.992489] ax88179_178a 2-1:1.0 eth1 (unregistered): Failed to write reg index 0x0002: -19
[95735.992503] ax88179_178a 2-1:1.0 eth1 (unregistered): Failed to write reg index 0x0001: -19
[95735.992510] ax88179_178a 2-1:1.0 eth1 (unregistered): Failed to write reg index 0x0002: -19
[95736.215301] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
[95736.566562] ax88179_178a 2-1:1.0 eth1: register 'ax88179_178a' at usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c6:81:79:01

Marco

Revision history for this message

In Linux Kernel Bug Tracker #202541, ske5074 (ske5074-linux-kernel-bugs) wrote on 2022-09-03:

#272

Download full text (9.6 KiB)

I also have the issue. Using Proxmox 7.2 (Debian Bullseye) with a Lenovo M910q core-i7-7700T, using two TPLink UE300 (RTL8153) USB to 1Gbe Ethernet adapters. Each one is stable in a lower USB slot. Swapping the adapters does not change the behavior and only impacts the USB device in the higher slot. Changes to different ports without change.

Easily reproducible with the following commands. Basically I'm trying to plumb bond0 again, which works initially, I get the xhci_hcd warning, and the link is down again. System details are also below.

root@higgins:~# dmesg -C ; ifup -a ; ip link | grep enx ; \
> dmesg -H ; dmesg -C ; sleep 70 ; \
> ip link | grep enx ; dmesg -H
3: enxd03745be5afc: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000
16: enx54af9786ab11: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000

[Sep 3 11:05] device enx54af9786ab11 entered promiscuous mode
[ +0.001236] bond0: (slave enx54af9786ab11): Enslaving as a backup interface with a down link
[ +0.006363] vmbr0: the hash_elasticity option has been deprecated and is always 16
[ +0.013972] r8152 2-4:1.0 enx54af9786ab11: Promiscuous mode enabled
[ +0.001344] r8152 2-4:1.0 enx54af9786ab11: carrier on

3: enxd03745be5afc: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000
17: enx54af9786ab11: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000

[Sep 3 11:05] bond0: (slave enx54af9786ab11): link status definitely up, 1000 Mbps full duplex
[Sep 3 11:06] usb 2-4: USB disconnect, device number 12
[ +0.001544] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ +0.001435] bond0: (slave enx54af9786ab11): Releasing backup interface
[ +0.029081] device enx54af9786ab11 left promiscuous mode
[ +0.316190] usb 2-4: new SuperSpeed USB device number 13 using xhci_hcd
[ +0.022053] usb 2-4: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00
[ +0.001297] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ +0.001337] usb 2-4: Product: USB 10/100/1000 LAN
[ +0.001261] usb 2-4: Manufacturer: TP-Link
[ +0.001208] usb 2-4: SerialNumber: 000001
[ +0.137200] usb 2-4: reset SuperSpeed USB device number 13 using xhci_hcd
[ +0.049197] r8152 2-4:1.0: load rtl8153a-4 v2 02/07/20 successfully
[ +0.030905] r8152 2-4:1.0 eth0: v1.12.12
[ +0.007834] r8152 2-4:1.0 enx54af9786ab11: renamed from eth0
root@higgins:~#

-------
System Details
-------

root@higgins:~# uname -a
Linux higgins 5.15.39-4-pve #1 SMP PVE 5.15.39-4 (Mon, 08 Aug 2022 15:11:15 +0200) x86_64 GNU/Linux

root@higgins:~# lspci -k -nn | grep -B2 xhci
00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af]
        Subsystem: Lenovo 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [17aa:310b]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci

root@higgins:~# lsusb -tv
/: Bus 02.Port 1: D...

I also have the issue.  Using Proxmox 7.2 (Debian Bullseye) with a Lenovo M910q core-i7-7700T,  using two TPLink UE300 (RTL8153) USB to 1Gbe Ethernet adapters. Each one is stable in a lower USB slot. Swapping the adapters does not change the behavior and only impacts the USB device in the higher slot.  Changes to different ports without change.

Easily reproducible with the following commands.  Basically I'm trying to plumb bond0 again,  which works initially, I get the xhci_hcd warning, and the link is down again.  System details are also below.

root@higgins:~# dmesg -C ; ifup -a ; ip link | grep enx ; \
> dmesg -H ; dmesg -C ; sleep 70 ;                       \ 
> ip link | grep enx ; dmesg -H
3: enxd03745be5afc: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000
16: enx54af9786ab11: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000

[Sep 3 11:05] device enx54af9786ab11 entered promiscuous mode
[  +0.001236] bond0: (slave enx54af9786ab11): Enslaving as a backup interface with a down link
[  +0.006363] vmbr0: the hash_elasticity option has been deprecated and is always 16
[  +0.013972] r8152 2-4:1.0 enx54af9786ab11: Promiscuous mode enabled
[  +0.001344] r8152 2-4:1.0 enx54af9786ab11: carrier on

3: enxd03745be5afc: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000
17: enx54af9786ab11: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000

[Sep 3 11:05] bond0: (slave enx54af9786ab11): link status definitely up, 1000 Mbps full duplex
[Sep 3 11:06] usb 2-4: USB disconnect, device number 12
[  +0.001544] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  +0.001435] bond0: (slave enx54af9786ab11): Releasing backup interface
[  +0.029081] device enx54af9786ab11 left promiscuous mode
[  +0.316190] usb 2-4: new SuperSpeed USB device number 13 using xhci_hcd
[  +0.022053] usb 2-4: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00
[  +0.001297] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[  +0.001337] usb 2-4: Product: USB 10/100/1000 LAN
[  +0.001261] usb 2-4: Manufacturer: TP-Link
[  +0.001208] usb 2-4: SerialNumber: 000001
[  +0.137200] usb 2-4: reset SuperSpeed USB device number 13 using xhci_hcd
[  +0.049197] r8152 2-4:1.0: load rtl8153a-4 v2 02/07/20 successfully
[  +0.030905] r8152 2-4:1.0 eth0: v1.12.12
[  +0.007834] r8152 2-4:1.0 enx54af9786ab11: renamed from eth0
root@higgins:~#

-------
System Details
-------

root@higgins:~# uname -a
Linux higgins 5.15.39-4-pve #1 SMP PVE 5.15.39-4 (Mon, 08 Aug 2022 15:11:15 +0200) x86_64 GNU/Linux

root@higgins:~# lspci -k -nn | grep -B2 xhci
00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af]
        Subsystem: Lenovo 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [17aa:310b]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci

root@higgins:~# lsusb -tv
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
        ID 2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153]
    |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
        ID 2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153]
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub

root@higgins:~# modinfo r8152
filename:       /lib/modules/5.15.39-4-pve/kernel/drivers/net/usb/r8152.ko
version:        v1.12.12
license:        GPL
description:    Realtek RTL8152/RTL8153 Based USB Ethernet Adapters
author:         Realtek linux nic maintainers <nic_swsd@realtek.com>
firmware:       rtl_nic/rtl8156b-2.fw
firmware:       rtl_nic/rtl8156a-2.fw
firmware:       rtl_nic/rtl8153c-1.fw
firmware:       rtl_nic/rtl8153b-2.fw
firmware:       rtl_nic/rtl8153a-4.fw
firmware:       rtl_nic/rtl8153a-3.fw
firmware:       rtl_nic/rtl8153a-2.fw
srcversion:     9144C27A9617457A5BEE55E
alias:          usb:v2357p0601d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v2357p0601d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0955p09FFd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0955p09FFd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v13B1p0041d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v13B1p0041d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFpA387d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFpA387d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp721Ed*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp721Ed*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp7214d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp7214d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp720Cd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp720Cd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp7205d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp7205d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp3082d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp3082d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp3069d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp3069d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp3062d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp3062d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v04E8pA101d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v04E8pA101d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v045Ep0927d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v045Ep0927d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v045Ep07C6d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v045Ep07C6d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v045Ep07ABd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v045Ep07ABd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8156d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8156d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8155d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8155d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8053d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8053d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8050d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8050d*dc*dsc*dp*icFFisc*ip*in*
depends:        mii
retpoline:      Y
intree:         Y
name:           r8152
vermagic:       5.15.39-4-pve SMP mod_unload modversions

root@higgins:~# tail -1000 /var/log/messages | grep usb | grep 09:39
Sep  3 09:39:26 higgins kernel: [    1.547421] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
Sep  3 09:39:26 higgins kernel: [    1.547426] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  3 09:39:26 higgins kernel: [    1.547429] usb usb1: Product: xHCI Host Controller
Sep  3 09:39:26 higgins kernel: [    1.547431] usb usb1: Manufacturer: Linux 5.15.39-4-pve xhci-hcd
Sep  3 09:39:26 higgins kernel: [    1.547434] usb usb1: SerialNumber: 0000:00:14.0
Sep  3 09:39:26 higgins kernel: [    1.549759] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
Sep  3 09:39:26 higgins kernel: [    1.549763] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  3 09:39:26 higgins kernel: [    1.549766] usb usb2: Product: xHCI Host Controller
Sep  3 09:39:26 higgins kernel: [    1.549769] usb usb2: Manufacturer: Linux 5.15.39-4-pve xhci-hcd
Sep  3 09:39:26 higgins kernel: [    1.549771] usb usb2: SerialNumber: 0000:00:14.0
Sep  3 09:39:26 higgins kernel: [    1.551090] usb: port power management may be unreliable
Sep  3 09:39:26 higgins kernel: [    1.889622] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
Sep  3 09:39:26 higgins kernel: [    1.912268] usb 2-1: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00
Sep  3 09:39:26 higgins kernel: [    1.912273] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Sep  3 09:39:26 higgins kernel: [    1.912276] usb 2-1: Product: USB 10/100/1000 LAN
Sep  3 09:39:26 higgins kernel: [    1.912278] usb 2-1: Manufacturer: TP-LINK
Sep  3 09:39:26 higgins kernel: [    1.912280] usb 2-1: SerialNumber: 000001000000
Sep  3 09:39:26 higgins kernel: [    2.045666] usb 2-4: new SuperSpeed USB device number 3 using xhci_hcd
Sep  3 09:39:26 higgins kernel: [    2.068477] usb 2-4: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00
Sep  3 09:39:26 higgins kernel: [    2.068498] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Sep  3 09:39:26 higgins kernel: [    2.068514] usb 2-4: Product: USB 10/100/1000 LAN
Sep  3 09:39:26 higgins kernel: [    2.068525] usb 2-4: Manufacturer: TP-Link
Sep  3 09:39:26 higgins kernel: [    2.068535] usb 2-4: SerialNumber: 000001
Sep  3 09:39:26 higgins kernel: [    4.110138] usbcore: registered new interface driver r8152
Sep  3 09:39:26 higgins kernel: [    4.198806] usbcore: registered new interface driver cdc_ether
Sep  3 09:39:26 higgins kernel: [    4.282161] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
Sep  3 09:39:26 higgins kernel: [    4.429911] usb 2-4: reset SuperSpeed USB device number 3 using xhci_hcd

Revision history for this message

In Linux Kernel Bug Tracker #202541, ske5074 (ske5074-linux-kernel-bugs) wrote on 2022-09-07:

#273

(In reply to Sean Kennedy from comment #205)
> I also have the issue. Using Proxmox 7.2 (Debian Bullseye) with a Lenovo
> M910q core-i7-7700T, using two TPLink UE300 (RTL8153) USB to 1Gbe Ethernet
> adapters. Each one is stable in a lower USB slot. Swapping the adapters does
> not change the behavior and only impacts the USB device in the higher slot.
> Changes to different ports without change.

Update - Tried a different dongle - a 2.5Gbe and have two hard drives attached to the system. Doesn't matter where the 2.5Gbe dongle is attached, it eventually errors with "WARN Set TR Deq Ptr cmd failed" And the error rate is only around six times a day right now:

8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN

# dmesg -T | grep xhci
[Tue Sep 6 13:37:13 2022] xhci_hcd 0000:00:14.0: xHCI Host Controller
[Tue Sep 6 13:37:13 2022] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[Tue Sep 6 13:37:13 2022] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000000009810
[Tue Sep 6 13:37:13 2022] usb usb1: Manufacturer: Linux 5.15.39-4-pve xhci-hcd
[Tue Sep 6 13:37:13 2022] xhci_hcd 0000:00:14.0: xHCI Host Controller
[Tue Sep 6 13:37:13 2022] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[Tue Sep 6 13:37:13 2022] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[Tue Sep 6 13:37:13 2022] usb usb2: Manufacturer: Linux 5.15.39-4-pve xhci-hcd
[Tue Sep 6 13:37:13 2022] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[Tue Sep 6 13:37:14 2022] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd
[Tue Sep 6 13:37:14 2022] usb 2-4: new SuperSpeed USB device number 4 using xhci_hcd
[Tue Sep 6 14:39:22 2022] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Tue Sep 6 14:39:22 2022] usb 2-4: new SuperSpeed USB device number 5 using xhci_hcd
[Tue Sep 6 18:44:01 2022] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Tue Sep 6 18:44:01 2022] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Tue Sep 6 18:44:02 2022] usb 2-4: new SuperSpeed USB device number 6 using xhci_hcd
[Tue Sep 6 22:19:06 2022] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Tue Sep 6 22:19:07 2022] usb 2-4: new SuperSpeed USB device number 7 using xhci_hcd

Since this drops the device from the system and offlines the link, I created a simple script to detect zero UP ethernet devices via cron once a minute and runs a ifnet -a. It's clunky but works.

crontab:
# m h dom mon dow command
* * * * * /root/fixnet.sh >/dev/null 2>&1

fixnet.sh:
#!/bin/sh

STATE=`ip link | grep " enx" | grep UP | wc -l`
if [ $STATE -gt 0 ]; then
# All good. Exit
exit 0
fi

/usr/sbin/ifup -a
sleep 20

ping -c 1 10.0.0.1 | grep "1 received"
if [ $? -eq 0 ]; then
# Network looks good. Exit.
exit 0
fi

sleep 310
ping -c 1 10.0.0.1 | grep "1 received"
if [ $? -ne 0 ]; then
# The network is still down.
systemctl reboot
fi

(In reply to Sean Kennedy from comment #205)
> I also have the issue.  Using Proxmox 7.2 (Debian Bullseye) with a Lenovo
> M910q core-i7-7700T,  using two TPLink UE300 (RTL8153) USB to 1Gbe Ethernet
> adapters. Each one is stable in a lower USB slot. Swapping the adapters does
> not change the behavior and only impacts the USB device in the higher slot. 
> Changes to different ports without change.

Update - Tried a different dongle - a 2.5Gbe and have two hard drives attached to the system.  Doesn't matter where the 2.5Gbe dongle is attached,  it eventually errors with "WARN Set TR Deq Ptr cmd failed"  And the error rate is only around six times a day right now:

8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN

# dmesg -T | grep xhci
[Tue Sep  6 13:37:13 2022] xhci_hcd 0000:00:14.0: xHCI Host Controller
[Tue Sep  6 13:37:13 2022] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[Tue Sep  6 13:37:13 2022] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000000009810
[Tue Sep  6 13:37:13 2022] usb usb1: Manufacturer: Linux 5.15.39-4-pve xhci-hcd
[Tue Sep  6 13:37:13 2022] xhci_hcd 0000:00:14.0: xHCI Host Controller
[Tue Sep  6 13:37:13 2022] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[Tue Sep  6 13:37:13 2022] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[Tue Sep  6 13:37:13 2022] usb usb2: Manufacturer: Linux 5.15.39-4-pve xhci-hcd
[Tue Sep  6 13:37:13 2022] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[Tue Sep  6 13:37:14 2022] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd
[Tue Sep  6 13:37:14 2022] usb 2-4: new SuperSpeed USB device number 4 using xhci_hcd
[Tue Sep  6 14:39:22 2022] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Tue Sep  6 14:39:22 2022] usb 2-4: new SuperSpeed USB device number 5 using xhci_hcd
[Tue Sep  6 18:44:01 2022] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Tue Sep  6 18:44:01 2022] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Tue Sep  6 18:44:02 2022] usb 2-4: new SuperSpeed USB device number 6 using xhci_hcd
[Tue Sep  6 22:19:06 2022] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Tue Sep  6 22:19:07 2022] usb 2-4: new SuperSpeed USB device number 7 using xhci_hcd

Since this drops the device from the system and offlines the link,  I created a simple script to detect zero UP ethernet devices via cron once a minute and runs a ifnet -a.   It's clunky but works.

crontab:
# m h  dom mon dow   command
* * * * * /root/fixnet.sh >/dev/null 2>&1

fixnet.sh:
#!/bin/sh

STATE=`ip link | grep " enx" | grep UP | wc -l`
if [ $STATE -gt 0 ]; then
  # All good.  Exit
  exit 0
fi

/usr/sbin/ifup -a
sleep 20

ping -c 1 10.0.0.1 | grep "1 received"
if [ $? -eq 0 ]; then
  # Network looks good. Exit.
  exit 0
fi

sleep 310
ping -c 1 10.0.0.1 | grep "1 received"
if [ $? -ne 0 ]; then
  # The network is still down.
  systemctl reboot
fi

Revision history for this message

In Linux Kernel Bug Tracker #202541, james (james-linux-kernel-bugs) wrote on 2022-12-21:

#274

I'm using a 2.5gb ethernet usb device and getting this error intermittently (a dozen times per day).

$ uname -a
Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ lsusb
<snip>
Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G

This is what plays out via /var/log/syslog each time:

Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect, device number 15
Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1: unregister 'cdc_ncm' usb-0000:00:14.0-4, CDC NCM
Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1: Network is down
Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1...
Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process
Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process
Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed Gen 1 USB device number 16 using xhci_hcd
Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=31.00
Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB 10/100/1G/2.5G LAN
Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer: Realtek
Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber: 001000001
Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0: MAC-Address: xx:xx:xx:xx:xx:xx
Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting rx_max = 16384
Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting tx_max = 16384
Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1: register 'cdc_ncm' at usb-0000:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx
Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface naming scheme 'v245'.
Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN.
(then things start back up and the ethernet link goes live again after about 10 seconds)

I'm using a 2.5gb ethernet usb device and getting this error intermittently (a dozen times per day).

$ uname -a
Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ lsusb
<snip>
Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G

This is what plays out via /var/log/syslog each time:

Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect, device number 15
Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1: unregister 'cdc_ncm' usb-0000:00:14.0-4, CDC NCM
Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1: Network is down
Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1...
Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process
Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process
Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed Gen 1 USB device number 16 using xhci_hcd
Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=31.00
Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB 10/100/1G/2.5G LAN
Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer: Realtek
Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber: 001000001
Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0: MAC-Address: xx:xx:xx:xx:xx:xx
Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting rx_max = 16384
Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting tx_max = 16384
Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1: register 'cdc_ncm' at usb-0000:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx
Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface naming scheme 'v245'.
Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN.
(then things start back up and the ethernet link goes live again after about 10 seconds)

Revision history for this message

In Linux Kernel Bug Tracker #202541, james (james-linux-kernel-bugs) wrote on 2023-01-03:

#275

FYI: I have built a kernel with the previously (on this thread) discussed patch (on a 5.4 kernel) and I still have the error multiple times per day.

(In reply to James H from comment #207)
> I'm using a 2.5gb ethernet usb device and getting this error intermittently
> (a dozen times per day).
>
> $ uname -a
> Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC
> 2022 x86_64 x86_64 x86_64 GNU/Linux
>
>
> $ lsusb
> <snip>
> Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB
> 10/100/1G/2.5G
>
>
>
> This is what plays out via /var/log/syslog each time:
>
> Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect,
> device number 15
> Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd 0000:00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1:
> unregister 'cdc_ncm' usb-0000:00:14.0-4, CDC NCM
> Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd 0000:00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd 0000:00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1:
> Network is down
> Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1...
> Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process
> Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process
> Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed
> Gen 1 USB device number 16 using xhci_hcd
> Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device
> found, idVendor=0bda, idProduct=8156, bcdDevice=31.00
> Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device
> strings: Mfr=1, Product=2, SerialNumber=6
> Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB
> 10/100/1G/2.5G LAN
> Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer:
> Realtek
> Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber:
> 001000001
> Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0:
> MAC-Address: xx:xx:xx:xx:xx:xx
> Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting
> rx_max = 16384
> Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting
> tx_max = 16384
> Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1:
> register 'cdc_ncm' at usb-0000:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx
> Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface
> naming scheme 'v245'.
> Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation
> is unset or enabled, the speed and duplex are not writable.
> Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN.
> (then things start back up and the ethernet link goes live again after about
> 10 seconds)

FYI: I have built a kernel with the previously (on this thread) discussed patch (on a 5.4 kernel) and I still have the error multiple times per day.

(In reply to James H from comment #207)
> I'm using a 2.5gb ethernet usb device and getting this error intermittently
> (a dozen times per day).
> 
> $ uname -a
> Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC
> 2022 x86_64 x86_64 x86_64 GNU/Linux
> 
> 
> $ lsusb
> <snip>
> Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB
> 10/100/1G/2.5G 
> 
> 
> 
> This is what plays out via /var/log/syslog each time:
> 
> Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect,
> device number 15
> Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd 0000:00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1:
> unregister 'cdc_ncm' usb-0000:00:14.0-4, CDC NCM
> Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd 0000:00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd 0000:00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1:
> Network is down
> Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1...
> Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process
> Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process
> Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed
> Gen 1 USB device number 16 using xhci_hcd
> Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device
> found, idVendor=0bda, idProduct=8156, bcdDevice=31.00
> Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device
> strings: Mfr=1, Product=2, SerialNumber=6
> Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB
> 10/100/1G/2.5G LAN
> Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer:
> Realtek
> Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber:
> 001000001
> Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0:
> MAC-Address: xx:xx:xx:xx:xx:xx
> Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting
> rx_max = 16384
> Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting
> tx_max = 16384
> Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1:
> register 'cdc_ncm' at usb-0000:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx
> Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface
> naming scheme 'v245'.
> Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation
> is unset or enabled, the speed and duplex are not writable.
> Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN.
> (then things start back up and the ethernet link goes live again after about
> 10 seconds)

Revision history for this message

In Linux Kernel Bug Tracker #202541, svmohr (svmohr-linux-kernel-bugs) wrote on 2023-08-20:

#276

Download full text (4.2 KiB)

I also get random disconnects on kernel 6.3.0-7-generic with a Samsung T7 Shield external SSD drive. Unfortunately it is hard to reproduce this error, it usually takes hours before it occurs the first time.

System:
  Kernel: 6.3.0-7-generic arch: x86_64 bits: 64 compiler: N/A Console: pty pts/10 Distro: Ubuntu
    23.10 (Mantic Minotaur)
Machine:
  Type: Server System: Supermicro product: C9Z390-PGW v: 0123456789 serial: <filter>
  Mobo: Supermicro model: C9Z390-PGW v: 1.01A serial: <filter> UEFI: American Megatrends v: 1.3
    date: 06/03/2020
CPU:
  Info: 8-core model: Intel Core i9-9900K bits: 64 type: MT MCP arch: Coffee Lake rev: D cache:
    L1: 512 KiB L2: 2 MiB L3: 16 MiB
  Speed (MHz): avg: 3687 high: 5002 min/max: 800/5000 cores: 1: 5002 2: 3600 3: 3600 4: 3600
    5: 3600 6: 3600 7: 3600 8: 3600 9: 3600 10: 3600 11: 3600 12: 3600 13: 3600 14: 3600 15: 3600
    16: 3600 bogomips: 115200
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx

/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 4: Dev 10, If 0, Class=Mass Storage, Driver=uas, 10000M
        ID 04e8:61fb Samsung Electronics Co., Ltd

BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic root=UUID=2c8c7990-bb1d-47dc-a70c-0272867b1807 ro quiet splash intel_iommu=on iommu=pt pcie_aspm=off initcall_blacklist=sysfb_init rd.modules-load=vf
io-pci vfio_pci.ids=10de:1e07,10de:10f7,10de:1ad6,10de:1ad7,1462:3710 vt.handoff=7

[349280.239403] usb 2-4: USB disconnect, device number 9
[349280.239689] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[349280.239695] usb 2-4: cmd cmplt err -108
[349280.239702] sd 9:0:0:0: [sdh] tag#13 uas_zap_pending 0 uas-tag 1 inflight: CMD
[349280.239705] sd 9:0:0:0: [sdh] tag#13 CDB: Write(16) 8a 00 00 00 00 00 d3 28 e4 00 00 00 00 d8 00 00
[349280.239724] sd 9:0:0:0: [sdh] tag#13 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
[349280.239726] sd 9:0:0:0: [sdh] tag#13 CDB: Write(16) 8a 00 00 00 00 00 d3 28 e4 00 00 00 00 d8 00 00
[349280.239728] I/O error, dev sdh, sector 3542672384 op 0x1:(WRITE) flags 0x8800 phys_seg 27 prio class 2
[349280.239741] device offline error, dev sdh, sector 3542674432 op 0x1:(WRITE) flags 0x8800 phys_seg 35 prio class 2
[349280.239747] device offline error, dev sdh, sector 3542672640 op 0x1:(WRITE) flags 0x8800 phys_seg 24 prio class 2
[349280.239750] device offline error, dev sdh, sector 3542677504 op 0x1:(WRITE) flags 0x8800 phys_seg 45 prio class 2
[349280.239753] device offline error, dev sdh, sector 3542680576 op 0x1:(WRITE) flags 0x8800 phys_seg 41 prio class 2
[349280.239788] device offline error, dev sdh, sector 3542663168 op 0x1:(WRITE) flags 0x8800 phys_seg 35 prio class 2
[349280.239793] device offline error, dev sdh, sector 3542663680 op 0x1:(WRITE) flags 0x8800 phys_seg 29 prio class 2
[349280.239799] device offline error, dev sdh, sector 3542663936 op 0x1:(WRITE) flags 0x8800 phys_seg 26 prio class 2
[349280.299534] sd 9:0:0:0: [sdh] Synchronizing SCSI cache
[349280.523475] sd 9:0:0:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVE...

I also get random disconnects on kernel 6.3.0-7-generic with a Samsung T7 Shield external SSD drive. Unfortunately it is hard to reproduce this error, it usually takes hours before it occurs the first time.

System:
  Kernel: 6.3.0-7-generic arch: x86_64 bits: 64 compiler: N/A Console: pty pts/10 Distro: Ubuntu
    23.10 (Mantic Minotaur)
Machine:
  Type: Server System: Supermicro product: C9Z390-PGW v: 0123456789 serial: <filter>
  Mobo: Supermicro model: C9Z390-PGW v: 1.01A serial: <filter> UEFI: American Megatrends v: 1.3
    date: 06/03/2020
CPU:
  Info: 8-core model: Intel Core i9-9900K bits: 64 type: MT MCP arch: Coffee Lake rev: D cache:
    L1: 512 KiB L2: 2 MiB L3: 16 MiB
  Speed (MHz): avg: 3687 high: 5002 min/max: 800/5000 cores: 1: 5002 2: 3600 3: 3600 4: 3600
    5: 3600 6: 3600 7: 3600 8: 3600 9: 3600 10: 3600 11: 3600 12: 3600 13: 3600 14: 3600 15: 3600
    16: 3600 bogomips: 115200
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx

/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 4: Dev 10, If 0, Class=Mass Storage, Driver=uas, 10000M
        ID 04e8:61fb Samsung Electronics Co., Ltd

BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic root=UUID=2c8c7990-bb1d-47dc-a70c-0272867b1807 ro quiet splash intel_iommu=on iommu=pt pcie_aspm=off initcall_blacklist=sysfb_init rd.modules-load=vf
io-pci vfio_pci.ids=10de:1e07,10de:10f7,10de:1ad6,10de:1ad7,1462:3710 vt.handoff=7

[349280.239403] usb 2-4: USB disconnect, device number 9
[349280.239689] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[349280.239695] usb 2-4: cmd cmplt err -108
[349280.239702] sd 9:0:0:0: [sdh] tag#13 uas_zap_pending 0 uas-tag 1 inflight: CMD
[349280.239705] sd 9:0:0:0: [sdh] tag#13 CDB: Write(16) 8a 00 00 00 00 00 d3 28 e4 00 00 00 00 d8 00 00
[349280.239724] sd 9:0:0:0: [sdh] tag#13 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
[349280.239726] sd 9:0:0:0: [sdh] tag#13 CDB: Write(16) 8a 00 00 00 00 00 d3 28 e4 00 00 00 00 d8 00 00
[349280.239728] I/O error, dev sdh, sector 3542672384 op 0x1:(WRITE) flags 0x8800 phys_seg 27 prio class 2
[349280.239741] device offline error, dev sdh, sector 3542674432 op 0x1:(WRITE) flags 0x8800 phys_seg 35 prio class 2
[349280.239747] device offline error, dev sdh, sector 3542672640 op 0x1:(WRITE) flags 0x8800 phys_seg 24 prio class 2
[349280.239750] device offline error, dev sdh, sector 3542677504 op 0x1:(WRITE) flags 0x8800 phys_seg 45 prio class 2
[349280.239753] device offline error, dev sdh, sector 3542680576 op 0x1:(WRITE) flags 0x8800 phys_seg 41 prio class 2
[349280.239788] device offline error, dev sdh, sector 3542663168 op 0x1:(WRITE) flags 0x8800 phys_seg 35 prio class 2
[349280.239793] device offline error, dev sdh, sector 3542663680 op 0x1:(WRITE) flags 0x8800 phys_seg 29 prio class 2
[349280.239799] device offline error, dev sdh, sector 3542663936 op 0x1:(WRITE) flags 0x8800 phys_seg 26 prio class 2
[349280.299534] sd 9:0:0:0: [sdh] Synchronizing SCSI cache
[349280.523475] sd 9:0:0:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[349280.799817] usb 2-4: new SuperSpeed Plus Gen 2x1 USB device number 10 using xhci_hcd
[349280.820511] usb 2-4: New USB device found, idVendor=04e8, idProduct=61fb, bcdDevice= 1.00
[349280.820516] usb 2-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[349280.820517] usb 2-4: Product: PSSD T7 Shield
[349280.820518] usb 2-4: Manufacturer: Samsung

[349280.830738] scsi host6: uas
[349280.831878] scsi 6:0:0:0: Direct-Access Samsung PSSD T7 Shield 0 PQ: 0 ANSI: 6
[349280.833309] sd 6:0:0:0: Attached scsi generic sg3 type 0
[349280.833566] sd 6:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[349280.833701] sd 6:0:0:0: [sdd] Write Protect is off
[349280.833702] sd 6:0:0:0: [sdd] Mode Sense: 43 00 00 00
[349280.833884] sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[349280.834061] sd 6:0:0:0: [sdd] Preferred minimum I/O size 512 bytes
[349280.834063] sd 6:0:0:0: [sdd] Optimal transfer size 33553920 bytes
[349280.868657] sdd: sdd1 sdd2 sdd3
[349280.868993] sd 6:0:0:0: [sdd] Attached SCSI disk

Ubuntu
linux package

xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

	Status	Importance	Assigned to
Linux	Confirmed	High	linux-kernel-bugs #202541
linux (Debian)	Confirmed	Undecided	Unassigned
linux (Ubuntu)	In Progress	Medium	Unassigned
Trusty	Won't Fix	Medium	Unassigned
Xenial	Confirmed	Medium	Unassigned
Bionic	Confirmed	Medium	Unassigned
Focal	Confirmed	Medium	Unassigned

Ubuntulinux package

xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package