* probable hardware bug: clock timer configuration lost
@ 2001-09-21 0:55 lonely wolf
2001-09-21 1:04 ` Alan Cox
0 siblings, 1 reply; 5+ messages in thread
From: lonely wolf @ 2001-09-21 0:55 UTC (permalink / raw)
To: linux-kernel
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.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: probable hardware bug: clock timer configuration lost
2001-09-21 0:55 probable hardware bug: clock timer configuration lost lonely wolf
@ 2001-09-21 1:04 ` Alan Cox
2001-09-21 2:16 ` Benjamin LaHaise
0 siblings, 1 reply; 5+ messages in thread
From: Alan Cox @ 2001-09-21 1:04 UTC (permalink / raw)
To: lonely wolf; +Cc: linux-kernel
> 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...)?
Its harmless. When we detect this we restore the state of the chip
correctly. If anything I should kill the printk but I'd still like to
figure the precise errata issue out
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: probable hardware bug: clock timer configuration lost
2001-09-21 1:04 ` Alan Cox
@ 2001-09-21 2:16 ` Benjamin LaHaise
2001-09-21 9:49 ` lonely wolf
2001-09-21 11:54 ` Alan Cox
0 siblings, 2 replies; 5+ messages in thread
From: Benjamin LaHaise @ 2001-09-21 2:16 UTC (permalink / raw)
To: Alan Cox; +Cc: lonely wolf, linux-kernel
On Fri, Sep 21, 2001 at 02:04:39AM +0100, Alan Cox wrote:
> Its harmless. When we detect this we restore the state of the chip
> correctly. If anything I should kill the printk but I'd still like to
> figure the precise errata issue out
Odd, I just got this during booting of my ALi based boards (never had seen
it before). Are we certain the test is correct?
-ben
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: probable hardware bug: clock timer configuration lost
2001-09-21 2:16 ` Benjamin LaHaise
@ 2001-09-21 9:49 ` lonely wolf
2001-09-21 11:54 ` Alan Cox
1 sibling, 0 replies; 5+ messages in thread
From: lonely wolf @ 2001-09-21 9:49 UTC (permalink / raw)
To: linux-kernel
Benjamin LaHaise wrote:
> > Its harmless. When we detect this we restore the state of the chip
> > correctly. If anything I should kill the printk but I'd still like to
> > figure the precise errata issue out
>
> Odd, I just got this during booting of my ALi based boards (never had seen
> it before). Are we certain the test is correct?
actually I get the message with RH's 7.1 stock kernel, with 2.4.7 (patched
with mosix 1.1.2) and with 2.4.9-ac12. it's always there, waiting for me. I
kind of think to remove the printk, just as Alan suggested, because they are
_very_ annoying. I have big hard disks, but I wouldn't like to have them
filled with logs containing mostly this message :)
--
Manuel Wolfshant linux registered user #131416
network administrator NoBug Consulting Romania
The degree of technical confidence is inversely proportional to the
level of management.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: probable hardware bug: clock timer configuration lost
2001-09-21 2:16 ` Benjamin LaHaise
2001-09-21 9:49 ` lonely wolf
@ 2001-09-21 11:54 ` Alan Cox
1 sibling, 0 replies; 5+ messages in thread
From: Alan Cox @ 2001-09-21 11:54 UTC (permalink / raw)
To: Benjamin LaHaise; +Cc: Alan Cox, lonely wolf, linux-kernel
> Odd, I just got this during booting of my ALi based boards (never had seen
> it before). Are we certain the test is correct?
Not entirely thats why I havent sent that specific change on to Linus.
(He has the quiet early fix one which is vital to boot some old VIA boxes
but not that one)
If you have a box with he thing triggering and a moment of time, tweak the
code to read "low1, high, low2, high2" and take min(low1,low2), with high1
as the test.
Alan
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-09-21 11:49 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-09-21 0:55 probable hardware bug: clock timer configuration lost lonely wolf
2001-09-21 1:04 ` Alan Cox
2001-09-21 2:16 ` Benjamin LaHaise
2001-09-21 9:49 ` lonely wolf
2001-09-21 11:54 ` Alan Cox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox