Date: Mon, 11 Feb 2013 20:48:56 -0500 From: Brett Wynkoop <wynkoop@wynn.com> To: Ian Lepore <ian@freebsd.org> Cc: Tim Kientzle <tim@kientzle.com>, freebsd-arm@freebsd.org Subject: Re: BeagleBone locked up Message-ID: <20130211204856.713c9ee2@ivory.local> In-Reply-To: <1360629932.4545.150.camel@revolution.hippie.lan> References: <20130210231709.26f122dc@ivory.local> <B4346DD4-BA90-4A2C-A2B3-D5DBB6B68942@kientzle.com> <20130211190606.1c985baf@ivory.local> <1360629932.4545.150.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 11 Feb 2013 17:45:32 -0700 Ian Lepore <ian@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. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 718-717-5435 I would never invade the United States. There would be a gun behind every blade of grass. --Isoroku Yamamoto
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130211204856.713c9ee2>