Robert Hancock wrote:
You can probably avoid this problem by using "notsc" on the kernel
command line. It would seem that somehow the TSC drift is too small for
the kernel to notice on boot, but causes problems anyway..
This sounds familiar, although much larger than what I see, is it
possible for an Intel dual core CPU to do this as well? I sometimes see
very unintuitive timestamps on network stuff.
--
-bill davidsen ([email protected])
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
