From: Arjan van de Ven <arjanv@redhat.com>
To: Dan Hollis <goemon@anime.net>
Cc: Arjan van de Ven <arjanv@redhat.com>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Athlon bug stomper. Pls apply.
Date: Wed, 19 Sep 2001 15:59:34 -0400 [thread overview]
Message-ID: <20010919155934.C17174@devserv.devel.redhat.com> (raw)
In-Reply-To: <20010919152121.A9952@devserv.devel.redhat.com> <Pine.LNX.4.30.0109191249130.26700-100000@anime.net>
In-Reply-To: <Pine.LNX.4.30.0109191249130.26700-100000@anime.net>; from goemon@anime.net on Wed, Sep 19, 2001 at 12:51:07PM -0700
On Wed, Sep 19, 2001 at 12:51:07PM -0700, Dan Hollis wrote:
> On Wed, 19 Sep 2001, Arjan van de Ven wrote:
> > If it were only 5%, I would vote for disabling the optimisation given the
> > number of problems; however it's 2x _and_ you can trigger the bug as normal
> > user from userspace too... so we need to fix the hardware/bios.
>
> But we really dont know what the hell that bit is doing. It might trigger
> some other obscure bugs and make things a real mess.
>
> Until we get some answer from VIA its IMHO a bad idea to start twiddling
> this bit willy-nilly on all machines.
no argument from me there...
next prev parent reply other threads:[~2001-09-19 19:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 21:15 [PATCH] Athlon bug stomper. Pls apply Petr Vandrovec
2001-09-19 19:21 ` Arjan van de Ven
2001-09-19 19:51 ` Dan Hollis
2001-09-19 19:59 ` Arjan van de Ven [this message]
2001-09-19 21:44 ` Eric W. Biederman
2001-09-19 22:13 ` Dan Hollis
2001-09-19 22:49 ` John Alvord
2001-09-19 23:14 ` Dan Hollis
2001-09-19 23:32 ` Daniel T. Chen
2001-09-19 22:55 ` Roberto Jung Drebes
2001-09-21 17:22 ` bill davidsen
2001-09-21 19:13 ` Dan Hollis
2001-09-19 20:52 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2001-09-20 13:08 Petr Vandrovec
2001-09-19 23:33 Leif Sawyer
2001-09-19 14:31 Re[2]: " Liakakis Kostas
2001-09-19 14:43 ` Stefan Smietanowski
2001-09-19 13:47 Re[2]: " Thomas Langås
2001-09-19 14:55 ` Jan Niehusmann
2001-09-19 16:00 ` Linus Torvalds
2001-09-19 17:15 ` safemode
2001-09-19 18:22 ` Stefan Smietanowski
2001-09-19 18:43 ` Re[2]: " Dan Hollis
2001-09-19 18:55 ` Arjan van de Ven
2001-09-19 19:00 ` Roberto Jung Drebes
2001-09-19 19:17 ` Arjan van de Ven
2001-09-19 20:16 ` Dan Hollis
2001-09-19 19:50 ` Ignacio Vazquez-Abrams
2001-09-19 20:01 ` Ignacio Vazquez-Abrams
2001-09-19 20:40 ` Ignacio Vazquez-Abrams
2001-09-19 21:43 ` safemode
2001-09-19 22:22 ` Brad Pepers
2001-09-19 22:28 ` Erno Kuusela
2001-09-19 20:36 ` Simen Thoresen
2001-09-19 20:37 ` Dan Hollis
2001-09-19 20:51 ` Simen Thoresen
2001-09-19 23:00 ` Roberto Jung Drebes
2001-09-19 20:36 ` Vojtech Pavlik
2001-09-19 20:57 ` Dan Hollis
2001-09-19 21:29 ` Vojtech Pavlik
2001-09-19 23:23 ` Luigi Genoni
2001-09-20 9:03 ` VDA
2001-09-20 0:19 ` Re[2]: " Nicholas Knight
2001-09-20 1:27 ` Stefan Smietanowski
2001-09-18 14:51 VDA
2001-09-18 15:43 ` Alan Cox
2001-09-20 4:56 ` Albert D. Cahalan
2001-09-18 17:45 ` Jeff Garzik
2001-09-18 21:39 ` Liakakis Kostas
2001-09-23 23:33 ` Jan Niehusmann
2001-09-24 15:44 ` bill davidsen
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=20010919155934.C17174@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=goemon@anime.net \
--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