Date: Wed, 27 Apr 2016 17:15:49 +0200 From: Svatopluk Kraus <onwahe@gmail.com> To: bob prohaska <fbsd@www.zefox.net> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: Another reboot hang Message-ID: <CAFHCsPVjE7yv_Wited_gLAcE2TbWAb31-YMNSUcD19kWDTV7pw@mail.gmail.com> In-Reply-To: <20160426214309.GP71221@www.zefox.net> References: <20160426183030.GN71221@www.zefox.net> <CAFHCsPU94vrXgHRSNPvwAFNE0Hnd-6zzhsCSUGDGkVyGQ6jNMg@mail.gmail.com> <20160426204016.GO71221@www.zefox.net> <CAFHCsPXjxHzHr2-4jiLJThSLQGJOqF9Z3hWXfF=3nH4F=%2BgfFg@mail.gmail.com> <20160426214309.GP71221@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 26, 2016 at 11:43 PM, bob prohaska <fbsd@www.zefox.net> wrote:
> On Tue, Apr 26, 2016 at 11:28:42PM +0200, Svatopluk Kraus wrote:
>>
>> Hmm, it's third command which needs WITNESS option. I added 'show all
>> pcpu' on first place later and did not fix the reference. By breaking
>> to debugger repeatedly I mean - type 'c' in ddb ('continue' command)
>> and then break to debugger again.
>>
>>
> Ok, that sounds much easier. I'll try continuing and returning
> to the debugger first.
Those were general hints how to deal with such situation. In your
case, it looks more like an infinite waiting for something on another
thread not in your backtrace. So the all procs and locks dumps would
be unavoidable. And probably a backtrace of all threads too.
>
> Thanks again!
>
> bob
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFHCsPVjE7yv_Wited_gLAcE2TbWAb31-YMNSUcD19kWDTV7pw>