From: Olivier Sessink <olivier@lx.student.wau.nl>
To: linux-kernel@vger.kernel.org
Subject: probable hardware bug: clock timer configuration lost - probably a VIA686a
Date: Wed, 22 Aug 2001 23:47:20 +0200 [thread overview]
Message-ID: <20010822234720.A12692@fender.fakenet> (raw)
Hi all,
I get a lot of these messages when the system is busy:
probable hardware bug: clock timer configuration lost - probably a VIA686a.
probable hardware bug: restoring chip configuration.
probable hardware bug: clock timer configuration lost - probably a VIA686a.
probable hardware bug: restoring chip configuration.
On: Linux version 2.2.19 (maurice@komodo) (gcc version 2.95.4 20010319
(Debian prerelease)) #3 Wed Aug 22 23:17:20 CEST 2001
Running Debian Potato (stable)
The system is a Intel Pentium 120
The motherboard is a Jetway 542C having the ALI 1542-m1543 aladdin-V chipset
(according to the manual)
This is from /proc/pci:
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Acer Labs Unknown device (rev 4).
Vendor id=10b9. Device id=1541.
Slow devsel. Master Capable. Latency=32.
Non-prefetchable 32 bit memory at 0xd0000000 [0xd0000000].
Bus 0, device 1, function 0:
PCI bridge: Acer Labs Unknown device (rev 4).
Vendor id=10b9. Device id=5243.
Slow devsel. Master Capable. Latency=32. Min Gnt=6.
Bus 0, device 7, function 0:
ISA bridge: Acer Labs M1533 Aladdin IV (rev 195).
Medium devsel. Master Capable. No bursts.
Bus 0, device 8, function 0:
VGA compatible controller: ATI 210888GX (rev 1).
Medium devsel. IRQ 11.
Non-prefetchable 32 bit memory at 0xd5000000 [0xd5000000].
Bus 0, device 15, function 0:
IDE interface: Acer Labs M5229 TXpro (rev 194).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
Min Gnt=2.Max Lat=4.
I/O at 0x2000 [0x2001].
The system further has 2 ISA etherworks3 network cards and that's about it.
Does anyone know what this means? Can I provide useful information (please
tell me how). The system once crashed under heavy load. Memtest86 sais the
memory is OK, so I'm a bit worried the error has something to do with it.
regards,
Olivier
reply other threads:[~2001-08-22 21:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010822234720.A12692@fender.fakenet \
--to=olivier@lx.student.wau.nl \
--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
all inboxes | Powered by JetHome®