public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Michael Geithe <warpy@gmx.de>,
	Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: __iounmap: bad address c00f0000 (Re: 2.6.10-bk5)
Date: 03 Jan 2005 12:24:36 -0500	[thread overview]
Message-ID: <1104773076.18173.64.camel@d845pe> (raw)
In-Reply-To: <200501030114.55399.warpy@gmx.de>

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



  reply	other threads:[~2005-01-03 17:26 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 ` Len Brown [this message]
2005-01-03 17:49   ` __iounmap: bad address c00f0000 (Re: 2.6.10-bk5) Al Viro
2005-01-03 17:49   ` Len Brown
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=1104773076.18173.64.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