From: Andrew Morton <akpm@osdl.org>
To: Bart Janssens <bart.janssens@polytechnic.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS: ext3 on 2.6.3 with high IO
Date: Mon, 23 Feb 2004 15:02:57 -0800 [thread overview]
Message-ID: <20040223150257.18e8d4d5.akpm@osdl.org> (raw)
In-Reply-To: <200402231202.17307.bart.janssens@polytechnic.be>
Bart Janssens <bart.janssens@polytechnic.be> wrote:
>
> Hello all
>
> 1. I am getting a kernel oops when having high IO on an ext3 partition in
> 2.6.3.
I doubt if this is related to high-IO.
> Unable to handle kernel NULL pointer dereference at virtual address 00000037
> c0223467
> *pde = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c0223467>] Tainted: P
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010212
> eax: ffffffff ebx: 00000001 ecx: f7bf1900 edx: ce02a680
> esi: 00000008 edi: ce02a680 ebp: 00000001 esp: f7d39d50
> ds: 007b es: 007b ss: 0068
> Stack: f7d39d50 f7d39d50 d9914000 f7e03978 c1bb4610 ce02a680 00000000 00000000
> 00000010 c0156dab f7fee8c0 00000010 00000000 cfe7c270 00000001 00000001
> 00000002 00000029 00000001 c022361d ce02a680 cfe7c270 c01566c3 00000001
> Call Trace:
> [<c0156dab>] bio_alloc+0xcb/0x1a0
> [<c022361d>] submit_bio+0x3d/0x70
> [<c01566c3>] ll_rw_block+0x63/0x90
> [<c01990d7>] journal_commit_transaction+0x1057/0x12c0
> [<c0117a60>] recalc_task_prio+0x90/0x1a0
> [<c019b6aa>] kjournald+0xca/0x260
> [<c011a2c0>] autoremove_wake_function+0x0/0x50
> [<c011a2c0>] autoremove_wake_function+0x0/0x50
> [<c010907e>] ret_from_fork+0x6/0x14
> [<c019b5c0>] commit_timeout+0x0/0x10
> [<c019b5e0>] kjournald+0x0/0x260
> [<c0106fc9>] kernel_thread_helper+0x5/0xc
> Code: 8b 50 38 8b 40 34 0f ac d0 09 85 c0 89 c3 0f 84 8b 00 00 00
>
>
> >>EIP; c0223467 <generic_make_request+17/190> <=====
>
It looks like bio->bi_bdev->bd_inode is 0xffffffff in generic_make_request().
(Please enable CONFIG_KALLSYMS: it gives better traces and you don't need
ksymoops).
The fact that this happens when you're doing something which thousands
of other people do makes me wonder. Is the oops always the same? Are
you sure the hardware is good?
next prev parent reply other threads:[~2004-02-23 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 11:02 Bart Janssens
2004-02-23 23:02 ` Andrew Morton [this message]
2004-02-24 16:13 ` Bart Janssens
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=20040223150257.18e8d4d5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bart.janssens@polytechnic.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®