Messages in this thread | | | Date | Tue, 5 Nov 2002 13:50:29 -0500 | From | Jim Paris <> | Subject | Re: [PATCH] Re: time() glitch on 2.4.18: solved |
| |
> could that be the reason a few people have experienced occasionnal jumps > backwards in gettimeofday() a few months ago, which many others could never > reproduce ? Just because of buggy hardware ?
An unpaired read on port 0x40 is almost certainly the cause of e.g.
http://www.uwsg.iu.edu/hypermail/linux/kernel/0206.0/1505.html
and we would expect to see the problem with count==LATCH about 1/11932 of the time, about 0.008% -- almost exactly the value reported in:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0206.3/0043.html
I believe that by adding both the (count > LATCH) check and a second (count == LATCH) check, we can fix both of these.
-jim - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |