From: William Lee Irwin III <wli@holomorphy.com>
To: Greg KH <greg@kroah.com>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
linux-kernel@vger.kernel.org, colpatch@us.ibm.com
Subject: Re: [BUG] 2.5.33 PCI and/or starfire.c broken
Date: Tue, 3 Sep 2002 22:12:00 -0700 [thread overview]
Message-ID: <20020904051200.GX888@holomorphy.com> (raw)
In-Reply-To: <20020904050401.GA4019@kroah.com>
On Tue, Sep 03, 2002 at 09:49:58PM -0700, Martin J. Bligh wrote:
>> It's confused by having a PCI-PCI bridge on a quad other than 0,
>> where the global and local PCI bus numbers don't line up. Rip
>> the card out, or get the horrible kludge I did for 2.4, and use
>> that.
On Tue, Sep 03, 2002 at 10:04:01PM -0700, Greg KH wrote:
> Might I suggest you port that "kludge" to the new 2.5 pci code, as the
> whole goal of those large PCI changes was due to some NUMA changes that
> you and Matt wanted to get into the main kernel.
> Remember, you have your own file to play with now, so put all the
> brain-damaged NUMA crap into it :)
It's a wee bit less brain-damaged than crackly sound cards with only 24
out of 32 address lines wired. At any rate, the issue is in all
likelihood that that support file is being circumvented. It's obviously
getting wrong information when it asks to read from a given bus as
there are no PCI devices off of node 0 (as this hasn't worked in a long
time), so perhaps a disassembly or other fishing around will reveal
whose pci config space accessors are actually being called here.
Cheers,
Bill
next prev parent reply other threads:[~2002-09-04 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 3:56 [BUG] 2.5.33 PCI and/or starfire.c broken William Lee Irwin III
2002-09-04 4:49 ` Martin J. Bligh
2002-09-04 5:04 ` Greg KH
2002-09-04 5:10 ` Martin J. Bligh
2002-09-04 5:12 ` William Lee Irwin III [this message]
2002-09-04 5:37 ` Martin J. Bligh
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=20020904051200.GX888@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=colpatch@us.ibm.com \
--cc=greg@kroah.com \
--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