From: TimO <hairballmt@mcn.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible critical VIA vt82c686a chip bug (private question)
Date: Fri, 27 Oct 2000 23:39:56 -0600 [thread overview]
Message-ID: <39FA66AC.A8691CAC@mcn.net> (raw)
In-Reply-To: <20001026173244.B8290@suse.cz> <200010271205.OAA31607@gum04.etpnet.phys.tue.nl> <20001027154122.A923@suse.cz>
Vojtech Pavlik wrote:
>
> I'm *not* sure. It just looks like a reasonable explanation. It doesn't
> happen on Intel chips and older VIA chips, it only happens on new VIA
> chips, and the code is the same all the time. Also, it happens both with
> 2.2 and 2.4 kernels ...
>
> --
> Vojtech Pavlik
> SuSE Labs
>
Do you have a method guaranteed to reproduce this? I have a newer VIA
chipset and haven't (yet) observed this problem.
Host bridge: VIA Technologies, Inc. VT8371 [KX133] (rev 2).
PCI bridge: VIA Technologies, Inc. VT8371 [KX133 AGP] (rev 0).
ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 34).
IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 16).
Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
48).
Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
Controller (rev 32).
===============
-- TimO
--------------------==============++==============--------------------
-
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-28 5:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001026173244.B8290@suse.cz>
2000-10-27 12:04 ` Possible critical VIA vt82c686a chip bug (private question) bart
2000-10-27 13:41 ` Vojtech Pavlik
2000-10-28 5:39 ` TimO [this message]
[not found] <m3d7gnd31m.fsf@test1.mandrakesoft.com>
[not found] ` <Pine.LNX.3.95.1001026115039.12337A-100000@chaos.analogic.com>
2000-10-26 17:03 ` 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
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=39FA66AC.A8691CAC@mcn.net \
--to=hairballmt@mcn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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.