Messages in this thread | | | Date | Mon, 14 Jan 2008 13:11:58 +0200 | From | Tuomo Valkonen <> | Subject | Re: The ext3 way of journalling |
| |
On 2008-01-14 10:57 +0100, Bernd Petrovitsch wrote: > That leads to the question why the clock starts to run like crazy at > some time so that `ntpd` can't cope with it.
I do wonder whether the PSU could've been causing it. Now that think about it, I got the PSU around two years ago, just like I compiled 2.6.14. This PSU coincidentally seems to have been the cause of the crash that started this thread, and went completely silent during the same day, on the third crash. But even if the PSU could cause the timer interrupt to signal too frequently or so, doesn't explain why nearly always after a crash (when journal recovery would be the normal course of action), fsck starts checking with absurd intervals since last check, whereas there's no trouble booting after normal shutdown.
-- Tuomo
| |