From: "Michał Pecio" <michal.pecio@gmail.com>
To: Marc SCHAEFER <schaefer@alphanet.ch>
Cc: linux-usb@vger.kernel.org
Subject: Re: Strange issues with UAS URB cancellation
Date: Tue, 3 Sep 2024 17:45:35 +0200 [thread overview]
Message-ID: <20240903174535.6e5e581b@foxbook> (raw)
In-Reply-To: <ZtcVXoI6jNM9Lqbl@alphanet.ch>
> On Tue, Sep 03, 2024 at 03:52:43PM +0200, Marc SCHAEFER wrote:
> Sep 3 15:53:37 video kernel: [ 355.639064] I/O error, dev sdb, sector 13962240 op 0x0:(READ) flags 0x4000 phys_seg 128 prio class 0
> Sep 3 15:53:56 video kernel: [ 374.766217] xhci_hcd 0000:01:00.0: Stop Endpoint Context Error & Stopped on slot 9 ep 10
> Sep 3 15:53:56 video kernel: [ 374.766227] xhci_hcd 0000:01:00.0: Stop Endpoint on slot 9 ep 10 failed with comp 19 ctx_state 3
> Sep 3 15:53:56 video kernel: [ 374.766587] sd 15:0:0:0: [sdb] tag#3 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=225s
> Sep 3 15:53:56 video kernel: [ 374.766593] sd 15:0:0:0: [sdb] tag#3 Sense Key : Illegal Request [current]
> Sep 3 15:53:56 video kernel: [ 374.766596] sd 15:0:0:0: [sdb] tag#3 Add. Sense: Invalid command operation code
> Sep 3 15:53:56 video kernel: [ 374.766601] sd 15:0:0:0: [sdb] tag#3 CDB: Read(16) 88 00 00 00 00 00 00 d5 04 00 00 00 04 00 00 00
> Sep 3 15:53:56 video kernel: [ 374.766603] critical target error, dev sdb, sector 13960192 op 0x0:(READ) flags 0x4000 phys_seg 128 prio class 0
Hmm, this is possibly not a coincidence, but it's also not the same
"ERROR Transfer event TRB DMA ptr not part of current TD" that happened
last week. Let me know if you see the other one, because those messages
should now contain more information thanks to the patch.
But this is interesting in its own right, I will have to think about it.
Maybe it's not a HW bug but a SW one, maybe also on my NEC controller.
Regards,
Michal
next prev parent reply other threads:[~2024-09-03 15:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 19:18 Strange issues with USB device Marc SCHAEFER
2024-08-24 6:44 ` Michał Pecio
2024-08-24 6:51 ` Marc SCHAEFER
2024-08-24 8:44 ` Michał Pecio
2024-08-26 5:17 ` Marc SCHAEFER
2024-09-03 7:48 ` Strange issues with UAS URB cancellation Michał Pecio
2024-09-03 12:55 ` Marc SCHAEFER
2024-09-03 13:22 ` Michał Pecio
2024-09-03 13:50 ` Marc SCHAEFER
2024-09-03 13:52 ` Marc SCHAEFER
2024-09-03 13:55 ` Marc SCHAEFER
2024-09-03 15:45 ` Michał Pecio [this message]
2024-09-03 19:40 ` Marc SCHAEFER
2024-09-04 14:26 ` Mathias Nyman
2024-09-04 16:36 ` Marc SCHAEFER
2024-09-05 13:52 ` Mathias Nyman
2024-09-05 15:01 ` Marc SCHAEFER
2024-09-05 15:06 ` Marc SCHAEFER
2024-09-05 17:24 ` Marc SCHAEFER
2024-09-05 18:20 ` Marc SCHAEFER
2024-09-09 15:24 ` Mathias Nyman
2024-09-09 16:21 ` Marc SCHAEFER
2024-09-11 14:25 ` Mathias Nyman
2024-09-12 15:22 ` Mathias Nyman
2024-08-25 16:32 ` Strange issues with USB device Marc SCHAEFER
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=20240903174535.6e5e581b@foxbook \
--to=michal.pecio@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=schaefer@alphanet.ch \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).