From: "Luck, Tony" <tony.luck@intel.com>
To: "Bjorn Helgaas" <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: lots of "bridge window ... (disabled)" messages
Date: Mon, 29 Mar 2010 09:57:16 -0700 [thread overview]
Message-ID: <4bb0dbec213331313b@agluck-desktop.sc.intel.com> (raw)
Hi Bjorn,
I just booted Linus latest git tree on my Tukwila system. I'm
seeing a lot of bridge windows marked as disabled. Here's the
start of a diff of dmesg output comparing a kernel from last
week to today's kernel (git 01e7770 vs. b72c409):
< pci 0000:00:01.0: bridge window [mem 0xfff00000 - 000fffff pref] reg reading
---
> pci 0000:00:01.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
222,224c222,224
< pci 0000:00:03.0: bridge window [io f000 - 0000] reg reading
< pci 0000:00:03.0: bridge window [mem 0xfff00000 - 0x000fffff] reg reading
< pci 0000:00:03.0: bridge window [mem 0xfff00000 - 000fffff pref] reg reading
---
> pci 0000:00:03.0: bridge window [io 0xf000-0x0000] (disabled)
> pci 0000:00:03.0: bridge window [mem 0xfff00000-0x000fffff] (disabled)
> pci 0000:00:03.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
233c233
< pci 0000:00:05.0: bridge window [mem 0xfff00000 - 000fffff pref] reg reading
---
> pci 0000:00:05.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
... many more such diffs.
This is the same system that you helped out with a couple of months
ago that had some issues in _CRS tables with ranges marked as
"consumer". The BIOS team fixed the one range that was needed
to allow access to my EHCI - but they didn't touch anything else.
Are these new checks related to the same sort of issues in _CRS?
Or is this some other stuff? I don't appear to have lost access
to any devices in today's kernel.
-Tony
next reply other threads:[~2010-03-29 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 16:57 Luck, Tony [this message]
2010-03-29 22:01 ` lots of "bridge window ... (disabled)" messages Bjorn Helgaas
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=4bb0dbec213331313b@agluck-desktop.sc.intel.com \
--to=tony.luck@intel.com \
--cc=bjorn.helgaas@hp.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