From: Arjan van de Ven <arjanv@redhat.com>
To: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stomping on Athlon bug
Date: Thu, 13 Sep 2001 11:17:46 +0100 [thread overview]
Message-ID: <3BA087CA.3BD1D557@redhat.com> (raw)
In-Reply-To: <17613305632.20010913121304@port.imtp.ilyichevsk.odessa.ua>
VDA wrote:
>
> Hi. Below is a modified printout of lspci -vvvxxx
> made on VIA KT133A based mainboard with BIOS version 3R flashed in
> (this system is exhibiting Athlon bug) and on the same system
> with BIOS version YH (which do not trigger bug).
> Each chipset config register which is changed between these two BIOSes
> is underlined with carets "^" with programming details immediately below.
> Each register is then commented with:
> *** 3R BIOS: settings made by 3R BIOS
> *** YH BIOS: settings made by YH BIOS
> *** TODO: is this relevant and what to do
>
> Anyone interested in trying to pin down the bug might
> try to reprogram this chipset along the lines:
> ...
> struct pci_dev *dev;
> dev = pci_find_device(PCI_VENDOR_ID_VIA, 0x0305, NULL);
> if(dev) {
> printk("Trying to stomp on Athlon bug...\n");
> u8 v;
> pci_read_config_byte(dev, 0x52, &v);
> /* set 52.7: Disconnect Enable When STPGNT Detected */
> v |= 0x80;
> pci_write_config_byte(dev, 0x52, v);
> ...
> }
> ...
> I'm not sure where exactly this piece of code should go.
> Anyway, compile K7 optimized kernel with this fix
> and give it a try.
Interesting; This is exactly the bit that the athlon cool thingy that
popped up
here a while ago changed; everybody agreed that it was WAAAAY too
dangerous
back then, because PSU's and voltage regulators wouldn't be able to
cope......
next prev parent reply other threads:[~2001-09-13 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 9:13 Stomping on Athlon bug VDA
2001-09-13 10:06 ` Gergely Tamas
2001-09-13 11:27 ` Gergely Tamas
2001-09-13 10:17 ` Arjan van de Ven [this message]
2001-09-13 12:19 ` Jan Niehusmann
2001-09-13 12:21 ` Arjan van de Ven
2001-09-13 14:02 ` Jan Niehusmann
2001-09-13 16:33 ` Eric W. Biederman
2001-09-13 18:09 ` Roberto Jung Drebes
2001-09-13 11:58 ` Carsten Leonhardt
2001-09-13 15:11 ` Eric W. Biederman
2001-09-14 20:06 ` Pavel Machek
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=3BA087CA.3BD1D557@redhat.com \
--to=arjanv@redhat.com \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--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