Date: Wed, 1 Dec 2021 11:39:17 +0000 From: Andrew Turner <andrew@fubar.geek.nz> To: Hans Petter Selasky <hps@selasky.org> Cc: freebsd-arm@freebsd.org Subject: Re: 14-CURRENT Kernel Panic due to USB hub? Message-ID: <E393543F-CE4C-4B27-BDB6-2B5C2440612B@fubar.geek.nz> In-Reply-To: <a281fe07-7963-5ff4-f18a-bbe7eb8744c7@selasky.org> 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> <B1DFC16D-47F6-4803-BF12-406EC96465B9@fubar.geek.nz> <45534c79-311b-d1df-c412-5bd782678cfb@selasky.org> <C3FE68C0-44DB-493F-9C29-C73859840C9B@fubar.geek.nz> <78ed0a6e-2ef0-46a4-f494-8eeef326d15e@selasky.org> <3E44BF3B-9181-480E-8D40-09B66203ADB6@fubar.geek.nz> <a281fe07-7963-5ff4-f18a-bbe7eb8744c7@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 30 Nov 2021, at 21:37, Hans Petter Selasky <hps@selasky.org> wrote: >=20 > On 11/30/21 18:21, Andrew Turner wrote: >>> On 30 Nov 2021, at 14:34, Hans Petter Selasky <hps@selasky.org> = wrote: >>>=20 >>> On 11/30/21 15:16, Andrew Turner wrote: >>>>> On 30 Nov 2021, at 12:35, Hans Petter Selasky <hps@selasky.org> = wrote: >>>>>=20 >>>>> On 11/30/21 13:22, Andrew Turner wrote: >>>>>> 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 >>>>>=20 >>>>> Hi, >>>>>=20 >>>>> Could you verify that you are not running out of kernel stack? >>>> I can still trigger it after doubling the kernel stack size. >>>>>=20 >>>>> May this be due to some code in the .text segment which is not = properly aligned? >>>> I would expect to have seen the issue on other HW. The issue looks = more like it=E2=80=99s memory corruption. >>>>>=20 >>>>> If you compile and load USB as modules, does the panic go away? >>>> I am unable to trigger it after removing xhci from the kernel, and = did get a panic after loading the xhci module. >>>> The xhci controller is one that originated in Broadcom. Linux has a = quirk for it to work around an erratum where attaching a USB 1 device = followed by a USB 2 device the linker the latter will come up as USB 1. = They reset the phy when anything less than USB 3 on a disconnect event. >>>=20 >>> And there is no BIOS / UEFI code still running on that XHCI = controller? >> I would expect the UEFI code to not be accessing the XHCI controller = after exiting the loader. >> Andrew >=20 > Hi, >=20 > Could you try to kldload xhci instead of building it into the kernel = config? Maybe you get a different kind of panic that way. I have. I=E2=80=99m hitting the KASSERT at [1]. Looking at the memory = around td->td_pcb->pcb_fpflags makes me think the memory has been = trashed as there are bits set that could never be so in the flags = fields, and kernel pointer values that point to user memory. Andrew [1] = https://cgit.freebsd.org/src/tree/sys/arm64/arm64/trap.c?id=3D6e9309bd3b04= 501b69593900a14e01114c7f2404#n627
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E393543F-CE4C-4B27-BDB6-2B5C2440612B>