From: Len Brown <len.brown@intel.com>
To: Michael Geithe <warpy@gmx.de>
Cc: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: __iounmap: bad address c00f0000 (Re: 2.6.10-bk5)
Date: 03 Jan 2005 12:49:43 -0500 [thread overview]
Message-ID: <1104774583.18174.68.camel@d845pe> (raw)
In-Reply-To: <1104773076.18173.64.camel@d845pe>
On Mon, 2005-01-03 at 12:24, Len Brown wrote:
> On Sun, 2005-01-02 at 19:14, Michael Geithe wrote:
>
> > DMI 2.3 present.
> > __iounmap: bad address c00f0000
> > ACPI: RSDP (v000 AMI ) @ 0x000fa380
>
> Not and ACPI issue:-)
>
> Looks like the warning is provoked by Al Viro's update to dmi_iterate().
> Perhaps there is a conflict between dmi_table()'s bt_iounmap(),
> and dmi_iterate()'s new iounmap() on the same address?
>
> -Len
>
Try this.
Suggested-by: Al Viro
Signed-off-by: Len Brown <len.brown@intel.com>
===== arch/i386/kernel/dmi_scan.c 1.74 vs edited =====
--- 1.74/arch/i386/kernel/dmi_scan.c 2004-12-28 14:07:48 -05:00
+++ edited/arch/i386/kernel/dmi_scan.c 2005-01-03 12:46:33 -05:00
@@ -126,12 +126,12 @@
dmi_printk((KERN_INFO "DMI table at 0x%08X.\n",
base));
if(dmi_table(base,len, num, decode)==0) {
- iounmap(p);
+ /* too early to call iounmap(p); */
return 0;
}
}
}
- iounmap(p);
+ /* too early to call iounmap(p); */
return -1;
}
next prev parent reply other threads:[~2005-01-03 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 0:14 2.6.10-bk5 Michael Geithe
2005-01-03 17:24 ` __iounmap: bad address c00f0000 (Re: 2.6.10-bk5) Len Brown
2005-01-03 17:49 ` Al Viro
2005-01-03 17:49 ` Len Brown [this message]
2005-01-03 18:02 ` Al Viro
2005-01-03 18:29 ` Michael Geithe
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=1104774583.18174.68.camel@d845pe \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=warpy@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox