From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: akpm@osdl.org, andrea@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.4.25 SMP - BUG at page_alloc.c:105
Date: Wed, 24 Mar 2004 17:58:11 -0300 [thread overview]
Message-ID: <20040324205811.GB6572@logos.cnet> (raw)
The backtrace is odd to me.
set_page_dirty() does not call __free_pages_ok() directly or indirectly.
How can it be?
---
Hi,
I found this in the logs of a Dual Athlon MP machine (Tyan board)
running 2.4.25-SMP:
kernel BUG at page_alloc.c:105!
invalid operand: 0000
CPU: 0
EIP: 0010:[__free_pages_ok+80/704] Not tainted
EFLAGS: 00010286
eax: c0333674 ebx: c1b2d720 ecx: 00000000 edx: f22f7a84
esi: 00000001 edi: 00000000 ebp: 00000001 esp: f6901e3c
ds: 0018 es: 0018 ss: 0018
Process svscan (pid: 1348, stackpage=f6901000)
Stack: c033364c f741cbc0 f22f7a84 00000001 0804c000 c0133ea6 f22f79c0 00000004
00000001 00000001 0804c000 00000001 c01308fa c1b2d720 f68e3080 0804b000
00001000 0844b000 c03ac4e0 00000001 0804c000 f68e3084 f42baa40 f7212440
Call Trace: [set_page_dirty+166/176] [zap_page_range+330/400] [exit_mmap+221/352] \
[mmput+88/176] [do_exit+259/800] [sig_exit+195/208] [dequeue_signal+95/192] \
[do_signal+448/694] [schedule_timeout+94/176] [process_timeout+0/96] \
[sys_nanosleep+232/448] [do_page_fault+0/1347] [signal_return+20/24]
Other than this BUG (that took down the machine hard, I was lucky to log
across the network), there appear to be no relevant logs shortly before
this crash.
next reply other threads:[~2004-03-24 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 20:58 Marcelo Tosatti [this message]
2004-03-24 20:28 ` 2.4.25 SMP - BUG at page_alloc.c:105 Andrew Morton
2004-03-24 21:12 ` Matthias Andree
2004-03-24 21:51 ` Marcelo Tosatti
2004-03-24 21:36 ` Matthias Andree
2004-03-25 0:22 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-03-22 14:49 Matthias Andree
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=20040324205811.GB6572@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@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 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.