From: Jim Castleberry <jcastle@in-system.com>
To: linux-kernel@vger.kernel.org
Subject: "clock timer configuration lost" on Serverworks chipset
Date: Wed, 16 May 2001 16:12:18 -0600 [thread overview]
Message-ID: <20010516161218.A28362@osprey.in-system.com> (raw)
I'm getting messages saying "clock timer configuration lost - probably
a VIA686a" from 2.2.19 running on a board using the Serverworks HE
chipset. Reading the list archives it sounds like this problem has
previously been attributed to a possible bug in the VIA chipset.
According to RedHat's bugzilla database, others have seen it on
Serverworks chipsets, too. And it sounds like using "noapic" sometimes
makes it go away, which doesn't make much sense to me.
How well has the problem been nailed down? Could it be that it just
showed up first on VIA and the real cause (and fix) remains to be
discovered? Or does Serverworks somehow have an identical bug in
their chipset?
jcastle
next reply other threads:[~2001-05-16 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 22:12 Jim Castleberry [this message]
2001-05-17 0:17 ` "clock timer configuration lost" on Serverworks chipset Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-05-21 17:52 Jim Castleberry
2001-05-21 18:44 ` Alan Cox
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=20010516161218.A28362@osprey.in-system.com \
--to=jcastle@in-system.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.