lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 10 Sep 2007 19:44:32 -0600 From: Robert Hancock <hancockr@...w.ca> To: Chuck Ebbert <cebbert@...hat.com> Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Karl Bellve <Karl.Bellve@...ssmed.edu>, linux-kernel@...r.kernel.org Subject: Re: PCI: Unable to reserve mem region problem Chuck Ebbert wrote: > On 09/05/2007 08:31 PM, Alan Cox wrote: >> On Wed, 05 Sep 2007 10:32:38 -0400 >> "Karl Bellve" <Karl.Bellve@...ssmed.edu> 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 hancockr@...pamshaw.ca Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists