Re: axen Ethernet device errors on both USB3.0 and USB2.0 ports
On Sun, Aug 19, 2018 at 11:40:50AM +0200, Stefan Sperling wrote: > On Sun, Aug 19, 2018 at 11:05:04AM +0200, Stefan Sperling wrote: > > On Sun, Aug 19, 2018 at 09:56:33AM +0200, Remi Locherer wrote: > > > It would help if you could send a clean version that applies to -current. > > > > One of the attachments was in fact clean but yes, this > > thread has been much too noisy to follow easily. > > > > Try this. > > Unfortunately, while this diff does indeed work on xhci(4), I've just > found that this diff breaks axen(4) attached to ehci(4) completely. > > I see several "axen0: rxeof: too short transfer" in dmesg and > almost all packets are lost. Even my Ethernet switch gives up > eventually and disables the port. > > So this diff is not ready to be committed. By now I verified that this is an improvement on xhci. Before I could panic my machine by unplugging axen while transfering date. Also without this diff after some time axen got "stuck" and I needed to unplug (dangerous) to get it working again. I'll prepare machine with ehci to be able to test the next diff. ;-) Remi
Re: Plugging in ADB-enabled Android device makes kernel panic with xhci
On 2018-08-18 23:02:24, Tom Murphy wrote: > >Synopsis:Kernel panic in xhci.c when Android phone with ADB > > [...] > > >How-To-Repeat: > I can reproduce this every time just by enabling ADB on the > phone and connecting it to the OpenBSD machine. > I've been seeing the same panics for about a month or two now. I hadn't filed a bug report because I was hoping I'd be able to find the time to bisect when the panics first started happening. Since I'm not sure if I'll have the time to do this anytime soon, I'd like to at least add the following information. According to the timestamps in the filesystem, I was able to successfuly use ADB to sync my phone to my computer on June 24th. So the panics must have begun some time after that. If you have the time to bisect this, first, try a build from before the above date and confirm that it works for you. Then, try a build from around July 24th to see if it happened before or after that. Then repeat the above until you can narrow down the time frame as much as possible. If you can find the exact commit that broke this, it'll be much easier to fix it. Failing that, being able to say "It worked up until the Nth, but started panicking on the N+1th" it will still make it significantly easier find out what changed and thus, to fix this. -- Bryan
