From: Stelian Pop <stelian@popies.net>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt_Domsch@dell.com, hostmaster@ed-soft.at,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH 1/1] EFI iounpam fix for acpi_os_unmap_memory
Date: Wed, 22 Feb 2006 07:50:22 +0100 [thread overview]
Message-ID: <1140591022.4813.7.camel@deep-space-9.dsnet> (raw)
In-Reply-To: <200602212209.07586.ak@suse.de>
Le mardi 21 février 2006 à 22:09 +0100, Andi Kleen a écrit :
> On Tuesday 21 February 2006 21:59, Andrew Morton wrote:
> > OK, thanks. I don't think we actually know who is trying to unmap some
> > memory which acpi didn't map.
> >
> > Edgar, can you please describe the bug which you're trying to fix?
>
> I think the bug is clear - the logic in acpi_os_unmap_memory needs to match
> what acpi_os_map_memory() does for EFI. In particular this means not calling
> iounmap.
>
> He probably has a EFI system where this caused troubles.
This EFI system is the new Intel Core Duo based Apple iMac (Edgar
described the process of booting Linux on this pretty box at
http://www.mactel-linux.org/)
In particular, the iounmap problem is visible in the logs at
http://www.mactel-linux.org/wiki/Dmesg
Stelian.
--
Stelian Pop <stelian@popies.net>
-
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-02-22 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 23:36 [PATCH 1/1] EFI iounpam fix for acpi_os_unmap_memory Edgar Hucek
2006-02-21 6:02 ` Andrew Morton
2006-02-21 14:15 ` Andi Kleen
2006-02-21 20:59 ` Andrew Morton
2006-02-21 21:09 ` Andi Kleen
2006-02-22 6:50 ` Stelian Pop [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=1140591022.4813.7.camel@deep-space-9.dsnet \
--to=stelian@popies.net \
--cc=Matt_Domsch@dell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=hostmaster@ed-soft.at \
--cc=linux-acpi@vger.kernel.org \
--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