From: Vojtech Pavlik <vojtech@suse.cz>
To: Yoann Vandoorselaere <yoann@mandrakesoft.com>
Cc: Martin Mares <mj@suse.cz>,
"Richard B. Johnson" <root@chaos.analogic.com>,
linux-kernel@vger.kernel.org
Subject: Re: Possible critical VIA vt82c686a chip bug (private question)
Date: Fri, 27 Oct 2000 13:15:48 +0200 [thread overview]
Message-ID: <20001027131548.A651@suse.cz> (raw)
In-Reply-To: <m3d7gnd31m.fsf@test1.mandrakesoft.com> <Pine.LNX.3.95.1001026115039.12337A-100000@chaos.analogic.com> <20001026190309.A372@suse.cz> <20001027120220.A5741@atrey.karlin.mff.cuni.cz> <20001027124947.A476@suse.cz> <m38zrablff.fsf@test1.mandrakesoft.com> <20001027130151.A607@suse.cz> <m3y9zaa60d.fsf@test1.mandrakesoft.com>
In-Reply-To: <m3y9zaa60d.fsf@test1.mandrakesoft.com>; from yoann@mandrakesoft.com on Fri, Oct 27, 2000 at 01:16:34PM +0200
On Fri, Oct 27, 2000 at 01:16:34PM +0200, Yoann Vandoorselaere wrote:
> > Which part of the chipset you mean? The PIT (programmable interrupt
> > timer)? That one is standard since XT times. The rest of the ISA bridge?
> > Maybe, but that's mostly BIOS work and shouldn't impact the PIT
> > under sane conditions.
>
> What is strange is that a number of persons seem to be hit by this
> problem... And if VIA didn't corrected it it's probably because
> they are not aware of it...
>
> I think that if such problem occured under windows
> (thinking to the windows user base), VIA would be already in touch.
It can't happen under Windows, because Windows timer runs at 18 Hz
(timer programmed to 65535), while Linux uses 100 Hz (timer programmed
to approx 11920), so when the timer unprograms itself due to the bug to
65535, only Linux notices it, Windows can't.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-27 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3d7gnd31m.fsf@test1.mandrakesoft.com>
[not found] ` <Pine.LNX.3.95.1001026115039.12337A-100000@chaos.analogic.com>
2000-10-26 17:03 ` Possible critical VIA vt82c686a chip bug (private question) Vojtech Pavlik
2000-10-26 17:42 ` Richard B. Johnson
2000-10-26 18:02 ` Vojtech Pavlik
2000-10-26 20:11 ` Yoann Vandoorselaere
2000-10-26 20:16 ` Vojtech Pavlik
2000-10-26 21:05 ` Yoann Vandoorselaere
2000-10-26 21:15 ` Vojtech Pavlik
2000-10-26 21:24 ` Yoann Vandoorselaere
2000-10-26 21:25 ` Vojtech Pavlik
2000-10-27 10:02 ` Martin Mares
2000-10-27 10:49 ` Vojtech Pavlik
2000-10-27 10:58 ` Yoann Vandoorselaere
2000-10-27 11:01 ` Vojtech Pavlik
2000-10-27 11:16 ` Yoann Vandoorselaere
2000-10-27 11:15 ` Vojtech Pavlik [this message]
[not found] <20001026173244.B8290@suse.cz>
2000-10-27 12:04 ` bart
2000-10-27 13:41 ` Vojtech Pavlik
2000-10-28 5:39 ` TimO
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=20001027131548.A651@suse.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@suse.cz \
--cc=root@chaos.analogic.com \
--cc=yoann@mandrakesoft.com \
/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