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: Tue, 08 Aug 2023 00:13:41 +0000	[thread overview]
Message-ID: <bug-217122-208809-6vo6nHqZJN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217122-208809@https.bugzilla.kernel.org/>

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

Dmitri (dmitri926@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dmitri926@gmail.com

--- Comment #35 from Dmitri (dmitri926@gmail.com) ---
Hi Mario & Michael,

I was able to test on a physical box. I'm not seeing the "Transfer event TRB
DMA ptr not part of current TD" error in dmesg but not able to capture any
packets either.

$ uname -a
Linux sonylaptop 6.5.0-0.a.test-amd64 #1 SMP PREEMPT_DYNAMIC Debian
6.5~rc4-1~exp1a~test (2023-08-07) x86_64 GNU/Linux

[ 1189.175651] usb 3-2: new high-speed USB device number 5 using xhci_hcd
[ 1189.326329] usb 3-2: New USB device found, idVendor=0e8d, idProduct=7961,
bcdDevice= 1.00
[ 1189.326351] usb 3-2: New USB device strings: Mfr=6, Product=7,
SerialNumber=8
[ 1189.326358] usb 3-2: Product: Wireless_Device
[ 1189.326363] usb 3-2: Manufacturer: MediaTek Inc.
[ 1189.326368] usb 3-2: SerialNumber: 000000000
[ 1189.332931] bluetooth hci1: firmware: direct-loading firmware
mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin
[ 1189.337734] mt7921u 3-2:1.3: firmware: direct-loading firmware
mediatek/WIFI_RAM_CODE_MT7961_1.bin
[ 1195.262160] mt7921u 3-2:1.3: firmware: direct-loading firmware
mediatek/WIFI_RAM_CODE_MT7961_1.bin
[ 1195.276095] mt7921u 3-2:1.3: WM Firmware Version: ____010000, Build Time:
20230526130958
[ 1196.916463] mt7921u 3-2:1.3 wlx00c0cab3c769: renamed from wlan0

    description: Motherboard
       product: VAIO
       vendor: Sony Corporation
       physical id: 0
       version: N/A
       serial: N/A
     *-firmware
          description: BIOS
          vendor: Insyde Corp.
          physical id: 0
          version: R0220DA
          date: 11/18/2013
          size: 128KiB
          capacity: 3MiB
          capabilities: pci pnp upgrade shadowing cdboot bootselect edd
int9keyboard int10video acpi usb smartbattery biosbootspecification netboot
uefi
     *-cpu
          description: CPU
          product: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz
          vendor: Intel Corp.
          physical id: 4
          bus info: cpu@0
          version: 6.58.9
          serial: N/A
          slot: N/A
          size: 2591MHz
     *-usbhost:1
                product: xHCI Host Controller
                vendor: Linux 6.5.0-0.a.test-amd64 xhci-hcd
                physical id: 1
                bus info: usb@4
                logical name: usb4
                version: 6.05
                capabilities: usb-3.00
                configuration: driver=hub slots=4 speed=5000Mbit/s

$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0bda:5729 Realtek Semiconductor Corp. Front Camera
Bus 001 Device 003: ID 0489:e062 Foxconn / Hon Hai BCM43142A0
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 0e8d:7961 MediaTek Inc. Wireless_Device
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ hcxdumptool -L

Requesting physical interface capabilities. This may take some time.
Please be patient...


available wlan devices:

phy idx hw-mac       virtual-mac  m ifname           driver (protocol)
---------------------------------------------------------------------------------------------
  3   6 00c0cab3c769 00c0cab3c769 * wlx00c0cab3c769  mt7921u (NETLINK)

* active monitor mode available
+ monitor mode available
- no monitor mode available


:~/work$ sudo iw dev $IFACE set type monitor
:~/work$ sudo ip link set $IFACE up
:~/work$ sudo iw dev
phy#3
        Interface wlx00c0cab3c769
                ifindex 6
                wdev 0x300000001
                addr d8:5d:fb:08:df:5c
                type monitor
                channel 6 (2437 MHz), width: 20 MHz (no HT), center1: 2437 MHz
                txpower 3.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



$ sudo tshark -i $IFACE
Running as user "root" and group "root". This could be dangerous.
Capturing on 'wlx00c0cab3c769'
 ** (tshark:8102) 20:10:07.839462 [Main MESSAGE] -- Capture started.
 ** (tshark:8102) 20:10:07.839571 [Main MESSAGE] -- File:
"/tmp/wireshark_wlx00c0cab3c769SOIS91.pcapng"
^Ctshark:
0 packets captured

-- 
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-08  0:15 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
2023-08-07 15:47 ` bugzilla-daemon
2023-08-07 16:15 ` bugzilla-daemon
2023-08-08  0:13 ` bugzilla-daemon [this message]

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-6vo6nHqZJN@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.