From: Peter Horton <pdh@colonel-panic.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.1ac9
Date: Sat, 10 Feb 2001 09:52:33 +0000 [thread overview]
Message-ID: <20010210095233.B1491@colonel-panic.com> (raw)
In-Reply-To: <3A847252.54AD7579@Hell.WH8.TU-Dresden.De> <E14RMXU-0008DV-00@the-village.bc.nu>
In-Reply-To: <E14RMXU-0008DV-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Feb 09, 2001 at 11:01:13PM +0000
On Fri, Feb 09, 2001 at 11:01:13PM +0000, Alan Cox wrote:
> > I've noticed that -ac9 comes with the "Disable PCI-Master-Read-Caching
> > on VIA" patch that Peter Horton posted a while back. I don't know
> > whether it was applied in Linus' or your tree first, but is it
> > actually verified to fix anything?
>
> Not yet. As the story becomes clear it can either be dropped or pushed
> on
>
It should be dropped I think ...
Different folks found that changing different settings fixed it for
them, so it looks like some kind of internal race in the North bridge
where changing the timings in any way makes it harder to reproduce.
The updated BIOS from Asus definitely fixes it for me, and "PCI Master
Read Caching" is *enabled*. There are quite a few differences in the
setup of the North bridge from the previous BIOS to this one, and I
assume the changes were suggested by VIA.
If there are other people out there who still have this problem we can
probably come up with a patch for the kernel, but isolating which of the
settings are important would be a long job.
Shame VIA won't help :-(
P.
-
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/
prev parent reply other threads:[~2001-02-10 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 21:52 Linux 2.4.1ac9 Alan Cox
2001-02-09 22:42 ` Udo A. Steinberg
2001-02-09 23:01 ` Alan Cox
2001-02-10 9:52 ` Peter Horton [this message]
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=20010210095233.B1491@colonel-panic.com \
--to=pdh@colonel-panic.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sorisor@Hell.WH8.TU-Dresden.De \
/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