From: Dave Hansen <haveblue@us.ibm.com>
To: Daniel Ritz <daniel.ritz-ml@swissonline.ch>
Cc: Greg KH <greg@kroah.com>, Marcus Better <marcus@better.se>,
Andrew Morton <akpm@osdl.org>,
James Bottomley <James.Bottomley@steeleye.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux scsi <linux-scsi@vger.kernel.org>,
ak@suse.de
Subject: Re: aic7xxx broken in 2.6.18-rc3-mm2
Date: Mon, 14 Aug 2006 09:05:51 -0700 [thread overview]
Message-ID: <1155571551.7574.143.camel@localhost.localdomain> (raw)
In-Reply-To: <200608130002.40223.daniel.ritz-ml@swissonline.ch>
On Sun, 2006-08-13 at 00:02 +0200, Daniel Ritz wrote:
> On Saturday 12 August 2006 20.05, Daniel Ritz wrote:
> > On Saturday 12 August 2006 03.03, Greg KH wrote:
> > > On Fri, Aug 11, 2006 at 05:36:24PM -0700, Andrew Morton wrote:
> > > > On Fri, 11 Aug 2006 17:17:15 -0700
> > > > Dave Hansen <haveblue@us.ibm.com> wrote:
> > > >
> > > > > Well, I have a new culprit of the hour:
> > > > >
> > > > > gregkh-pci-pci-use-pci_bios-as-last-fallback
> > > >
> > > > Thanks, I'll drop it.
> > > >
> > > > > There was a previous patch that messed up a few of my machines and this
> > > > > same driver a few months ago, which accounts for my sense of deja vu:
> > > > >
> > > > > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc6/2.6.16-rc6-mm1/broken-out/gregkh-pci-pci-give-pci-config-access-initialization-a-defined-ordering.patch
> > >
> > > Ugh, this is a mess. Daniel, why does your machine need this patch, yet
> > > as per Dave's comments, it's wrong?
> >
> > it's not my machines. they work fine :) but there where bug reports on linux-pcmcia
> > for this problem...only shows up with kernel >= 2.6.17. see also bug 6801.
> >
> > 2.6.16 shows this:
> > PCI: PCI BIOS revision 2.10 entry at 0xfb9a0, last bus=0
> > PCI: Using configuration type 1
> > while 2.6.17+ shows only
> > PCI: PCI BIOS revision 2.10 entry at 0xfb9a0, last bus=0
> >
> > so accessing the cardbus cards is not possible with PCI BIOS but works
> > just fine with direct access...
> >
> > >
> > > I think it might come down to the fact that the ordering before used to
> > > not always happen in the same order (it depended on config options and
> > > linker luck.) Now it's "fixed" to be the same way all the time.
> > > Daniel, can't you solve this with the proper pci boot option?
> >
> > sure, but the point is: it used to work on those boxes, but broke with 2.6.17
> >
> > ok, i had a look. the problem is not the patch itself. look at arch/i386/pci/legacy.c
> > it's where those messages come from:
> > PCI: Probing PCI hardware
> > PCI: Discovered peer bus 02
> > PCI: Discovered peer bus 05
> >
> > now if pcibios probing never runs pcibios_last_bus is -1 and pcibios_fixup_peer_bridges()
> > exits immediatley, the other busses are never found...but why legacy probing anyway?
> >
> anyway, this alternative patch should help. it should be more like the <= 2.6.16
> behavior.
>
> [ CC'ing Marcus Better as the tester of the original patch. ]
>
> Marcus, could you test this patch instead of the original one and see how your
> cardbus cards behave?
>
> Dave, your SCSI card should work with this as well :)
Sorry, it has the same behavior as without the patch. If it matters,
here is the relevant portion of my .config:
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCIEPORTBUS is not set
-- Dave
next prev parent reply other threads:[~2006-08-14 16:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 22:11 aic7xxx broken in 2.6.18-rc3-mm2 Dave Hansen
2006-08-11 22:27 ` James Bottomley
2006-08-11 22:31 ` Dave Hansen
2006-08-11 22:50 ` James Bottomley
2006-08-11 23:05 ` Doug Maxey
2006-08-11 23:06 ` Dave Hansen
2006-08-11 23:21 ` Andrew Morton
2006-08-12 0:17 ` Dave Hansen
2006-08-12 0:36 ` Andrew Morton
2006-08-12 1:03 ` Greg KH
2006-08-12 18:05 ` Daniel Ritz
2006-08-12 22:02 ` Daniel Ritz
2006-08-14 12:17 ` Marcus Better
2006-08-14 16:05 ` Dave Hansen [this message]
2006-08-14 16:58 ` Daniel Ritz
2006-08-14 17:04 ` Dave Hansen
2006-08-14 17:16 ` Dave Hansen
2006-08-14 18:21 ` Daniel Ritz
2006-08-14 19:56 ` Dave Hansen
2006-08-14 20:19 ` Daniel Ritz
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=1155571551.7574.143.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=daniel.ritz-ml@swissonline.ch \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcus@better.se \
/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