Date: Tue, 07 Aug 2007 17:41:47 -0700 From: Mike Harding <mvh@ix.netcom.com> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-stable@freebsd.org Subject: Re: Crash report Message-ID: <1186533707.5244.3.camel@localhost> In-Reply-To: <20070807192626.GA57403@rot26.obsecurity.org> References: <20070807174354.DAC5017921@bsd.mvh> <20070807192626.GA57403@rot26.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yep, have had to do this many many times. I had another crash, during the 'umount' process. Is there possibly a race condition with tinderbox? I generally run the tinderbox as 'idprio 10'... This crash happens with 2 different boxes, doing the same thing. One is an Intel Dell, one is a AMD system. 6.1 was so solid I may go back to it... On Tue, 2007-08-07 at 15:26 -0400, Kris Kennaway wrote: > On Tue, Aug 07, 2007 at 10:43:54AM -0700, Mike Harding wrote: > > > > I have had -lots- of panics since upgrading to 6.2 - my system was > > pretty much 100% before that. One thing I do have on my system is > > some jails, and I also see this crashes during tinderbox builds. I > > upgraded to 6.2-STABLE to see if the crashes were fixed, I still have > > them. Any ideas? memtest shows nothing wrong... > > Try disabling bg fsck, then booting to single user mode and running > fsck -f. You may have residual file system corruption. > > Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1186533707.5244.3.camel>