Re: 14-CURRENT Kernel Panic due to USB hub?

May or may not be related, but here's a bt after a panic while running 
poudriere for a few hours.  I still have hw.usb.disable_enumeration=1 
set.  I'm going to do a new install with the latest snapshot later 
today.  I'll post a bt of that without hw.usb.disable_enumeration once I 
get it.

db> bt
Tracing pid 0 tid 101633 td 0xffffa008230c6580
db_trace_self() at db_trace_self
db_stack_trace() at db_stack_trace+0x11c
db_command() at db_command+0x310
db_command_loop() at db_command_loop+0x54
db_trap() at db_trap+0xf8
kdb_trap() at kdb_trap+0x1c0
handle_el1h_sync() at handle_el1h_sync+0x78
--- exception, esr 0xf2000000
kdb_enter() at kdb_enter+0x44
vpanic() at vpanic+0x1c0
panic() at panic+0x44
deadlkres() at deadlkres+0x2c0
fork_exit() at fork_exit+0x74
fork_trampoline() at fork_trampoline+0x14

I'll find a

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
>