From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, neilb@cse.unsw.edu.au
Subject: Re: 2.5.70-mm5 new oops that wasn't in 2.5.70-mm4
Date: Thu, 05 Jun 2003 13:57:31 +0200 [thread overview]
Message-ID: <3EDF302B.70601@aitel.hist.no> (raw)
In-Reply-To: <20030605021231.2b3ebc59.akpm@digeo.com>
mm5 has a raid-1-related boot oops that wasn't in mm4.
Unlike my earlier reports this was a single oops, not
a string of them.
This is an UP machine with / on raid-1, no raid-0.
The kernel is monolithic and compiled with gcc 3.3
The last boot message before the crash was
md: ... autorun DONE.
The next one is normally
VFS: Mounted root (ext2 filesystem) readonly.
So I guess this failed.
Here is the oops, written down form a framebuffer using
the 4x6 font (urgh...)
unable to handle kernel paging request at 6b6b6b97 (poison?)
PREEMP DEBUG_PAGEALLOC not tainted
EIP: put_all_bios
process swapper
trace:
raid_end_bio_io
raid1_end_request
kernel_map_pages
mempool_free
bio_endio
_end_that_request_first
ide_end_request
ide_dma_intr
ide_intr
handle_IRQ_event
do_IRQ
default_idle
common_interrupt
default_idle
default_idle
cpu_idle
rest_init
start_kernel
unknown_bootoption
This is 2.5.70-mm5 without other patches.
Helge Hafting
--
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-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-06-05 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 9:12 2.5.70-mm5 Andrew Morton
2003-06-05 11:57 ` Helge Hafting [this message]
2003-06-05 12:35 ` 2.5.70-mm5 new oops that wasn't in 2.5.70-mm4 Paul E. Erkkila
2003-06-05 14:05 ` 2.5.70-mm5 Pavel Machek
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=3EDF302B.70601@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=neilb@cse.unsw.edu.au \
/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