From: Nathan Lynch <ntl@pobox.com>
To: "Justin R. Smith" <jsmith@drexel.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Instability in kernel version 2.6.12.5
Date: Sat, 8 Oct 2005 16:38:04 -0500 [thread overview]
Message-ID: <20051008213804.GB3577@otto> (raw)
In-Reply-To: <43455F33.7020102@drexel.edu>
Justin R. Smith wrote:
> funky=
>
> 1. the clock is frozen at about 2331 the previous night. Setting it is
> possible, but it remains frozen at whatever time one set it to.
>
> 2. Any X app one starts hangs.
>
> 3. Many operations take an extraordinarily long time. Rebooting the
> system too > 30 minutes (all spent shutting down. The restart was at the
> normal speed).
I saw behavior quite similar to this on a P4 workstation a few months
ago -- after about 24 hours the system would get all "funky" and
/proc/interrupts showed that timer interrupts had slowed to a trickle.
Updating the BIOS fixed it.
Nathan
next prev parent reply other threads:[~2005-10-08 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 17:30 Instability in kernel version 2.6.12.5 Justin R. Smith
2005-10-06 18:24 ` Linus Torvalds
2005-10-06 20:23 ` David S. Miller
2005-10-07 16:41 ` Romano Giannetti
2005-10-08 21:38 ` Nathan Lynch [this message]
2005-10-10 2:53 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051008213804.GB3577@otto \
--to=ntl@pobox.com \
--cc=jsmith@drexel.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox