All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217122] Regression in xhci driver since 6.1 "Transfer event TRB DMA ptr not part of current TD"
Date: Mon, 07 Aug 2023 07:01:01 +0000	[thread overview]
Message-ID: <bug-217122-208809-IDTyE1kKsR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217122-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217122

--- Comment #32 from Michael (ZeroBeat@gmx.de) ---
Some additional information:

I'm on kernel 6.4.8 and noticed that a WiFi device connected to an USB 3 port
doesn't work:
Bus 002 Device 003: ID 0e8d:7612 MediaTek Inc. MT7612U 802.11a/b/g/n/ac
Wireless Adapter

[ 7280.709821] usb 2-3: New USB device found, idVendor=0e8d, idProduct=7612,
bcdDevice= 1.00
[ 7280.709829] usb 2-3: New USB device strings: Mfr=2, Product=3,
SerialNumber=4
[ 7280.709830] usb 2-3: Product: Wireless 
[ 7280.709832] usb 2-3: Manufacturer: MediaTek Inc.
[ 7280.709833] usb 2-3: SerialNumber: 000000000
[ 7280.970177] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[ 7280.994419] mt76x2u 2-3:1.0: ASIC revision: 76120044
[ 7281.025164] mt76x2u 2-3:1.0: ROM patch build: 20141115060606a
[ 7281.202395] mt76x2u 2-3:1.0: Firmware Version: 0.0.00
[ 7281.202404] mt76x2u 2-3:1.0: Build: 1
[ 7281.202405] mt76x2u 2-3:1.0: Build Time: 201507311614____
[ 7281.928318] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 7281.928840] usbcore: registered new interface driver mt76x2u
[ 7281.942982] mt76x2u 2-3:1.0 wlp22s0f0u3: renamed from wlan0

$ sudo iw dev wlp22s0f0u3 set type monitor
[ 7475.445473] mt76x2u 2-3:1.0 wlp22s0f0u3: entered promiscuous mode

$ sudo ip link set wlp22s0f0u3 up
$ sudo iw dev wlp22s0f0u3 set channel 6
$ iw dev
phy#1
        Interface wlp22s0f0u3
                ifindex 4
                wdev 0x100000001
                addr 00:c0:ca:ad:0e:49
                type monitor
                channel 6 (2437 MHz), width: 20 MHz (no HT), center1: 2437 MHz
                txpower 20.00 dBm
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol
tx-bytes        tx-packets
                        0       0       0       0       0       0       0      
0               0

$ tshark -i wlp22s0f0u3
Capturing on 'wlp22s0f0u3'
 ** (tshark:12534) 08:42:20.045697 [Main MESSAGE] -- Capture started.
 ** (tshark:12534) 08:42:20.045804 [Main MESSAGE] -- File:
"/tmp/wireshark_wlp22s0f0u3LO1981.pcapng"
^Ctshark: 
0 packets captured


$ sudo ip link set wlp22s0f0u3 down
$ sudo iw dev wlp22s0f0u3 set type managed
[ 7479.304196] mt76x2u 2-3:1.0 wlp22s0f0u3: left promiscuous mode

Controller:
                description: USB controller
                product: Renoir/Cezanne USB 3.1
                vendor: Advanced Micro Devices, Inc. [AMD]
                physical id: 0.3
                bus info: pci@0000:30:00.3
                version: 00
                width: 64 bits
                clock: 33MHz
                capabilities: xhci bus_master cap_list
                configuration: driver=xhci_hcd latency=0
                resources: irq:33 memory:fc300000-fc3fffff


Mainboard: MSI B550 A-Pro


While all USB 2 devices are working as expected on this port, none of the USB 3
devices is working. I don't think that it is a driver problem, because I tested
several devices manufactured by different vendors (mt76m rt2800usb).

Unfortunately I got no dmesg message like this user
https://github.com/ZerBea/hcxdumptool/issues/334#issuecomment-1667093519

I guess all this problems are related to each other.

BTW:
A long time ago, we got something similar related to XHCI):
https://bugzilla.kernel.org/show_bug.cgi?id=202541
but that seems to be fixed, now.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-08-07  7:01 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 19:53 [Bug 217122] New: Regression in xhci driver since 6.1 "Transfer event TRB DMA ptr not part of current TD" bugzilla-daemon
2023-03-06  2:04 ` [Bug 217122] " bugzilla-daemon
2023-03-06  9:17 ` bugzilla-daemon
2023-03-06 11:35 ` bugzilla-daemon
2023-03-06 13:15 ` bugzilla-daemon
2023-03-06 21:06 ` bugzilla-daemon
2023-03-06 21:09 ` bugzilla-daemon
2023-03-06 21:18 ` bugzilla-daemon
2023-03-07 20:25 ` bugzilla-daemon
2023-03-23 14:00 ` bugzilla-daemon
2023-03-23 14:59 ` bugzilla-daemon
2023-04-19 16:36 ` bugzilla-daemon
2023-05-06 17:31 ` bugzilla-daemon
2023-05-10 20:06 ` bugzilla-daemon
2023-05-10 20:15 ` bugzilla-daemon
2023-05-10 21:25 ` bugzilla-daemon
2023-05-10 21:51 ` bugzilla-daemon
2023-05-10 21:52 ` bugzilla-daemon
2023-05-10 21:54 ` bugzilla-daemon
2023-05-10 22:23 ` bugzilla-daemon
2023-05-10 22:25 ` bugzilla-daemon
2023-05-10 22:26 ` bugzilla-daemon
2023-05-10 22:28 ` bugzilla-daemon
2023-05-10 22:29 ` bugzilla-daemon
2023-05-12 16:38 ` bugzilla-daemon
2023-05-12 16:45 ` bugzilla-daemon
2023-05-12 16:51 ` bugzilla-daemon
2023-05-12 17:00 ` bugzilla-daemon
2023-08-02 15:48 ` bugzilla-daemon
2023-08-02 16:41 ` bugzilla-daemon
2023-08-02 16:46 ` bugzilla-daemon
2023-08-07  5:12 ` bugzilla-daemon
2023-08-07  7:01 ` bugzilla-daemon [this message]
2023-08-07 15:47 ` bugzilla-daemon
2023-08-07 16:15 ` bugzilla-daemon
2023-08-08  0:13 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-217122-208809-IDTyE1kKsR@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.