[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: kernel/1789: panic under i/o-load
- To: bugs_(_at_)_cvs_(_dot_)_openbsd_(_dot_)_org
- Subject: Re: kernel/1789: panic under i/o-load
- From: "Todd C. Miller" <Todd_(_dot_)_Miller_(_at_)_courtesan_(_dot_)_com>
- Date: Mon, 23 Apr 2001 13:40:02 -0600 (MDT)
- Cc:
- Reply-to: "Todd C. Miller" <Todd_(_dot_)_Miller_(_at_)_courtesan_(_dot_)_com>
The following reply was made to PR kernel/1789; it has been noted by GNATS.
From: "Todd C. Miller" <Todd_(_dot_)_Miller_(_at_)_courtesan_(_dot_)_com>
To: ibo_(_at_)_val-axs_(_dot_)_net
Cc: gnats_(_at_)_openbsd_(_dot_)_org
Subject: Re: kernel/1789: panic under i/o-load
Date: Mon, 23 Apr 2001 13:31:22 -0600
Memory errors can also cause this kind of behavior but if you
are not seeing SEGV's while compiling that's probably not what
is going on. The fact that 2.6 doesn't exhibit the problem also
makes me less suspicious of a hardware problem. Still, it wouldn't
hurt to try a kernel compile torture test on the 2.6 kernel (since that
seems to work for you).
I do things like:
while (1)
make clean bsd || break
end
in the kernel compile dir for long periods of time ;-)
- todd
Visit your host, monkey.org