On Thu, Feb 06, 2020 at 04:46:08PM +0100, Adam Wolk wrote: > On Tue, Feb 04, 2020 at 03:19:17PM +1100, Kenneth R Westerback wrote: > > On Sun, Feb 02, 2020 at 10:19:44PM -0500, Kenneth R Westerback wrote: > > > On Mon, Feb 03, 2020 at 12:30:18AM +0100, Adam Wolk wrote: > > > > On Sun, Feb 02, 2020 at 04:06:38PM -0500, Kenneth Westerback wrote: > > > > > A kernel with XHCI_DEBUG may supply useful info. > > > > > > > > > > > > > I'm currently running with the XHCI_DEBUG enabled in the kernel. > > > > Attaching a dmesg and will report back if I manage to reproduce > > > > the issue on it. > > > > > > > > Look for: > > > > > > > > OpenBSD 6.6-current (XHCI_DEBUG) #0: Sun Feb 2 23:55:04 CET 2020 > > > > mulander@napalm.local:/sys/arch/amd64/compile/XHCI_DEBUG > > > > > > > > in the trace below. > > > > > > > > Between the first two panics I had roughly 1h of usage. You can > > > > see that on the clock from ddb photos. I don't have a reliable > > > > way to reproduce however I wasn't able to trigger it with the xhci.c > > > > commit 1.111 reverted - had several hours of uptime with solid load. > > > > > > > > With the XHCI_DEBUG enabled I tried forcing the issue by generating load > > > > (large downloads, speedtests, running pkg_add and trying to load chrome > > > > with HD videos). No luck so far. > > > > > > > > > Testing the device on the EHCI port I see in your dmesg would also be > > > > > useful to confirm the problem is likely in xhci vs run. > > > > > > > > > > > > > I will attempt that if I manage to reproduce the issue one more time on > > > > the xhci port. > > > > > > > > > A quick test with an older run device plugged into my Lenovo e595 has > > > > > not > > > > > panic'ed yet. > > > > > > > > > > Are you connecting to an ' N' access point or 'G', or ... > > > > > > > > > > > > > I am using the same setup on all reboots. > > > > > > > > Currently: IEEE802.11 autoselect (OFDM9 mode 11g) > > > > > > I have scrounged two run(4) devices from the scrap heap and both fail > > > during a reposync. No panic, just "txerr? code=4" messages before they > > > cease to pass traffic. Both with 'G' and 'N'. > > > > > > Unfortunately they fail the same way with or without r1.111. :-( So I > > > *suspect* this is a different problem than yours. But I will see if > > > any of my older machines have the same Intel xHCI interface as your > > > box and perhaps they will fail differently there. Tomorrow. > > > > > > .... Ken > > > > My x230 has Intel xHCI series 7. And the run(4) devices either work, > > or fail the same way as on the AMD xHCI in my E595. > > > > Amazon says they can't provide one of the devices you are > > using. Poking around to see if I can find one with at least the same > > chip inside. > > > > .... Ken > > I have been running the same kernel (without any changes reverted) and > XHCI DEBUG on since the time of my last email. > > I unfortunately wasn't able to reproduce the issue and it didn't happen > naturally so far. > > I appreciate your help but I don't want to take more of your time > with an unreproducible bug. I will let you know as soon as I manage to > reproduce it and grab more data. > > Regards, > Adam
Noted. Thanks. .... Ken
