From: Matthew Hall <mhall@mhcomputing.net>
To: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, matthew@wil.cx
Subject: Re: sata_nv does not function in kernel > 2.6.20.21
Date: Thu, 10 Jan 2008 04:27:59 +0000 [thread overview]
Message-ID: <20080110042759.GA9755@mhcomputing.net> (raw)
In-Reply-To: <20080110033944.GW16309@parisc-linux.org>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
Matthew,
On Wed, Jan 09, 2008 at 08:39:45PM -0700, Matthew Wilcox wrote:
> On Thu, Jan 10, 2008 at 02:47:33AM +0000, Matthew Hall wrote:
> > I am using the Supermicro H8DCE motherboard. Some (not all) of the SATA
> > channels quit working due to some kind of resource conflict when I
> > upgrade to any kernel above 2.6.20.xx series, in my case I am running
> > 2.6.20.21 SMP x86_64 presently.
>
> Could you provide an 'lspci -v' and a 'cat /proc/iomem' for both kernels
> please?
I attached the requested materials to this mail.
> This doesn't seem to be a scsi problem per se, so I'm adding
> linux-kernel and linux-ide -- can you drop linux-scsi from any reply
> please.
Sorry, my mistake... since SATA was located under the SCSI section of
the kernel and I have not posted previously I was not sure where to go
with this one.
[-- Attachment #2: iomem-2.6.20.21.gz --]
[-- Type: application/octet-stream, Size: 575 bytes --]
[-- Attachment #3: iomem-2.6.23.12.gz --]
[-- Type: application/octet-stream, Size: 561 bytes --]
[-- Attachment #4: lspci-verbose-2.6.20.21.gz --]
[-- Type: application/octet-stream, Size: 1393 bytes --]
[-- Attachment #5: lspci-verbose-2.6.23.12.gz --]
[-- Type: application/octet-stream, Size: 1400 bytes --]
next prev parent reply other threads:[~2008-01-10 4:37 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 [this message]
2008-01-10 4:40 ` Jeff Garzik
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=20080110042759.GA9755@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).