From: Steve Underwood <steveu@coppice.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kermel ML <linux-kernel@vger.kernel.org>
Subject: Re: VIA 686 timer bugfix incomplete
Date: Thu, 08 Nov 2001 03:29:45 +0800 [thread overview]
Message-ID: <3BE98BA9.7090102@coppice.org> (raw)
In-Reply-To: <E161RcS-0003x8-00@the-village.bc.nu>
Alan Cox wrote:
>>but it seems that the patch was incomplete: The bug is still triggered on my
>>computer using 2.4.14, but the bugfix seems to work whith -ac kernels.
>>
>
> The first piece is in.
>
>
>>you can see what's missing to actually work around the via timer bug. I hope
>>this will go into 2.4.15.
>>
>
> I don't plan to submit it until the locking fixes for the timer access are
> done and we know the real cause
If the messages:
probable hardware bug: clock timer configuration lost - probably a
VIA686a motherboard.
probable hardware bug: restoring chip configuration.
are really related to a VIA686A bug, why do they erratically appear on
Compaq ML370's, which use ServerWorks chip sets? Is there a common bug
between these chip sets? Seems unlikely.
Regards,
Steve
next prev parent reply other threads:[~2001-11-07 19:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 11:50 VIA 686 timer bugfix incomplete Jonas Diemer
2001-11-07 12:15 ` Alan Cox
2001-11-07 19:25 ` Vojtech Pavlik
2001-11-07 19:48 ` Jonas Diemer
2001-11-07 20:14 ` Vojtech Pavlik
2001-11-07 22:32 ` Neale Banks
2001-11-08 8:02 ` Vojtech Pavlik
2001-11-08 9:21 ` Jonas Diemer
2001-11-08 20:08 ` Vojtech Pavlik
[not found] ` <20011108221751.5273484e.diemer@gmx.de>
2001-11-08 21:22 ` Vojtech Pavlik
2001-11-08 21:30 ` george anzinger
2001-11-08 23:30 ` Alan Cox
2001-11-09 8:34 ` Vojtech Pavlik
2001-11-09 17:21 ` george anzinger
2001-11-07 19:29 ` Steve Underwood [this message]
2001-11-08 20:11 ` Vojtech Pavlik
2001-11-09 2:57 ` Steve Underwood
-- strict thread matches above, loose matches on Subject: below --
2001-11-09 19:19 Grover, Andrew
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=3BE98BA9.7090102@coppice.org \
--to=steveu@coppice.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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.