From: Robert Hancock <hancockr@shaw.ca>
To: Diego Calleja <diegocg@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: BUG?: "Cannot map mmconfig aperture"
Date: Wed, 20 Feb 2008 17:47:06 -0600 [thread overview]
Message-ID: <47BCBBFA.9030004@shaw.ca> (raw)
In-Reply-To: <fa.ta6yFP+Jk2cm3xbIaPPD8L82kEs@ifi.uio.no>
Diego Calleja wrote:
> I get the following new message in my dmesg:
>
> [ 0.155476] ACPI: bus type pci registered
> [ 0.155567] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory Controller Hub with MMCONFIG support.
> [ 0.161149] PCI: Cannot map mmconfig aperture for segment 0
> [ 0.161181] PCI: Using configuration type 1
> [ 0.165980] ACPI: EC: Look up EC in DSDT
>
> when previously i'd have:
>
> [ 0.156577] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory Controller Hub with MMCONFIG support.
> [ 0.166403] PCI: Using MMCONFIG at e0000000 - efffffff
> [ 0.166407] PCI: Using configuration type 1
> [ 0.171548] ACPI: EC: Look up EC in DSDT
>
>
> No idea if this is a regression or not, or what it means, the system works well.
> git-bisect says the problem cames from:
>
> commit c31c7d4844ea4817692ae16bf70f9c96c05a50eb
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Mon Feb 18 20:54:14 2008 +0100
>
> x86: CPA, fix alias checks
Yeah, sounds like a regression.
next parent reply other threads:[~2008-02-20 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ta6yFP+Jk2cm3xbIaPPD8L82kEs@ifi.uio.no>
2008-02-20 23:47 ` Robert Hancock [this message]
2008-02-20 21:31 BUG?: "Cannot map mmconfig aperture" Diego Calleja
2008-02-21 7:53 ` Thomas Gleixner
2008-02-21 15:41 ` Diego Calleja
2008-02-21 20:26 ` Thomas Gleixner
2008-02-22 20:22 ` Diego Calleja
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=47BCBBFA.9030004@shaw.ca \
--to=hancockr@shaw.ca \
--cc=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.