Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Dec 1997 08:33:12 +1030
From:      Greg Lehey <grog@lemis.com>
To:        John Polstra <jdp@polstra.com>
Cc:        current@freebsd.org
Subject:   Re: UFS problems on -current (panic: ffs_alloccg: map corrupted)
Message-ID:  <19971217083312.13948@lemis.com>
In-Reply-To: <199712161648.IAA13950@austin.polstra.com>; from John Polstra on Tue, Dec 16, 1997 at 08:48:05AM -0800
References:  <19971215194623.30917@lemis.com> <199712161648.IAA13950@austin.polstra.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 16, 1997 at 08:48:05AM -0800, John Polstra wrote:
> In article <19971215194623.30917@lemis.com>,
> Greg Lehey  <grog@lemis.com> wrote:
>> I've been having a large number of these panics in the last few days
>> after replacing significant parts of my system.  In each case, the
>> system appears to die when writing a large file (the text of "The
>> Complete FreeBSD", about 40 MB).
>
> I had that same panic a few days ago on a 2.2-stable machine.  If I
> remember correctly, it happened during an open(2) call when spooling
> an incoming mail file.

In my case, they occurred during write() calls.

> I don't know whether there was any connection between the disk errors
> and the panic.  It doesn't seem like a disk error should cause this
> kind of panic.

Agreed.

It's beginning to look like my problem is hardware after all.  I
removed the SDRAMs and ran with only 64 MB, and all is fine, despite
more work than usual yesterday.

Greg



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971217083312.13948>