public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Joshua Kwan <joshk@triplehelix.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [?] PCI BIOS masks some IDs to prevent OS detection?
Date: Mon, 16 Jan 2006 10:53:53 -0500	[thread overview]
Message-ID: <20060116155353.GC18972@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20060113144529.56fa3166@darjeeling.triplehelix.org>

On Fri, Jan 13, 2006 at 02:45:29PM -0800, Joshua Kwan wrote:
> I'd like to tap some of the Linux-PCI gurus about something weird I've
> been helping a friend with...
> 
> He recently installed a PCI RAID card, and ever since, his Ethernet
> card stopped working. Further investigation revealed that his
> Realtek 8139 (10ec:8139) card had become 10ec:0139, and his 3Com Cyclone
> card had become 10b7:1055 from 10b7:9055.
> 
> Did the PCI bus decide to mask those PCI IDs to prevent some sort of
> resource conflict that would ensue from loading an appropriate driver
> for these devices?

Maybe the raid card has a pin shorted to ground, so all reads of that
bit read as 0.  That would explain why all the cards lost the same bit.
It appears to be the highest bit on the bus that is stuck low.

I see this fairly frequently on our own mainboards due to a problem with
the soldering of a surface mount pci bridge chip on the bottom of
the board.

So check if the problem goes away if the raid card is removed, and you
could check the raid card in another machine too.  Either it isn't
seated properly, or it is broken, or the pci slot is defective perhaps.

Len Sorensen

  parent reply	other threads:[~2006-01-16 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 22:45 [?] PCI BIOS masks some IDs to prevent OS detection? Joshua Kwan
2006-01-14  0:31 ` Alan Cox
2006-01-14 19:12 ` Onur Küçük
2006-01-16 15:53 ` Lennart Sorensen [this message]
2006-01-16 16:15   ` Kyle Moffett

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=20060116155353.GC18972@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=joshk@triplehelix.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