On Thu, Jul 15, 1999 at 12:08:07AM -0400, Luoqi Chen wrote:
I've been getting this panic when I've installed new kernels the last
couple of times. The panic is occuring when I have freshly booted the
system with a new kernel and logged on for the first time. It appears
to occur at the
: I realise that will stop the panic from looking at the source code, but
: surely it's just covering up the problem and waiting for it to happen
: later?
:
:I'm pretty it's caused by the INVARIANTS option, similar incidents have been
:reported many times before. The problem with INVARIANTS is
On Thu, Jul 15, 1999 at 01:32:50PM -0400, John W. DeBoskey wrote:
It seems to have dropped the v2 flag...
Mount can only get generic options back again - I went looking for
a way to get the other options back again when I was adding the fstab
and cur options to mount, but couldn't find any.
On Thu, Jul 15, 1999 at 12:18:42PM -0400, Luoqi Chen wrote:
I realise that will stop the panic from looking at the source code, but
surely it's just covering up the problem and waiting for it to happen
later?
I'm pretty it's caused by the INVARIANTS option, similar incidents have been
On Thu, Jul 15, 1999 at 10:01:18AM -0700, Matthew Dillon wrote:
: I realise that will stop the panic from looking at the source code, but
: surely it's just covering up the problem and waiting for it to happen
: later?
:
:I'm pretty it's caused by the INVARIANTS option, similar incidents
On Thu, 15 Jul 1999 21:18:03 +0100, Dominic Mitchell wrote:
This of course begs the question, under what circumstances *should* one
use INVARIANTS?
This has been explained to me before as "when you have the time and
inclination to look into any problems that this might cause or
highlight."
On Thursday, 15 July 1999 at 0:08:07 -0400, Luoqi Chen wrote:
I've been getting this panic when I've installed new kernels the last
couple of times. The panic is occuring when I have freshly booted the
system with a new kernel and logged on for the first time. It appears
to occur at the
