Re: [OT] Major Clock Drift

Andrew Morton (andrewm@uow.edu.au)
Mon, 12 Feb 2001 22:38:35 +1100


Alan Cox wrote:
>
> > > queued_writes=1;
> > > return;
> > > }
> > > }
> >
> > Unfortunately, that means that if machine crashes in interrupt, it may
> > "loose" printk message. That is considered bad (tm).
>
> The alternative is that the machine clock slides continually and the machine
> is unusable. This is considered even worse by most people

Neither. I was going to dust off my enhanced "bust_spinlocks"
patch which sets a little flag when we're doing an
oops, BUG(), panic() or die(). If the flag
is set, printk() just punches through the lock.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/