From: Matthew Hall <mhall@mhcomputing.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sata_nv does not function in kernel > 2.6.20.21
Date: Thu, 10 Jan 2008 05:25:20 +0000 [thread overview]
Message-ID: <20080110052520.GA9901@mhcomputing.net> (raw)
In-Reply-To: <4785A1CF.7050006@garzik.org>
On Wed, Jan 09, 2008 at 11:40:47PM -0500, Jeff Garzik wrote:
> 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?).
I will follow up on this with the appropriate subsystem lists ASAP.
Thanks for getting me redirected appropriately.
> 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.
I am not quite sure what to do about this part... my boot device for the
system is on one of the sata_nv channels which remains functional and
does not get disabled by the resource conflict.
How shall I best attempt the suggested workaround without having to
delete the sata_nv driver from the kernel thus rendering the kernel
unbootable on this machine? Is there some way to pass the appropriate
option at boot instead of at module load time or some file I could
modify to enable the specified option in the code?
> Jeff
Thanks for the fast reply!
Matthew Hall
next prev parent reply other threads:[~2008-01-10 5:25 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
2008-01-10 5:25 ` Matthew Hall [this message]
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=20080110052520.GA9901@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).