From: Matthew Hall <mhall@mhcomputing.net>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-acpi@vger.kernel.org,
Jeff Garzik <jeff@garzik.org>
Subject: Re: sata_nv does not function in kernel > 2.6.20.21... possible ACPI or PCI involvement?
Date: Tue, 15 Jan 2008 04:38:04 +0000 [thread overview]
Message-ID: <20080115043804.GA17040@mhcomputing.net> (raw)
In-Reply-To: <200801141702.26914.bjorn.helgaas@hp.com>
On Mon, Jan 14, 2008 at 05:02:26PM -0700, Bjorn Helgaas wrote:
> I think this is a bug in the BIOS description of the motherboard
> device. In 2.6.20, the PNP system driver reserved ioport resources
> but ignored mmio resources. In 2.6.23, the system driver reserves
> both ioport and mmio resources, which I think is more correct, but
> exposes this bug.
Bjorn,
I complained to Supermicro and mentioned that the beta BIOS they
provided to one of the customers in the Redhat Bugzilla threads did not
solve the issue at all. I also included links to both Bugzilla threads
as well as a link to the mail you sent back to me as snipped above which
contained your excellent analysis of the problem.
> I posted the attached test patch to the redhat bugzilla above, but
> nobody's tested it yet. Can you try it?
The patch applied, booted, ran, and solved the problem perfectly. Do you
want any output or configuration files to verify anything? Let me know
if there is anything I can do to help. Other than that if you think it
is safe to apply this, I am in favor of adding it to the mainline or
other appropriate tree.
> Bjorn
Thanks,
Matthew Hall
next prev parent reply other threads:[~2008-01-15 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 20:59 sata_nv does not function in kernel > 2.6.20.21... possible ACPI or PCI involvement? Matthew Hall
2008-01-15 0:02 ` Bjorn Helgaas
2008-01-15 4:38 ` Matthew Hall [this message]
2008-01-15 16:47 ` Bjorn Helgaas
2008-01-16 21:07 ` Bjorn Helgaas
2008-01-17 19:04 ` Matthew Hall
2008-01-15 22:02 ` Bjorn Helgaas
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=20080115043804.GA17040@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=bjorn.helgaas@hp.com \
--cc=jeff@garzik.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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