public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brian C. Huffman" <bhuffman@graze.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel DP43BF MB - No PCI Devices detected
Date: Mon, 4 Oct 2010 14:39:36 -0400	[thread overview]
Message-ID: <4CAA1F68.4080402@graze.net> (raw)
In-Reply-To: <20100924142924.cf074205.akpm@linux-foundation.org>

  On 09/24/2010 05:29 PM, Andrew Morton wrote:
> On Wed, 25 Aug 2010 17:54:45 -0400
> "Brian C. Huffman"<bhuffman@graze.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.

      reply	other threads:[~2010-10-04 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 21:54 Intel DP43BF MB - No PCI Devices detected Brian C. Huffman
2010-09-24 21:29 ` Andrew Morton
2010-10-04 18:39   ` Brian C. Huffman [this message]

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=4CAA1F68.4080402@graze.net \
    --to=bhuffman@graze.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox