lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080717141313.GA24513@bromo.msbb.uc.edu>
Date:	Thu, 17 Jul 2008 10:13:14 -0400
From:	Jack Howarth <howarth@...mo.msbb.uc.edu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: 2.6.26-rc9-git9 doesn't boot on Macintel

YH,
   I am wondering why, on my MacBook Pro, I see a call to...

PCI: Scanning behind PCI bridge 0000:00:01.0, config 010100, pass 0

immediately after the instance of...

> > PCI: Fixups for bus 0000:00

and your machine goes directly to the...

> PCI: Transparent bridge - 0000:00:01.0

(which 2.6.26 never makes it to on my MacBook Pro)?
Might we be able to disable that additional scan behind the PCI bridge
of the bus?
                  Jack

On Wed, Jul 16, 2008 at 11:48:19PM -0700, Yinghai Lu wrote:
> On Wed, Jul 16, 2008 at 11:18 PM, Jack Howarth
> <howarth@...mo.msbb.uc.edu> wrote:
> > YH,
> >  Using the debug patches and your mmconfig patch as well as the kernel
> > options 'debug initcall_debug apic=verbose pci=routeirq", I see the following
> > messages that don't scroll off screen...
> >
> > PCI: 0000:00:1f.1 reg 10 io port: [ 40d8, 40df]
> > PCI: 0000:00:1f.1 reg 14 io port: [ 40ec, 40ef]
> > PCI: 0000:00:1f.1 reg 18 io port: [ 40d0, 40d7]
> > PCI: 0000:00:1f.1 reg 1c io port: [ 40e8, 40eb]
> > PCI: 0000:00:1f.1 reg 20 io port: [ 40b0, 40bf]
> > pci 0000:00.1f.1: calling pci_fixup_transparent_bridge+0x0/0x2a
> > PCI: Found 0000:00:1f.2 [8086/27c4] 000101 00
> > PCI: 0000:00:1f.2 reg 10 io port: [ 40c8, 40cf]
> > PCI: 0000:00:1f.2 reg 14 io port: [ 40e4, 40e7]
> > PCI: 0000:00:1f.2 reg 18 io port: [ 40c0, 40c7]
> > PCI: 0000:00:1f.2 reg 1c io port: [ 40e0, 40e3]
> > PCI: 0000:00:1f.2 reg 20 io port: [ 40a0, 40af]
> > PCI: 0000:00:1f.2 reg 24 32bit mmio: [d8405000, d84053ff]
> > pci: 0000:00:1f.2 calling pci_fixup_transparent_bridge+0x0/0x2a
> > PCI: Found 0000:00:1f.3 [8086/27da] 000c05 00
> > PCI: 0000:00:1f.3 reg 20 io port: [ efa0, efbf]
> > PCI: 0000:00:1f.3: calling pci_fixup_transparent_bridge+0x0/0x2a
> > PCI: Fixups for bus 0000:00
> > PCI: Scanning behind PCI bridge 0000:00:01.0, config 010100, pass 0
> > PCI: Scanning bus 0000:01
> > PCI: Found 0000:01:00.0 [1002/71c5] 000300 00
> > PCI: 0000:00:01:00.0 reg 10 32bit mmio: [c0000000, cfffffff]
> > PCI: 0000:00:01:00.0 reg 14 io port: [ 3000, 30ff]
> > PCI: 0000:00:01:00.0 reg 18 32bit mmio: [d8300000, d830ffff]
> >
> should get
> PCI: Fixups for bus 0000:01
> PCI: Transparent bridge - 0000:00:01.0
> PCI: bridge 0000:00:01.0 io port: [3000, 3fff]
> PCI: bridge 0000:00:01.0 32bit mmio: ...
> PCI: Bus scan for 0000:01 returning with max=01
> 
> Do you have CONFIG_PCIEASPM in your config?
> 
> YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ