Date: Tue, 30 Nov 2021 12:22:18 +0000 From: Andrew Turner <andrew@fubar.geek.nz> To: freebsd-arm@freebsd.org Subject: Re: 14-CURRENT Kernel Panic due to USB hub? Message-ID: <B1DFC16D-47F6-4803-BF12-406EC96465B9@fubar.geek.nz> In-Reply-To: <6F2AD5E1-5AB1-4D08-97F4-84E2905D592B@fubar.geek.nz> References: <fbfa2dcc-ae3f-230b-2f56-3b940b025342@morante.net> <2b555ef9-12fe-6214-79a0-cebce1933771@selasky.org> <5bfb1865-8033-0da6-27e4-3c25fb067cee@morante.net> <6F2AD5E1-5AB1-4D08-97F4-84E2905D592B@fubar.geek.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
I bisected the detached messages back to 601ee53858f6 [1]. If I revert = this change I no longer see this on the console. I am also unable to reproduce the panic with this change reverted. As = the panic can be difficult to reproduce I am unsure if reverting this = change is enough to fix it, or if it=E2=80=99s just making it less = likely to be triggered. Andrew [1] https://cgit.freebsd.org/src/commit/?id=3D601ee53858f6 > On 23 Nov 2021, at 17:34, Andrew Turner <andrew@fubar.geek.nz> wrote: >=20 > Can you create a bug for this in bugzilla so we can keep track of it? >=20 > Andrew >=20 >> On 21 Nov 2021, at 07:18, Daniel Morante via freebsd-arm = <freebsd-arm@freebsd.org> wrote: >>=20 >> Here's the bt: >>=20 >> 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 =3D 108 >> time =3D 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> >>=20 >> 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 >>>>=20 >>>> I suspect these problems are caused by the above = detaching/reattaching. >>>=20 >>> Can you type "bt" in the panic prompt? >>>=20 >>> --HPS >>>=20 >=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B1DFC16D-47F6-4803-BF12-406EC96465B9>