Date: Thu, 11 Mar 2021 23:20:15 -0800 From: Alastair Hogge <agh@riseup.net> To: Alastair Hogge <agh@riseup.net> Cc: freebsd-current@freebsd.org Subject: Re: Asus E45M1-M PRO (panic: malloc(M_WAITOK) with sleeping prohibited) Message-ID: <9ec378ec3287b7c8978fa5c27579af16@riseup.net> In-Reply-To: <YEroReUVQyhWjTxm@albert.catwhisker.org> References: <d443584b3dffa12b03e2dc89bf19f9e2@riseup.net> <3db68a3f1944fa9e099796ff45f1b1a2@riseup.net> <YEroReUVQyhWjTxm@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-03-12 12:04, David Wolfskill wrote: > On Thu, Mar 11, 2021 at 07:57:36PM -0800, Alastair Hogge wrote: >> Turns out, EFI boot stopped working. The following boots but fails with >> ... >> umass0: SCSI over Bulk-Only; quirks = 0x4001 >> umass0:6:0: Attached to scbus6 >> Root mount waiting for: usbus5 CAM >> panic: malloc(M_WAITOK) with sleeping prohibited >> cpuid = 0 >> time = 4 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >> 0xfffffe0081dcf5f0 >> vpanic() at vpanic+0x181/frame 0xfffffe0081dcf640 >> panic() at panic+0x43/frame 0xfffffe0081dcf6a0 >> malloc_dbg() at malloc_dbg+0xd4/frame 0xfffffe0081dcf6c0 >> malloc() at malloc+0x34/frame 0xfffffe0081dcf720 >> disk_alloc() at disk_alloc+0x1c/frame 0xfffffe0081dcf740 >> daregister() at daregister+0x3f4/frame 0xfffffe0081dcf9c0 >> cam_periph_alloc() at cam_periph_alloc+0x57b/frame 0xfffffe0081dcfa90 >> daasync() at daasync+0x2c2/frame 0xfffffe0081dcfb00 >> xpt_async_process_dev() at xpt_async_process_dev+0x152/frame >> 0xfffffe0081dcfb50 >> xpt_async_process() at xpt_async_process+0x334/frame 0xfffffe0081dcfc60 >> xpt_done_process() at xpt_done_process+0x3a3/frame 0xfffffe0081dcfca0 >> xpt_done_td() at xpt_done_td+0xf5/frame 0xfffffe0081dcfcf0 >> fork_exit() at fork_exit+0x80/frame 0xfffffe0081dcfd30 >> fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0081dcfd30 >> --- trap 0, rip = 0, rsp = 0, rbp = 0 --- >> .... > > You may find the change that's in https://reviews.freebsd.org/D29210 > helps -- the trace looks similar to what I saw, and it has worked for > me. > > Note that I only saw the panic while running a kernel with INVARIANTS. Patch works; tested with INVARIANTS only. Thanks all. To good health, Alastair
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ec378ec3287b7c8978fa5c27579af16>