From: Martin Dalecki <dalecki@evision-ventures.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: 2.5.23+ bootflag.c triggers __iounmap: bad address
Date: Fri, 21 Jun 2002 14:23:16 +0200 [thread overview]
Message-ID: <3D131AB4.8090906@evision-ventures.com> (raw)
In-Reply-To: 200206211156.NAA13885@harpo.it.uu.se
Użytkownik Mikael Pettersson napisał:
> When booting 2.5.23/.24, my test boxes generate the following:
>
> (an ASUS P4T-E which has SBF)
> __iounmap: bad address d0802100
> SBF: Simple Boot Flag extension found and enabled.
> __iounmap: bad address d0805040
> __iounmap: bad address d0808080
> SBF: Setting boot flags 0x1
>
> (an old Intel AL440LX which doesn't have SBF)
> __iounmap: bad address c4800009
> __iounmap: bad address c4804b8c
> __iounmap: bad address c4802009
>
> These warnings/errors are new since 2.5.23, which makes me
> suspect something's wrong in the 2.5.23 iounmap changes.
Just to complete the pattern: ASUS S8600 gives me the following:
PCI: Found IRQ 5 for device 00:0c.1
PCI: Sharing IRQ 5 with 00:00.2
PCI: Sharing IRQ 5 with 00:06.0
__iounmap: bad address cc800cb7
__iounmap: bad address cc804b64
SBF: Simple Boot Flag extension found and enabled.
__iounmap: bad address cc807bd8
__iounmap: bad address cc802cb7
SBF: Setting boot flags 0x1
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
With the mapping beein:
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e5800 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000bff0000 (usable)
BIOS-e820: 000000000bff0000 - 000000000bfffc00 (ACPI data)
BIOS-e820: 000000000bfffc00 - 000000000c000000 (ACPI NVS)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
191MB LOWMEM available.
On node 0 totalpages: 49136
zone(0): 4096 pages.
zone(1): 45040 pages.
zone(2): 0 pages.
next prev parent reply other threads:[~2002-06-21 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 11:56 2.5.23+ bootflag.c triggers __iounmap: bad address Mikael Pettersson
2002-06-21 12:23 ` Martin Dalecki [this message]
2002-06-21 12:43 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2002-06-21 16:44 Mikael Pettersson
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=3D131AB4.8090906@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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.