Anyone else seeing this: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=184593 ? With the last two kernels, 2.6.15-1.2032_FC5 and 2.6.15-1.2038_FC5, the system clock starts running too fast for me. It gains about an hour per day. It runs so fast that NTP won't sync to any clock servers because the jitter grows far too fast. Rebooting to kernel-2.6.15-1.2009.4.2_FC5 works perfectly. I can switch back and forth between the working kernel-2.6.15-1.2009.4.2_FC5 and the two broken kernels, and the behavior shifts between working and running too fast each time. (The hardware clock runs perfectly fine too.) Anyone else seeing it? Any more information that would be useful? I assume this is related to the "timer fixes" from git9 mentioned in the 2028 update, although frankly I don't know enough to be sure. Obviously, this is a blocker for me personally, but I haven't seen any other complaints. John Thacker
Attachment:
pgpHrvwwsmfZX.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
