From: Dave Hansen <haveblue@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux scsi <linux-scsi@vger.kernel.org>
Subject: Re: aic7xxx broken in 2.6.18-rc3-mm2
Date: Fri, 11 Aug 2006 17:17:15 -0700 [thread overview]
Message-ID: <1155341835.7574.76.camel@localhost.localdomain> (raw)
In-Reply-To: <20060811162124.66895682.akpm@osdl.org>
Well, I have a new culprit of the hour:
gregkh-pci-pci-use-pci_bios-as-last-fallback
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
There was an off-list thread called
"PCI device issue in 2.6.16-rc3-mm1 through 2.6.16-rc6-mm1"
Anyway, here's the information from the syslog at boot in a working
system (without the patch applied):
PCI: PCI BIOS revision 2.10 entry at 0xfd32c, last bus=8
Setting up standard PCI resources
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Discovered peer bus 02
PCI: Firmware left 0000:02:05.0 e100 interrupts enabled, disabling
PCI: Discovered peer bus 05
PCI->APIC IRQ transform: 0000:00:05.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:0f.2[A] -> IRQ 19
PCI->APIC IRQ transform: 0000:02:01.0[A] -> IRQ 17
PCI->APIC IRQ transform: 0000:02:01.1[B] -> IRQ 18
PCI->APIC IRQ transform: 0000:02:05.0[A] -> IRQ 24
PCI->APIC IRQ transform: 0000:05:02.0[A] -> IRQ 21
PCI->APIC IRQ transform: 0000:05:02.1[B] -> IRQ 26
PCI->APIC IRQ transform: 0000:06:04.0[A] -> IRQ 22
PCI->APIC IRQ transform: 0000:06:05.0[A] -> IRQ 27
PCI->APIC IRQ transform: 0000:06:06.0[A] -> IRQ 28
PCI->APIC IRQ transform: 0000:06:07.0[A] -> IRQ 29
PCI: Bridge: 0000:05:03.0
IO window: 7000-7fff
MEM window: eb000000-ec1fffff
PREFETCH window: ea300000-ea3fffff
And the same thing in a system where it can't find my SCSI card (with
the patch applied):
PCI: Using configuration type 1
Setting up standard PCI resources
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI->APIC IRQ transform: 0000:00:05.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:0f.2[A] -> IRQ 19
-- Dave
next prev parent reply other threads:[~2006-08-12 0:17 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 [this message]
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
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=1155341835.7574.76.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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