Please CC any response. Thanks.
I am having an issue with a Supermicro h8dce motherboard and failure to
recognize a 5th SATA drive after upgrading to Fedora 7.
This motherboard has 8 sata ports that use the sata_nv driver.
The lack of seeing the 5th SATA drive shows up in 2.6.22 kernels, such
as kernel-2.6.22.2-42.fc6 and kernel-2.6.22.1-41.fc7.
The 5th SATA drive can still be detected in 2.6.20 kernels such as
kernel-2.6.20-1.2933.fc6 (I am currently using this kernel).
From dmesg, it appears the reason I am not seeing the 5th SATA drive
(second SATA controller) is the following error:
Aug 30 14:08:03 alcor kernel: sata_nv 0000:80:08.0: Using ADMA mode
Aug 30 14:08:03 alcor kernel: PCI: *Unable to reserve mem region*
#6:1000@dfefd000 for device 0000:80:08.0
Aug 30 14:08:03 alcor kernel: ACPI: PCI interrupt for device
0000:80:08.0 disabled
Aug 30 14:08:03 alcor kernel: sata_nv: probe of 0000:80:08.0 failed with
error -16
sata_nv that comes with the 2.6.22 kernels appear to be version 3.4
while the older kernels comes with version 3.2 (which work). I contacted
Robert Hancock directly about this and he suggested I post an email to LKML.
Motherboard:
http://www.supermicro.com/Aplus/motherboard/Opteron/nForce/H8DCE.cfm
Single AMD Opteron(tm) Processor 244
1 GB of memory.
I can send you the complete dmesg output if you would like.
Thanks!
On 09/05/2007 10:32 AM, Karl Bellve wrote:
>
> Please CC any response. Thanks.
>
> I am having an issue with a Supermicro h8dce motherboard and failure to
> recognize a 5th SATA drive after upgrading to Fedora 7.
>
> This motherboard has 8 sata ports that use the sata_nv driver.
>
> The lack of seeing the 5th SATA drive shows up in 2.6.22 kernels, such
> as kernel-2.6.22.2-42.fc6 and kernel-2.6.22.1-41.fc7.
>
> The 5th SATA drive can still be detected in 2.6.20 kernels such as
> kernel-2.6.20-1.2933.fc6 (I am currently using this kernel).
>
> From dmesg, it appears the reason I am not seeing the 5th SATA drive
> (second SATA controller) is the following error:
>
> Aug 30 14:08:03 alcor kernel: sata_nv 0000:80:08.0: Using ADMA mode
> Aug 30 14:08:03 alcor kernel: PCI: *Unable to reserve mem region*
> #6:1000@dfefd000 for device 0000:80:08.0
> Aug 30 14:08:03 alcor kernel: ACPI: PCI interrupt for device
> 0000:80:08.0 disabled
> Aug 30 14:08:03 alcor kernel: sata_nv: probe of 0000:80:08.0 failed with
> error -16
>
> sata_nv that comes with the 2.6.22 kernels appear to be version 3.4
> while the older kernels comes with version 3.2 (which work). I contacted
> Robert Hancock directly about this and he suggested I post an email to
> LKML.
>
> Motherboard:
> http://www.supermicro.com/Aplus/motherboard/Opteron/nForce/H8DCE.cfm
> Single AMD Opteron(tm) Processor 244
> 1 GB of memory.
>
> I can send you the complete dmesg output if you would like.
>
Open a bugzilla at https://bugzilla.redhat.com and post full dmesg from
the new and old kernels as attachments there.
There seems to be some kind of memory layout problem in 2.6.22...
On Wed, 05 Sep 2007 10:32:38 -0400
"Karl Bellve" <[email protected]> wrote:
>
> Please CC any response. Thanks.
>
> I am having an issue with a Supermicro h8dce motherboard and failure to
> recognize a 5th SATA drive after upgrading to Fedora 7.
Can you send me an lspci -vvxxx so that I can look into this. Might be a
few days with the kernel summit but it should give a clue and may be
linked to ADMA mode
On 09/05/2007 08:31 PM, Alan Cox wrote:
> On Wed, 05 Sep 2007 10:32:38 -0400
> "Karl Bellve" <[email protected]> wrote:
>
>> Please CC any response. Thanks.
>>
>> I am having an issue with a Supermicro h8dce motherboard and failure to
>> recognize a 5th SATA drive after upgrading to Fedora 7.
>
> Can you send me an lspci -vvxxx so that I can look into this. Might be a
> few days with the kernel summit but it should give a clue and may be
> linked to ADMA mode
It's in RH bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=280641
Chuck Ebbert wrote:
> On 09/05/2007 08:31 PM, Alan Cox wrote:
>> On Wed, 05 Sep 2007 10:32:38 -0400
>> "Karl Bellve" <[email protected]> wrote:
>>
>>> Please CC any response. Thanks.
>>>
>>> I am having an issue with a Supermicro h8dce motherboard and failure to
>>> recognize a 5th SATA drive after upgrading to Fedora 7.
>> Can you send me an lspci -vvxxx so that I can look into this. Might be a
>> few days with the kernel summit but it should give a clue and may be
>> linked to ADMA mode
>
> It's in RH bugzilla:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=280641
The last BAR on the nForce4 ADMA controllers on this board are at
0xdfefe000 and 0xdfefd000. But it looks like PnP ACPI is also reserving
those memory ranges:
Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range
0xdfefd000-0xdfefd3ff has been reserved
Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range
0xdfefe000-0xdfefe3ff has been reserved
Which I very much doubt it should be doing, the BIOS doesn't need to
reserve PCI BAR ranges in the ACPI tables. This sounds like a BIOS bug.
You might want to check for an update from Supermicro.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
> > https://bugzilla.redhat.com/show_bug.cgi?id=280641
>
> The last BAR on the nForce4 ADMA controllers on this board are at
> 0xdfefe000 and 0xdfefd000. But it looks like PnP ACPI is also reserving
> those memory ranges:
>
> Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range
> 0xdfefd000-0xdfefd3ff has been reserved
> Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range
> 0xdfefe000-0xdfefe3ff has been reserved
>
> Which I very much doubt it should be doing, the BIOS doesn't need to
> reserve PCI BAR ranges in the ACPI tables. This sounds like a BIOS bug.
> You might want to check for an update from Supermicro.
They may be doing it to force the system out of ADMA mode. Right now we
just blow up in that case but it appears other-OS may fall back (which is
I suspect what we need to be doing)