Re: time() glitch on 2.4.18: solved

[Alan Cox]

On Sun, 2002-11-03 at 19:32, Jim Paris wrote:
> After 180 days of uptime, it's not surprising that there would have
> been one read of the port that failed, triggering the problem, so I
> think the kernel should detect and fix this.  We could just check for
> it: if the returned count > LATCH, read an extra byte from port 0x40,
> as I did.  Or, use the method in do_slow_gettimeoffset, which
> basically resets the 8253's counter if count > LATCH.

We have locking that ought to get that all correct nowdays but I've seen
at least one bios generate half a read in SMM mode

> Any comments?

Have a play with it, if your idea works when you deliberately disturb it
then send in a patch