Key part of dmesg is:
[76704.227672] cdc_acm 1-1.4:1.0: failed to set dtr/rts
[76704.936301] usb 1-1.4: USB disconnect, device number 11
[76704.951638] blk_update_request: I/O error, dev sdc, sector 1110 op
0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
[76704.951644] Buffer I/O error on dev sdc1,
Public bug reported:
Device is an Adafruit microcontroller board running
https://github.com/adafruit/circuitpython, using the TinyUSB USB stack:
https://github.com/hathach/tinyusb.
Device presents a composite USB device that includes MSC, CDC, HID, and MIDI
Device was commanded to forcibly reform
Another crash, with a different backtrace. with a different board, but
related USB implementation. Since the report above, the underlying USB
implementation on the boards has changed somewhat, but the circumstances
of the crash are similar:
[40859.232293] usb 1-1.3: USB disconnect, device number 3
Thanks for the reply.
TinyUSB runs on the microcontroller board; it is the USB stack
implementation used by the software on the board. So it doesn't touch
the kernel, by definition. It is behaving in some way that is unexpected
to the Linux driver, and causing bad behavior on the part of the drive
I was able to reproduce the problem after a few tries with the
5.7.0-050700-generic kernel. I then started trying older kernels. It
appears the problem started somewhere between 4.10.0 an 4.18.0. But
sometimes it takes several tries to reproduce, so I'll continue some ad-
hoc bisecting to see if I
I'm wrong, I got this to happen on 4.10, which is quite old, so I'm not
sure if it's worth going back much further in time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1871143
Title:
Thank you. Attaching lspci-v output in preparation for reporting to the
linux-usb mailing list. lsusb -v output is already attached to the first
port.
** Attachment added: "lspci-v.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+attachment/5389646/+files/lspci-v.txt
--
You
I brought this up on the linux-usb email list and was told it was more
likely to be an issue in the filesystem code. In addition, that code
(and the USB code) don't expect an MSC USB device to behave badly, and
there's no guarantee that if it does, Linux will not crash. In this
case, the filesystem
>Can we get a title that describes better this bug?
If you are logged in, you can edit the title yourself. Just click the little
circle icon of a pencil to the right of the title.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in U
9 matches
Mail list logo
