BeagleBone locked up
Ian Lepore
ian at FreeBSD.org
Tue Feb 12 14:58:51 UTC 2013
On Mon, 2013-02-11 at 20:48 -0500, Brett Wynkoop wrote:
> On Mon, 11 Feb 2013 17:45:32 -0700
> Ian Lepore <ian at freebsd.org> wrote:
>
> > On Mon, 2013-02-11 at 19:06 -0500, Brett Wynkoop wrote:
> > > Greeting-
> > >
> > > While building a kernel the Bone stopped responding on the net and
> > > this is what I found on the console:
> > >
> > > ti_mmchs0: Error: current cmd NULL, already done?
> > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 5534, size:
> > > 8192
> > [...]
> > > ti_mmchs0: Error: current cmd NULL, already done?
> > > ifaddr cache = 0xc1fbd700 is deleted
> > > ti_mmchs0: Error: current cmd NULL, already done?
> > > ti_mmchs0: Error: current cmd NULL, already done?
>
> snip
>
> >
> > That's the second report recently of indefinite wait buffer. What it
> > really means is that it has been waiting more than 20 seconds to pull
> > a page (or block of pages) in from swap. That plus the cmd NULL
> > errors tend to point in the direction of the mmchs driver.
> >
> > -- Ian
>
> Greeting-
>
> I am glad that I am passing on needed feedback. I did not have to
> reboot the box, just waited and the console eventually responded again
> and I restarted sshd.
When it gets into that sort of state, can you get a response by hitting
^T on the console (or any open ssh terminal session)? If so, the line
it prints may have a clue about what it's blocked on.
-- Ian
More information about the freebsd-arm
mailing list