From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tejun Heo <tj@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
pgnet.trash@gmail.com
Subject: Re: [PATCH 2.6.29-rc7 2/2] x86: disallow DAC for MCP51 PCI bridge
Date: Wed, 4 Mar 2009 09:57:27 +0000 [thread overview]
Message-ID: <20090304095727.707ac18c@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <49ADE9D3.6080000@kernel.org>
On Wed, 04 Mar 2009 11:39:15 +0900
Tejun Heo <tj@kernel.org> wrote:
> MCP51 corrupts DAC transfers. Disallow it. Reported by pgnet on
> bnc#463829.
So you have a single piece of evidence as I read it - from a single
board that represents system with a very common chipset and no supporting
errata information from the vendor.
That bug could easily be a faulty motherboard or dodgy connector or a
specific hardware compatibility issue between two specific components. I
don't think that can be considered sufficient evidence for adding
sledgehammer sized workarounds that harm everyone elses performance and
cripples such systems for certain kinds of work (eg video)
Insufficient evidence and google searches and other bug searches don't
seem to be turning up any parallel cases so for the moment At the very
least someone needs to reproduce the hardware configuration and see the
same problem, and then repeat with a different DAC enabled card.
I don't believe this patch should go in ... yet. More information/testing
is needed.
Alan
next prev parent reply other threads:[~2009-03-04 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 2:32 [PATCH 2.6.29-rc7 1/2] x86: fix iommu=nodac parameter handling Tejun Heo
2009-03-04 2:39 ` [PATCH 2.6.29-rc7 2/2] x86: disallow DAC for MCP51 PCI bridge Tejun Heo
2009-03-04 9:57 ` Alan Cox [this message]
2009-03-04 10:11 ` Tejun Heo
2009-03-04 13:29 ` Alan Cox
2009-03-04 13:36 ` Tejun Heo
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=20090304095727.707ac18c@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pgnet.trash@gmail.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®