Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Nov 2021 15:34:41 +0100
From:      Hans Petter Selasky <hps@selasky.org>
To:        Andrew Turner <andrew@fubar.geek.nz>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: 14-CURRENT Kernel Panic due to USB hub?
Message-ID:  <78ed0a6e-2ef0-46a4-f494-8eeef326d15e@selasky.org>
In-Reply-To: <C3FE68C0-44DB-493F-9C29-C73859840C9B@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> <B1DFC16D-47F6-4803-BF12-406EC96465B9@fubar.geek.nz> <45534c79-311b-d1df-c412-5bd782678cfb@selasky.org> <C3FE68C0-44DB-493F-9C29-C73859840C9B@fubar.geek.nz>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/30/21 15:16, Andrew Turner wrote:
> 
> 
>> On 30 Nov 2021, at 12:35, Hans Petter Selasky <hps@selasky.org> wrote:
>>
>> 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’s just making it less likely to be triggered.
>>> Andrew
>>> [1] https://cgit.freebsd.org/src/commit/?id=601ee53858f6
>>
>> Hi,
>>
>> Could you verify that you are not running out of kernel stack?
> 
> I can still trigger it after doubling the kernel stack size.
> 
>>
>> 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’s memory corruption.
> 
>>
>> 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.

And there is no BIOS / UEFI code still running on that XHCI controller?

--HPS




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?78ed0a6e-2ef0-46a4-f494-8eeef326d15e>