Date: Mon, 21 Mar 2016 08:53:30 -0700 From: Adrian Chadd <adrian@freebsd.org> To: "Jukka A. Ukkonen" <jau789@gmail.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: RPI2 panics while trying sleepq_add Message-ID: <CAJ-VmonpiKF2Kb=Rq1URzgopBBDdqms2nAOzLnfXJ0cCfbG9Gw@mail.gmail.com> In-Reply-To: <56F01049.4020108@gmail.com>
index | next in thread | previous in thread | raw e-mail
hiya,
are you able to post a backtrace ('bt') from the db> prompt? That'll
be a good start in narrowing down what the issue is.
(It's a bad sleep whilst a non-sleep lock is held, but we need to know
the code path :)
-a
On 21 March 2016 at 08:16, Jukka A. Ukkonen <jau789@gmail.com> wrote:
>
> Hello,
>
> Has anyone else seen symptoms similar to those described below?
>
> The RPI2 experiences odd panics displaying complaints like...
>
> <---------->
>
> panic: sleepq_add: td 0xc3a5e370 to sleep on wchan 0xc3afd000 with
> sleeping prohinited
> cpuid = 0
> KBD: enter: panic
> [ thread pid 11 tid 100008 ]
> Stopped at $d.10: lrdb r15, [r15, r15, ror r15]!
> db>
>
> <----------->
>
> It does not seem to matter anything whether the system is busy
> or relatively idle. What seems to be common to these panics is
> that in most cases when they happen the keyboard hasn't been
> touched for a while. This is just a wild guess, but maybe the
> kernel tries to put something in some low energy mode and fails.
>
> If I leave the thing doing something on its own for a while,
> when I get backsome 5 to 15 minutes later the poor RPI2 has
> fallen on its face showing the panic message similar to the
> one shown above.
>
> Have you seen this happening? Any ideas what might be going on?
>
> --jau
>
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonpiKF2Kb=Rq1URzgopBBDdqms2nAOzLnfXJ0cCfbG9Gw>