From: Lorenzo Allegrucci <l_allegrucci@yahoo.it>
To: Jens Axboe <axboe@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-mm1 oops
Date: Sun, 24 Oct 2004 16:20:50 +0200 [thread overview]
Message-ID: <200410241620.50438.l_allegrucci@yahoo.it> (raw)
In-Reply-To: <20041024123016.GA31870@suse.de>
On Sunday 24 October 2004 14:30, Jens Axboe wrote:
> On Sat, Oct 23 2004, Lorenzo Allegrucci wrote:
> >
> > 100% reproducible with elevator=cfq
>
> but not with the other io schedulers?
No, now I can reproduce it with the anticipatory scheduler too.
> > Unable to handle kernel NULL pointer dereference at virtual address 00000000
> > printing eip:
> > c013f2c7
> > *pde = 00000000
> > Oops: 0000 [#1]
> > PREEMPT
> > Modules linked in: ipv6 dm_mod emu10k1 sound soundcore ac97_codec unix
> > CPU: 0
> > EIP: 0060:[put_page+7/144] Not tainted VLI
> > EFLAGS: 00010282 (2.6.9-mm1)
> > EIP is at put_page+0x7/0x90
> > eax: 00000000 ebx: df047400 ecx: 00000000 edx: 00000000
> > esi: 00000000 edi: 00000000 ebp: df047400 esp: cadd0c80
> > ds: 007b es: 007b ss: 0068
> > Process diotest4 (pid: 4498, threadinfo=cadd0000 task=de712a40)
> > Stack: df047400 c0178d50 00000000 00000000 c0179c91 df047400 00000001 c01b391b
> > c86b6b00 cb0c9b80 cadd0d1c cb0c9c38 c019d31e cee0b0b0 00000000 00000000
> > 00003000 00000000 df047400 00000000 08051000 0000000c c017a182 00000001
> > Call Trace:
> > [dio_cleanup+48/64] dio_cleanup+0x30/0x40
> > [direct_io_worker+817/1568] direct_io_worker+0x331/0x620
> > [journal_put_journal_head+59/192] journal_put_journal_head+0x3b/0xc0
> > [ext3_do_update_inode+366/944] ext3_do_update_inode+0x16e/0x3b0
> > [__blockdev_direct_IO+514/752] __blockdev_direct_IO+0x202/0x2f0
> > [ext3_direct_io_get_blocks+0/240] ext3_direct_io_get_blocks+0x0/0xf0
> > [ext3_direct_IO+201/576] ext3_direct_IO+0xc9/0x240
> > [ext3_direct_io_get_blocks+0/240] ext3_direct_io_get_blocks+0x0/0xf0
> > [generic_file_direct_IO+121/160] generic_file_direct_IO+0x79/0xa0
> > [generic_file_direct_write+134/416] generic_file_direct_write+0x86/0x1a0
> > [generic_file_aio_write_nolock+689/1200] generic_file_aio_write_nolock+0x2b1/0x4b0
> > [generic_file_aio_write+131/256] generic_file_aio_write+0x83/0x100
> > [ext3_file_write+68/224] ext3_file_write+0x44/0xe0
> > [do_sync_write+190/240] do_sync_write+0xbe/0xf0
> > [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60
> > [dnotify_parent+162/224] dnotify_parent+0xa2/0xe0
> > [do_sync_write+0/240] do_sync_write+0x0/0xf0
> > [vfs_write+184/304] vfs_write+0xb8/0x130
> > [sys_write+81/128] sys_write+0x51/0x80
> > [syscall_call+7/11] syscall_call+0x7/0xb
>
> Please provide a test case, or at least a description of the problem.
I can 100% reproduce it running "runalltests.sh -x 100" of
ltp-full-20040804.
The test cases seem to be diotest1 and diotest4 because they always
appear in the oops, but I couldn't reproduce it running diotest1 and
diotest4 alone.
--
I route therefore you are
next prev parent reply other threads:[~2004-10-24 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 15:31 Lorenzo Allegrucci
2004-10-24 12:30 ` Jens Axboe
2004-10-24 14:20 ` Lorenzo Allegrucci [this message]
2004-10-24 20:02 ` Lorenzo Allegrucci
2004-10-25 8:45 ` Lorenzo Allegrucci
2004-10-25 8:55 ` Jens Axboe
2004-10-25 10:05 ` Jens Axboe
2004-10-25 10:27 ` Jens Axboe
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=200410241620.50438.l_allegrucci@yahoo.it \
--to=l_allegrucci@yahoo.it \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--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®