linux-kernel - Re: Intel DP43BF MB - No PCI Devices detected

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 4 Oct 2010 14:39:36 -0400
From:	"Brian C. Huffman" <bhuffman@...ze.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Intel DP43BF MB - No PCI Devices detected

  On 09/24/2010 05:29 PM, Andrew Morton wrote:
> On Wed, 25 Aug 2010 17:54:45 -0400
> "Brian C. Huffman"<bhuffman@...ze.net>  wrote:
>
>>    I have searched and found no previous posts on this topic.  Using the
>> 2.6.36-rc2-git3 (and many before that rev), the kernel doesn't see my
>> PCI devices.  They can be seen with dmidecode but do not show up with
>> lspci (and are not mentioned on boot up).
> Is this still happening?
>
> Do you know when it started happening?  Was 2.6.35 OK?  2.6.34?
>
Thanks.

Unfortunately I no longer have this board to help test.  I posted the 
same message on the linux-pci list and we got so far as to determine 
that somehow the kernel is getting the wrong primary / secondary bus 
number.  Using pci=assign-busses worked around it, but even after 
recognizing the cards, they didn't work properly and I had to send the 
board back.  Here's the pertinent excerpt from linux-pci:

On 09/10/2010 02:38 PM, Bjorn Helgaas wrote:
>
>> pci 0000:00:1e.0: PCI bridge to [bus 20-08] (subtractive decode)
> There's something wrong here because the [20-08] bus number range is
> backwards.  Maybe the secondary bus is really 08, but we scan bus 20
> instead?
>
> The "pci=assign-busses" parameter might work around this for now.
> Maybe Windows is smart enough to notice this problem and reprogram
> the bridge to something sensible automatically.
--
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/