Date: Fri, 12 Mar 2021 00:30:42 -0800 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: RPi4 Status and xorg behavior (FreeBSD debug kernel panics for USB storage devices) Message-ID: <07B00E95-6802-4C98-8BD4-46CD5B2D67F3@yahoo.com> In-Reply-To: <453A972C-D4C7-4789-BAD0-78A167019E7B@yahoo.com> References: <AAA4E495-4E9E-4C55-A07E-74D9737EC15B@yahoo.com> <20210307155515.GA4591@www.zefox.net> <67BF2EAC-04AD-4822-99B2-48A99563331F@yahoo.com> <G5ZAfvg49jl5dj40HAnjmwoEKpVSuGp8KmiBrSY_EBLXou6UGBIjU3tVxUuPGKeCvXEovg2d3tqhIGOmQCyb7c3wKsUHJ8xrSasvwXfbqwk=@protonmail.com> <4B963C56-D7E9-42FE-8B8B-B8A425ACE78F@yahoo.com> <20210308011035.GA6603@www.zefox.net> <DB3CD5BA-337E-476F-9F0C-C70401F7D800@yahoo.com> <C500EE5B-B483-4580-8C7C-9B9B013D726B@googlemail.com> <20210308173045.GB13739@www.zefox.net> <4D8FD8EE-6642-46ED-8AAE-CAECB36572F6@yahoo.com> <20210309023348.GA16279@www.zefox.net> <EC4C3040-E86A-45EC-9E4F-0E0F81ED3CBD@yahoo.com> <77D90D34-4403-44F0-A7D7-EEBCDCF745D3@yahoo.com> <453A972C-D4C7-4789-BAD0-78A167019E7B@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Mar-11, at 23:57, Mark Millard <marklmi@yahoo.com> wrote: > There is a known FreeBSD error exposed by recent debug > kernels that panic with backtraces like the following > when USB storage is present or plugged in, not just > on aarch64 or armv7/6 but in general: > > panic: malloc(M_WAITOK) with sleeping prohibited > cpuid = 0 > time = 1615452946 > KDB: stack backtrace: > db_trace_self() at db_trace_self > db_trace_self_wrapper() at db_trace_self_wrapper+0x30 > vpanic() at vpanic+0x184 > panic() at panic+0x44 > malloc_dbg() at malloc_dbg+0xf8 > malloc() at malloc+0x30 > disk_alloc() at disk_alloc+0x1c > daregister() at daregister+0x3b8 > cam_periph_alloc() at cam_periph_alloc+0x528 > daasync() at daasync+0x260 > xpt_async_process_dev() at xpt_async_process_dev+0x194 > xpt_async_process() at xpt_async_process+0x3a0 > xpt_done_process() at xpt_done_process+0x314 > xpt_done_td() at xpt_done_td+0xd8 > fork_exit() at fork_exit+0x74 > fork_trampoline() at fork_trampoline+0x14 > > It turns out that the snapshot: > > FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210311-15565e0a217-257277.img.xz > > Is an example of having this problem. So are the > other "20210311" snapshots with debug kernels. > > Recent https://artifact.ci.freebsd.org/snapshot/ > materials will also have the problem (debug kernels). > > The http://ftp3.freebsd.org/pub/FreeBSD/releases/ > material do not have debug kernels and so will not > panic and should work as long as various memory > allocations do not fail. > > https://reviews.freebsd.org/D29210/ is for a patch in > review for the issue. Various folks have used it to > get debug kernels going for their activities. Looks like the final / was a bad thing to have typed for teh review: https://reviews.freebsd.org/D29210 works better. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07B00E95-6802-4C98-8BD4-46CD5B2D67F3>