From: Matthew Hall <mhall@mhcomputing.net>
To: linux-scsi@vger.kernel.org
Subject: sata_nv does not function in kernel > 2.6.20.21
Date: Thu, 10 Jan 2008 02:47:33 +0000 [thread overview]
Message-ID: <20080110024733.GC9461@mhcomputing.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2519 bytes --]
Hello Storage Controller Experts,
I am writing this mail to you to request your assistance in resolving a
functionality regression in my sata_nv controller driver in recent Linux
kernels. I am hoping you can assist me in finding a solution to this
because my TV tuner card is dependent on some fixes in the newer kernels
but using the newer kernels causes some of my storage volumes to be
unreadable, thereby putting me in a catch-22 situation. Please let me
know if any other omitted information is required for diagnostics.
Sorry for the delay in contacting you promptly but:
1) I attempted to contact the maintainer listed directly in the driver
source code and he never replied.
2) I was holding out the mistaken hope that the problem was transient
and would be resolved without my intervention.
Disclaimer: I am sure one of you will notice I am using the nvidia
binary video graphics driver on this system... I say this to provide
full disclosure that I am aware of the implications and of course I am
willing to disable the driver for diagnostic purposes. I have tried
running the system without the driver loaded and did not find any change
in behavior but if you think it is part of the problem please let me
know.
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.
The boot error which appears in dmesg for the missing SATA channels on
2.6.23.12 is pasted below and a compressed copy of my configuration file
for 2.6.23.12 is attached.
The dmesg for 2.6.20.21 is attached and note the configuration is the
same except for being run through make oldconfig.
Best Regards,
Matthew Hall
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
[-- Attachment #2: config-2.6.23.12.gz --]
[-- Type: application/octet-stream, Size: 9733 bytes --]
[-- Attachment #3: dmesg-2.6.20.21.gz --]
[-- Type: application/octet-stream, Size: 6329 bytes --]
next reply other threads:[~2008-01-10 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 2:47 Matthew Hall [this message]
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
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=20080110024733.GC9461@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.