Re: 14-CURRENT Kernel Panic due to USB hub?
- Reply: Andrew Turner : "Re: 14-CURRENT Kernel Panic due to USB hub?"
- In reply to: Hans Petter Selasky : "Re: 14-CURRENT Kernel Panic due to USB hub?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 21 Nov 2021 07:18:03 UTC
Here's the bt: ugen0.2: <Generic 4-Port USB 3.0 Hub> at usbus0 (disconnected) uhub5: at uhub0, port 1, addr 1 (disconnected) uhub5: detached ugen0.2: <Generic 4-Port USB 3.0 Hub> at usbus0 uhub5 numa-domain 0 on uhub0 uhub5: <Interrupt In Interface> on usbus0 uhub5: 4 ports with 4 removable, self powered ugen0.2: <Generic 4-Port USB 3.0 Hub> at usbus0 (disconnected) uhub5: at uhub0, port 1, addr 1 (disconnected) uhub5: detached panic: data abort with spinlock held cpuid = 108 time = 1637478997 KDB: stack backtrace: db_trace_self() at db_trace_self KDB: enter: panic [ thread pid 11 tid 100111 ] Stopped at kdb_enter+0x44: undefined f901411f db> bt Tracing pid 11 tid 100111 td 0xffffa00005619580 db_trace_self() at db_trace_self db> On 11/12/2021 5:52 AM, Hans Petter Selasky wrote: > On 11/12/21 00:43, Daniel Morante via freebsd-arm wrote: >> ugen0.2: <Generic 4-Port USB 3.0 Hub> at usbus0 (disconnected) >> uhub5: at uhub0, port 1, addr 1 (disconnected) >> uhub5: detached >> ugen0.2: <Generic 4-Port USB 3.0 Hub> at usbus0 >> uhub5 numa-domain 0 on uhub0 >> uhub5: <Interrupt In Interface> on usbus0 >> uhub5: 4 ports with 4 removable, self powered >> >> I suspect these problems are caused by the above detaching/reattaching. > > Can you type "bt" in the panic prompt? > > --HPS >