Contact
Subscribe

Last post on leap seconds.

Jan 1, 2009
Uncategorized

I thought I was done with this. Then, today I saw this. To the best of my knowledge, Fedora 8 didn’t suffer from the bug I originally described several posts ago. I think this one happening at nearly midnight UTC is coincidence.

There’s a “me too” in the comments, but it seems odd that two people on slashdot saw it, but we never heard a peep on the Fedora mailing lists, or in bugzilla. Or even in upstream kernel.org. It could just be coincidence, the story is unsurprisingly short on details. I guess slashdot stories are easier to write than bug reports. But without additional debugging info we won’t ever know. Bear in mind that last time we saw a crash of this nature it didn’t affect everyone then either.

It was only by chance I managed to catch the backtrace in the `06 crash. I actually had two locked up machines, but one had its screen blanked, and wouldn’t unblank. The other machine had blanking disabled (setterm -blank 0) and thankfully, had also been set up to use a VGA screen resolution so had plenty of lines to display the whole backtrace.

Update: a problem has been found, and fixed.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

8 Comments
Tags , , ,

8 Comments

  1. David  •  Jan 1, 2009 @21:45

    Well, for the record, Fedora 8 here, everything up-to-date, uptime of 9 days, so if it’s a F8 problem, it’s probably hardware-specific.

  2. jldugger  •  Jan 1, 2009 @22:05

    In addition, it’s probably more likely the average fedora user has a Slashdot account than a Fedora bugzilla account.

  3. Stephen Smoogen  •  Jan 1, 2009 @22:55

    There is a long list of me-too’s on the Red Hat Enterprise Mailling lists. Seems a bunch of different people with RHEL-4 and Slackware-12.0 were bitten. No idea how many

  4. davej  •  Jan 1, 2009 @23:01

    Interesting. Doesn’t make a huge amount of sense, as none of the RHEL releases were tickless, and before that the code in question hadn’t been changed in forever.

  5. Laurens  •  Jan 2, 2009 @05:06

    Actually there are at least 2 “me too”s. Mine wasn’t modded up. And on Debian not Fedora.

    I admit this could be coincidence, but my box has been running without a problem for over 3 years now.

    Like yours my screen blanked so no possibility to get a backtrace. But couldn’t this be a bug which only occurs under very specific circumstances? Guessing here: but what about NTP updating the system clock at exactly 23:59:60?

  6. Kevin  •  Jan 2, 2009 @10:13

    Dave, my F8 machine crashed right around that time as well. I was running a pretty upto date Fedora 8 on x86_64. There was nothing in my /var/log/messages and I could not get the screen to come up before I rebooted the box so I was unable to see any crash messages.

  7. Brian  •  Jan 2, 2009 @14:50

    We had our slack 12 box shoot to 100% CPU and need to be shut down. Running under Xen.

  8. Anon  •  Jan 3, 2009 @14:16

    Some brave soul collected the leap second crash slashdot reports together and posted them to the LKML – http://lkml.org/lkml/2009/1/2/276 .



  • huaglahglah huaglahglah