From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Pavel Troller <patrol@sinus.cz>
Cc: linux-acpi@vger.kernel.org
Subject: Re: what is MCFG area ?
Date: Wed, 07 Jun 2006 14:33:12 +0100 [thread overview]
Message-ID: <1149687192.3011.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20060607041525.GA10931@tangens.sinus.cz>
On Wed, 2006-06-07 at 06:15 +0200, Pavel Troller wrote:
> > On my buggy computer i get
> > cat dmesg09 | grep "MM\|MCFG"
> > ACPI: MCFG (v001 A M I OEMMCFG 0x05000602 MSFT 0x00000097) @ 0x000000003ffb0410
> > PCI: BIOS Bug: MCFG area is not E820-reserved
> > PCI: Not using MMCONFIG.
> > PCI-DMA: Disabling IOMMU.
>
> I'm getting exactly the same messages, just the numbers in the MCFG line are
> different:
> root@arcus:~# dmesg | grep "MM\|MCFG"
> ACPI: MCFG (v001 A M I OEMMCFG 0x11000524 MSFT 0x00000097) @ 0x000000003f7d03f0
> PCI: BIOS Bug: MCFG area is not E820-reserved
> PCI: Not using MMCONFIG.
> PCI-DMA: Disabling IOMMU.
>
> It's on a MSI motherboard with Intel 945 chipset (MS-7210). The machine
> otherwise works very well.
> The "Disabling IOMMU" message I'm getting also on another, Nvidia NF4/Opteron
> based board, without this MCFG bug. I think it's unrelated and because Linux
> properly detected the BIOS bug and probably fixed it, I think the MCFG message
> is harmless.
> With regards, Pavel Troller
yes, IOMMU is a different thing some AGPs have it. But I don't what is
too.
Sérgio M. B.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2006-06-07 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 23:45 what is MCFG area ? Sergio Monteiro Basto
2006-06-07 4:15 ` Pavel Troller
2006-06-07 13:33 ` Sergio Monteiro Basto [this message]
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=1149687192.3011.3.camel@localhost.localdomain \
--to=sergio@sergiomb.no-ip.org \
--cc=linux-acpi@vger.kernel.org \
--cc=patrol@sinus.cz \
/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