lkml.org 
[lkml]   [2002]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [BUG] 2.5.33 PCI and/or starfire.c broken
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.049 / U:3.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site