From: Andrea Arcangeli <andrea@suse.de>
To: Sasi Peter <sape@iq.rulez.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.19pre6aa1 weird error
Date: Sat, 13 Jan 2001 21:24:58 +0100 [thread overview]
Message-ID: <20010113212458.B25855@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.30.0101132007540.11593-100000@iq.rulez.org>
In-Reply-To: <Pine.LNX.4.30.0101132007540.11593-100000@iq.rulez.org>; from sape@iq.rulez.org on Sat, Jan 13, 2001 at 08:10:33PM +0100
On Sat, Jan 13, 2001 at 08:10:33PM +0100, Sasi Peter wrote:
> Jan 13 01:58:17 iq kernel: probable hardware bug: clock timer
> configuration lost - probably a VIA686a.
> Jan 13 01:58:17 iq kernel: probable hardware bug: restoring chip
> configuration.
>
> I get these, do not know why. MB is abit BH6, IDE controllers are the
> onboard and a WinFast CMD648.
>
> Have never seen such before (2.0.x and 2.2.x up till now).
>
> Bug rather in SW maybe?
That's a new check in the 2.2.19pre kernels (not part of the aa patchkit).
It means your timer chip didn't resetted itself to the timeout value (LATCH)
after triggering the irq and in turn it means you are losing system time (you
lose more time the the higher is the irq latency). I don't know the details of
the hardware bug though, maybe somebody else can give more details on it.
It doesn't look like a sw problem (previous kernel would malfunction silenty if
that would happen without such a new sanity check).
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-13 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 19:10 2.2.19pre6aa1 weird error Sasi Peter
2001-01-13 20:24 ` Andrea Arcangeli [this message]
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=20010113212458.B25855@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sape@iq.rulez.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