From: Pavel Machek <pavel@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Brian Moyle <bmoyle@mvista.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.2-ac6 hangs on boot w/AMD Elan SC520 dev board
Date: Thu, 1 Mar 2001 12:12:11 +0000 [thread overview]
Message-ID: <20010301121210.B34@(none)> (raw)
In-Reply-To: <200102280312.TAA13404@bia.mvista.com> <E14Y539-0005XE-00@the-village.bc.nu>
In-Reply-To: <E14Y539-0005XE-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Feb 28, 2001 at 11:45:40AM +0000
Hi!
> > bios-e820: 000000000009f400 @ 0000000000000000 (usable)
> > bios-e820: 0000000000000c00 @ 000000000009f400 (reserved)
> > bios-e820: 0000000003f00000 @ 0000000000100000 (usable)
> > bios-e820: 0000000003f00000 @ 0000000000100000 (usable)
> > bios-e820: 0000000000100000 @ 00000000fff00000 (reserved)
> > (at this point, it appears to be in an infinite printk loop <?>)
> >
> > I didn't spend much time looking into the printk loop, but it seems to
> > end up there, even if CONFIG_DEBUG_BUGVERBOSE is not defined, as if the
> > ".byte 0x0f,0x0b" is causing the loop to begin.
> >
> > Any ideas/suggestions/comments?
>
> Having been over the code the problem is indeed the bios reporting overlapping
> /duplicated ranges. That will cause a crash in mm/bootmem when we try and free
> the range twice.
>
> I suspect you need to add some code to take the E820 map and remove any
> overlaps from it, favouring ROM over RAM if the types disagree (for safety),
> and filter them before you register them with the bootmem in
> arch/i386/kernel/setup.c
...plus prining ?@#@&#&$ BIOS reports invalid mem map
seems like good idea, so that bios bugs are fixed.
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2001-03-02 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 3:12 2.4.2-ac6 hangs on boot w/AMD Elan SC520 dev board Brian Moyle
2001-02-28 9:49 ` Alan Cox
2001-02-28 11:45 ` Alan Cox
2001-03-01 8:56 ` Brian Moyle
2001-03-02 1:32 ` Brian Moyle
2001-03-01 12:12 ` Pavel Machek [this message]
2001-04-05 0:36 ` Brian Moyle
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='20010301121210.B34@(none)' \
--to=pavel@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bmoyle@mvista.com \
--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 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.