From: lonely wolf <wolfy@nobugconsulting.ro>
To: linux-kernel@vger.kernel.org
Subject: probable hardware bug: clock timer configuration lost
Date: Fri, 21 Sep 2001 03:55:36 +0300 [thread overview]
Message-ID: <3BAA9008.9837EA52@nobugconsulting.ro> (raw)
Hi there
I've got a small problem. Just installed kernel-2.4.9-ac12 on 5
identical boxes. They all use Asus A7A266 motherboards, with Tbirds
running at 1.2 GHz. A lspci gives:
00:00.0 Host bridge: Acer Laboratories Inc. [ALi]: Unknown device 1647
(rev 04)
00:01.0 PCI bridge: Acer Laboratories Inc. [ALi] M5247
00:02.0 USB Controller: Acer Laboratories Inc. [ALi] M5237 USB (rev 03)
00:04.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c4)
00:06.0 USB Controller: Acer Laboratories Inc. [ALi] M5237 USB (rev 03)
00:07.0 ISA bridge: Acer Laboratories Inc. [ALi] M1533 PCI to ISA Bridge
[Aladdin IV]
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139
(rev 10)
00:0d.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev
10)
00:11.0 Bridge: Acer Laboratories Inc. [ALi] M7101 PMU
01:00.0 VGA compatible controller: nVidia Corporation Vanta [NV6] (rev
15)
The problem: especially when copying from a disk to another one (I have
cloned /dev/hda to /dev/hdc, testing both dd if=/dev/hda of=/dev/hdc and
cp -a /dev/hdaN /devc/hdcN) a get _a_lot_ of messages like this one:
probable hardware bug: clock timer configuration lost - probably a
VIA686a motherboard.
probable hardware bug: restoring chip configuration.
Is it dangerous ? Any way to get rid of this phenomemon (maintaining the
hardware...)?
--
Manuel Wolfshant linux registered user #131416
network administrator NoBug Consulting Romania
The degree of technical confidence is inversely proportional to the
level of management.
next reply other threads:[~2001-09-21 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 0:55 lonely wolf [this message]
2001-09-21 1:04 ` probable hardware bug: clock timer configuration lost Alan Cox
2001-09-21 2:16 ` Benjamin LaHaise
2001-09-21 9:49 ` lonely wolf
2001-09-21 11:54 ` 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=3BAA9008.9837EA52@nobugconsulting.ro \
--to=wolfy@nobugconsulting.ro \
--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