From: ernte23@gmx.de
To: Rik van Riel <riel@conectiva.com.br>
Cc: Roger Larsson <roger.larsson@norran.net>, linux-mm@kvack.org
Subject: Re: Fwd: kernel BUG at page_alloc.c:75! / exit.c
Date: Tue, 10 Apr 2001 14:48:28 +0200 [thread overview]
Message-ID: <3AD3011C.E5F2674C@gmx.de> (raw)
In-Reply-To: Pine.LNX.4.21.0104041915070.25572-100000@imladris.rielhome.conectiva
Rik van Riel wrote:
>
> On Wed, 4 Apr 2001, Roger Larsson wrote:
>
> > I'm running the 2.4.3 kernel and my system always (!) crashes when I
> > try to generate the "Linux kernel poster" from lgp.linuxcare.com.au.
> > After working for one hour, the kernel printed this message:
>
> There are some known bugs in the 2.4 memory management.
> Does 2.4.3-ac<latest> fix this ?
>
> (note: 2.4.3-ac<latest> isn't stable/safe either, but
> people are working on it and it would be cool to know
> if at least this bug has been fixed)
I tried 2.4.4-pre1 and it showed up again (when there was high disk IO):
this was in the syslog:
kernel BUG at page_alloc.c:75!
invalid operand: 0000
CPU: 0
EIP: 0010:[__free_pages_ok+62/784]
EFLAGS: 00010296
eax: 0000001f ebx: c1410d6c ecx: 00000000 edx: 00000006
esi: c1410d6c edi: c0203518 ebp: 00000000 esp: c1477f78
ds: 0018 es: 0018 ss: 0018
on the screen there was something like:
panic ... in interrupt handler, not syncing ...
I hope this helps.
Grussle, Felix
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-04-10 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 19:36 Fwd: kernel BUG at page_alloc.c:75! / exit.c Roger Larsson
2001-04-04 22:16 ` Rik van Riel
2001-04-10 12:48 ` ernte23 [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 13:22 ernte23
2001-04-17 12:39 ` Stephen C. Tweedie
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=3AD3011C.E5F2674C@gmx.de \
--to=ernte23@gmx.de \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=roger.larsson@norran.net \
/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.