From: Jeff Garzik <jeff@garzik.org>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: linux-scsi@vger.kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sata_nv does not function in kernel > 2.6.20.21
Date: Wed, 09 Jan 2008 23:40:47 -0500 [thread overview]
Message-ID: <4785A1CF.7050006@garzik.org> (raw)
In-Reply-To: <20080110024733.GC9461@mhcomputing.net>
Matthew Hall wrote:
> ACPI: PCI Interrupt Link [LT3D] enabled at IRQ 46
> ACPI: PCI Interrupt 0000:80:07.0[A] -> Link [LT3D] -> GSI 46 (level,
> low) -> IRQ 46
> sata_nv 0000:80:07.0: Using ADMA mode
> PCI: Unable to reserve mem region #6:1000@dfefe000 for device
> 0000:80:07.0
> ACPI: PCI interrupt for device 0000:80:07.0 disabled
> sata_nv: probe of 0000:80:07.0 failed with error -16
> ACPI: PCI Interrupt Link [LT2E] enabled at IRQ 45
> ACPI: PCI Interrupt 0000:80:08.0[A] -> Link [LT2E] -> GSI 45 (level,
> low) -> IRQ 45
> sata_nv 0000:80:08.0: Using ADMA mode
> PCI: Unable to reserve mem region #6:1000@dfefd000 for device
> 0000:80:08.0
> ACPI: PCI interrupt for device 0000:80:08.0 disabled
> sata_nv: probe of 0000:80:08.0 failed with error -16
Error -16 is EBUSY, which causes the driver load to fail due to the
"Unable to reserve mem region" message.
This means that the sata_nv driver needed to use PCI BAR 6, but was
unable to for some reason. Given that sata_nv uses devres like other
libata drivers, IMO the likely cause is outside the ATA subsystem (PCI?
ACPI?).
One workaround to try is setting sata_nv module option 'adma' to zero
(0), in the hopes that it ignores that final region and work anyway.
Jeff
next prev parent reply other threads:[~2008-01-10 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080110024733.GC9461@mhcomputing.net>
2008-01-10 3:39 ` sata_nv does not function in kernel > 2.6.20.21 Matthew Wilcox
2008-01-10 4:27 ` Matthew Hall
2008-01-10 4:40 ` Jeff Garzik [this message]
2008-01-10 5:25 ` Matthew Hall
2008-01-10 5:45 ` Jeff Garzik
2008-01-11 15:17 ` Alan Cox
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=4785A1CF.7050006@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mhall@mhcomputing.net \
/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;
as well as URLs for NNTP newsgroup(s).