From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pci 0000:01:00.0: BAR 6: no parent found for of device [0xfffe0000-0xffffffff]
Date: Wed, 24 Jun 2009 12:32:41 -0700 [thread overview]
Message-ID: <20090624123241.01ca4fec@jbarnes-g45> (raw)
In-Reply-To: <dd18b0c30906241027u152274b1kd4c854ada4de33dd@mail.gmail.com>
On Wed, 24 Jun 2009 10:27:42 -0700
Justin Mattock <justinmattock@gmail.com> wrote:
> (just pulled the latest git)
> And am seeing this:
>
>
> [ 0.696001] pci 0000:01:00.0: BAR 6: no parent found for of device
> [0xfffe0000-0xffffffff]
> [ 0.696010] pci 0000:02:00.0: BAR 6: no parent found for of device
> [0xfffe0000-0xffffffff]
> [ 0.696069] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
> [ 0.696074] pci 0000:00:01.0: IO window: 0x3000-0x3fff
> [ 0.696081] pci 0000:00:01.0: MEM window: 0x50300000-0x503fffff
> [ 0.696087] pci 0000:00:01.0: PREFETCH window:
> 0x00000040000000-0x00000047ffffff
> [ 0.696096] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
> [ 0.696102] pci 0000:00:1c.0: IO window: 0x2000-0x2fff
> [ 0.696111] pci 0000:00:1c.0: MEM window: 0x50200000-0x502fffff
> [ 0.696118] pci 0000:00:1c.0: PREFETCH window:
> 0x50500000-0x505fffff [ 0.696126] pci 0000:00:1c.1: PCI bridge,
> secondary bus 0000:03 [ 0.696130] pci 0000:00:1c.1: IO window:
> disabled [ 0.696138] pci 0000:00:1c.1: MEM window:
> 0x50100000-0x501fffff [ 0.696145] pci 0000:00:1c.1: PREFETCH
> window: disabled [ 0.696152] pci 0000:00:1c.2: PCI bridge,
> secondary bus 0000:04 [ 0.696158] pci 0000:00:1c.2: IO window:
> 0x1000-0x1fff [ 0.696167] pci 0000:00:1c.2: MEM window:
> 0x4c100000-0x500fffff [ 0.696174] pci 0000:00:1c.2: PREFETCH
> window: 0x00000048000000-0x0000004bffffff
> [ 0.696186] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:0c
> [ 0.696190] pci 0000:00:1e.0: IO window: disabled
> [ 0.696198] pci 0000:00:1e.0: MEM window: 0x4c000000-0x4c0fffff
> [ 0.696205] pci 0000:00:1e.0: PREFETCH window: disabled
> [ 0.696219] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) ->
> IRQ 16 [ 0.696225] pci 0000:00:01.0: setting latency timer to 64
> [ 0.696235] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) ->
> IRQ 17 [ 0.696243] pci 0000:00:1c.0: setting latency timer to 64
> [ 0.696254] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) ->
> IRQ 16 [ 0.696261] pci 0000:00:1c.1: setting latency timer to 64
> [ 0.696273] pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) ->
> IRQ 18 [ 0.696280] pci 0000:00:1c.2: setting latency timer to 64
> [ 0.696437] pci 0000:00:1e.0: power state changed by ACPI to D0
> [ 0.696446] pci 0000:00:1e.0: setting latency timer to 64
>
>
> Is this good or bad?
> (BAR 6: no parent found for of device)
There have been a few changes in this area recently, notably
commit 9e9f46c44e487af0a82eb61b624553e2f7118f5b
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date: Thu Jun 11 10:58:28 2009 -0700
PCI: use ACPI _CRS data by default
and some related to
commit ff54250a0ebab7f90a5f848a0ba63f999830c872
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Apr 18 21:44:24 2009 -0700
Remove 'recurse into child resources' logic from ...
The first you can control with the nocrs boot param, the other ones
will have to be bisected through though...
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-06-24 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 17:27 Justin Mattock
2009-06-24 19:30 ` Rafael J. Wysocki
2009-06-24 19:50 ` Matthew Wilcox
2009-06-24 20:04 ` Jesse Barnes
2009-06-24 20:41 ` Justin Mattock
2009-06-24 19:32 ` Jesse Barnes [this message]
2009-06-24 19:42 ` Justin Mattock
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=20090624123241.01ca4fec@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=justinmattock@gmail.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
all inboxes | Powered by JetHome®