From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220069] [6.13.9] regression USB controller dies
Date: Sun, 04 May 2025 13:58:55 +0000 [thread overview]
Message-ID: <bug-220069-208809-rluHGuQNPG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220069-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220069
--- Comment #33 from Claudio Wunder (cwunder@gnome.org) ---
Created attachment 308090
--> https://bugzilla.kernel.org/attachment.cgi?id=308090&action=edit
Autopsy Result (2)
A 2nd crash happened, sending another autopsy. After this crash I moved the
Monitor Hub (Webcam etc) to Bus 5.
```
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 19f7:0050 RODE Microphones RODECaster Duo
Bus 005 Device 003: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 005 Device 004: ID 0b05:1a53 ASUSTek Computer, Inc. USB Audio
Bus 005 Device 005: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 005 Device 006: ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
Bus 005 Device 007: ID 2e1a:4c03 Insta360 Insta360 Link 2C
Bus 005 Device 008: ID 2109:2211 VIA Labs, Inc. USB2.0 Hub
Bus 005 Device 009: ID 2109:8884 VIA Labs, Inc. USB Billboard Device
Bus 005 Device 010: ID 0cf2:a201 ENE Technology, Inc. 6K7732
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
Bus 006 Device 003: ID 2109:0211 VIA Labs, Inc. USB3.0 Hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 004: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 007 Device 006: ID 1e71:300e NZXT NZXT Kraken Base
Bus 007 Device 009: ID 046d:c54d Logitech, Inc. USB Receiver
Bus 007 Device 011: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller
Bus 007 Device 027: ID 2109:4817 VIA Labs, Inc. USB2.0 Hub
Bus 007 Device 028: ID 1a40:0801 Terminus Technology Inc. USB 2.0 Hub
Bus 007 Device 029: ID 2109:8817 VIA Labs, Inc. USB Billboard Device
Bus 007 Device 030: ID 19f7:004e RODE Microphones RØDECaster Duo
Bus 007 Device 031: ID 31e3:1322 Wooting Wooting 60HE+
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 004: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 008 Device 008: ID 2109:3817 VIA Labs, Inc. USB3.0 Hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 013 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 014 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
```
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-05-04 13:58 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 14:28 [Bug 220069] New: [6.13.9] regression USB controller dies bugzilla-daemon
2025-04-29 20:07 ` [Bug 220069] " bugzilla-daemon
2025-04-29 20:43 ` bugzilla-daemon
2025-04-29 20:45 ` bugzilla-daemon
2025-04-30 5:57 ` bugzilla-daemon
2025-04-30 8:57 ` bugzilla-daemon
2025-04-30 9:42 ` bugzilla-daemon
2025-04-30 9:49 ` bugzilla-daemon
2025-04-30 9:53 ` bugzilla-daemon
2025-04-30 21:36 ` bugzilla-daemon
2025-04-30 22:36 ` bugzilla-daemon
2025-04-30 22:52 ` bugzilla-daemon
2025-05-01 7:29 ` bugzilla-daemon
2025-05-01 7:45 ` bugzilla-daemon
2025-05-01 9:48 ` bugzilla-daemon
2025-05-01 21:04 ` bugzilla-daemon
2025-05-01 21:43 ` bugzilla-daemon
2025-05-01 23:43 ` bugzilla-daemon
2025-05-02 0:07 ` bugzilla-daemon
2025-05-02 0:08 ` bugzilla-daemon
2025-05-02 9:28 ` bugzilla-daemon
2025-05-02 11:02 ` bugzilla-daemon
2025-05-02 11:03 ` bugzilla-daemon
2025-05-03 0:23 ` bugzilla-daemon
2025-05-03 8:08 ` bugzilla-daemon
2025-05-03 12:09 ` bugzilla-daemon
2025-05-03 12:10 ` bugzilla-daemon
2025-05-03 14:00 ` bugzilla-daemon
2025-05-03 17:49 ` bugzilla-daemon
2025-05-03 18:25 ` bugzilla-daemon
2025-05-03 19:09 ` bugzilla-daemon
2025-05-04 11:40 ` bugzilla-daemon
2025-05-04 12:41 ` bugzilla-daemon
2025-05-04 13:58 ` bugzilla-daemon [this message]
2025-05-04 14:17 ` bugzilla-daemon
2025-05-04 17:23 ` bugzilla-daemon
2025-05-05 8:49 ` bugzilla-daemon
2025-05-05 8:58 ` bugzilla-daemon
2025-05-05 9:13 ` bugzilla-daemon
2025-05-05 9:32 ` bugzilla-daemon
2025-05-05 9:40 ` bugzilla-daemon
2025-05-05 9:48 ` bugzilla-daemon
2025-05-05 10:53 ` bugzilla-daemon
2025-05-05 14:07 ` bugzilla-daemon
2025-05-05 21:22 ` bugzilla-daemon
2025-05-05 21:41 ` bugzilla-daemon
2025-05-07 23:02 ` bugzilla-daemon
2025-05-11 11:18 ` bugzilla-daemon
2025-05-11 12:49 ` bugzilla-daemon
2025-05-11 12:53 ` bugzilla-daemon
2025-05-11 12:58 ` bugzilla-daemon
2025-05-11 13:00 ` bugzilla-daemon
2025-05-15 10:05 ` bugzilla-daemon
2025-05-17 16:04 ` bugzilla-daemon
2025-05-18 23:37 ` bugzilla-daemon
2025-05-19 0:02 ` bugzilla-daemon
2025-05-19 0:13 ` bugzilla-daemon
2025-05-19 6:47 ` bugzilla-daemon
2025-05-19 12:08 ` bugzilla-daemon
2025-05-20 16:18 ` bugzilla-daemon
2025-05-20 16:22 ` bugzilla-daemon
2025-05-23 21:43 ` bugzilla-daemon
2025-05-23 21:44 ` bugzilla-daemon
2025-09-12 12:36 ` bugzilla-daemon
2025-09-12 20:41 ` 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-220069-208809-rluHGuQNPG@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.