his thread which seems to be exactly my issue:
http://openbsd-archive.7691.n7.nabble.com/Re-Current-197-Nov-5-umb0-ucom0-umodem0-detached-td330969.html
For the record, this can be better worked around with a sleep/resume
cycle, no need to reboot.
ound this thread which seems to be exactly my issue:
>
> http://openbsd-archive.7691.n7.nabble.com/Re-Current-197-Nov-5-umb0-ucom0-umodem0-detached-td330969.html
>
> When the issue occurs, the following is written into /var/log/messages:
>
> May 3 14:42:09 carbon /bsd: umb0
sue:
http://openbsd-archive.7691.n7.nabble.com/Re-Current-197-Nov-5-umb0-ucom0-umodem0-detached-td330969.html
When the issue occurs, the following is written into /var/log/messages:
May 3 14:42:09 carbon /bsd: umb0 detached
May 3 14:42:09 carbon /bsd: ucom0 detached
May 3 14:42:09 carbon /bs
Ah right, the bug actually trigs below, so this is the XHCI_DEBUG log for the
whole bug/failure sequence. Great.
> Thanks for your answer. Sorry for the delay.
>
> In /cc to mpi@.
>
>> The first thing I see when looking at your report, is that your USB
>> devices were plugged in via USB3
Thanks for your answer. Sorry for the delay.
In /cc to mpi@.
> The first thing I see when looking at your report, is that your USB
> devices were plugged in via USB3 (XHCI).
It is a m.2 card in a ThinkPad. Yes, as it looks, they use USB3 internal.
> Please recompile your kernel with
llo !
>
> Today I experienced, that umb0 ucom0 umodem0 detached at the same
> time. I can't reproduce it but saw it 1 time with snapshot #194 but
> before not.
[..]
> xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x04: msi
> usb0 at xhci0: USB revision 3.0
Hello !
Today I experienced, that umb0 ucom0 umodem0 detached at the same
time. I can't reproduce it but saw it 1 time with snapshot #194 but
before not.
If I lost the connection in the past, I saw a timeout message at the
xconsole and could simple re-connect. At this time umb0(4) is not
longer
7 matches
Mail list logo
