From: Andi Kleen <ak@suse.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
alex@nibbles.it, dac@conglom-o.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: [Bug 8942] dac960 driver stopped working with 2.6.22 kernel series
Date: Sat, 1 Sep 2007 12:18:16 +0200 [thread overview]
Message-ID: <200709011218.17129.ak@suse.de> (raw)
In-Reply-To: <20070831161733.GC14130@parisc-linux.org>
> So anyway, what's actually failing is one of these:
Thanks for the analysis.
In theory we could not fail DAC if the machine has <4GB RAM to work around
such buggy drivers, but then they would fail anyways with >4GB. Also
the failure was intended to allow some drivers to use more efficient non DAC
operation.
> It seems a bit mean to write off *all* VIA bridges as data-corruptors.
> Maybe the people who haven't had problems before can help us start a
> white-list of VIA PCI bridges that don't have a problem with DAC.
The reason I blacklisted all was that there was a small triple of data corruption
reports with VIA bridges. Also it's impossible to get any errata information
out of VIA. And there are not that many >4GB VIA systems because these
chipsets are usually used in lower end systems.
-Andi
prev parent reply other threads:[~2007-09-01 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8942-27@http.bugzilla.kernel.org/>
[not found] ` <20070831151748.37C39108012@picon.linux-foundation.org>
2007-08-31 15:42 ` [Bug 8942] dac960 driver stopped working with 2.6.22 kernel series Andrew Morton
2007-08-31 16:17 ` Matthew Wilcox
2007-08-31 16:47 ` [PATCH] Fix DAC960 driver on machines which don't support 64-bit DMA Matthew Wilcox
2007-08-31 17:25 ` Jeff Garzik
2007-09-01 10:18 ` Andi Kleen [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=200709011218.17129.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alex@nibbles.it \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=dac@conglom-o.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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