From: Warren Togami <wtogami@redhat.com>
To: Jens Axboe <axboe@suse.de>
Cc: Markus Lidel <Markus.Lidel@shadowconnect.com>,
Arjan van de Ven <arjanv@redhat.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Cox <alan@redhat.com>
Subject: Re: [PATCH] i2o_block Fix, possible CFQ elevator problem?
Date: Tue, 20 Apr 2004 01:29:11 -1000 [thread overview]
Message-ID: <40850987.1080603@redhat.com> (raw)
In-Reply-To: <20040420105622.GK25806@suse.de>
Jens Axboe wrote:
>>>
>>>Repeat the tests that made it crash. The last patch I sent should work
>>>for you, at least until the real issue is found.
>>>
>>
>>Tested your patch, it indeed does seem to keep the system stable. If I
>>am understanding it right, the patch disables merging in the case where
>>it would have caused a BUG condition? (Less efficiency.)
>
>
Bad news... much later during the test the system locked up. During
this test we did not use "sync" but just let all four bonnie++'s run.
http://togami.com/~warren/archive/2004/i2o_cfq_quad_bonnie3.txt
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at cfq_iosched:404
invalid operand: 0000 [1] SMP
CPU 0
Pid: 0, comm: swapper Not tainted 2.6.5-1.326changeme
RIP: 0010:[<ffffffff80234f74>] <ffffffff80234f74>{cfq_next_request+35}
RSP: 0018:ffffffff804a9048 EFLAGS: 00010046
RAX: 000001007f2c6000 RBX: 000001004483b340 RCX: 0000000000000000
RDX: 000001007f2ca600 RSI: 0000000000180000 RDI: 000001007f2c6000
RBP: 000001007f2c6000 R08: 0000010037ffa568 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000001000 R12: 000001007f2c6000
R13: 000001007f2c6000 R14: ffffffff804adf08 R15: 0000000000000000
FS: 0000002a9555f360(0000) GS:ffffffff804a4e80(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000856348 CR3: 0000000000101000 CR4: 00000000000006e0
Process swapper (pid: 0, stackpage=ffffffff803cf5c0)
Stack: ffffffffa003a880 00000100348b2300 ffffffffa003a880 ffffffff8022b444
00000100348b2300 ffffffffa003a880 000000000001ac00 ffffffffa0036b82
ffffffff803f40a0 00000100629a5e80
Call Trace:<IRQ> <ffffffff8022b444>{elv_next_request+238}
<ffffffffa0036b82>{:i2o_block:i2ob_request+233}
<ffffffffa003670e>{:i2o_block:i2o_block_reply+1162}
<ffffffff8013e13a>{__mod_timer+807}
<ffffffff801310b5>{load_balance+1046}
<ffffffff8013e7f9>{update_wall_time+12}
<ffffffffa002908a>{:i2o_core:i2o_run_queue+124}
<ffffffffa002b60e>{:i2o_core:i2o_pci_interrupt+9}
<ffffffff80113d85>{handle_IRQ_event+44}
<ffffffff801140b8>{do_IRQ+285} <ffffffff8013a894>{__do_softirq+76}
<ffffffff8010f590>{default_idle+0}
<ffffffff8011185f>{ret_from_intr+0}
<EOI> <ffffffff8010f590>{default_idle+0}
<ffffffff8010f5b4>{default_idle+36}
<ffffffff8010f627>{cpu_idle+24} <ffffffff804af7ea>{start_kernel+512}
<ffffffff804af17c>{x86_64_start_kernel+144}
Code: 0f 0b 78 3a 32 80 ff ff ff ff 94 01 f6 43 10 10 48 8b 73 68
RIP <ffffffff80234f74>{cfq_next_request+35} RSP <ffffffff804a9048>
<0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
NMI Watchdog detected LOCKUP on CPU1, registers
CPU 1
Pid: 1525, comm: bonnie++ Not tainted 2.6.5-1.326changeme
RIP: 0010:[<ffffffff8022f332>] <ffffffff8022f332>{.text.lock.ll_rw_blk+95}
RSP: 0018:000001005b553808 EFLAGS: 00000086
RAX: 0000000000000000 RBX: 0000010037ffb118 RCX: 0000010064b61800
RDX: 0000000000000000 RSI: 000001005b553830 RDI: 000001007f2c6000
RBP: 000001007f2c6000 R08: 0000000000000000 R09: 00000100498666c0
R10: 00000100498666c0 R11: 00000100498666c0 R12: 0000000000000060
R13: 0000000000000008 R14: 00000000007ca9b7 R15: 0000000000000000
FS: 0000002a9555f360(0000) GS:ffffffff804a4f00(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000002a9555a000 CR3: 000000007fe2f000 CR4: 00000000000006e0
Process bonnie++ (pid: 1525, stackpage=1007e5363c0)
Stack: 0000010000000000 0000000000000001 000001005cc8d6e8 0000000000000000
0000000000001000 00000100583a0cc0 000001005b553898 0000000000000000
00000100583a0cc0 0000000000000060
Call Trace:<ffffffff8022e4a7>{generic_make_request+331}
<ffffffff8022e5b1>{submit_bio+247}
<ffffffff801961c6>{mpage_bio_submit+27}
<ffffffff801964d7>{do_mpage_readpage+493}
<ffffffff801b3f63>{ext2_get_block+0}
<ffffffff801b3f63>{ext2_get_block+0}
<ffffffff801b3f63>{ext2_get_block+0}
<ffffffff8015428c>{add_to_page_cache+129}
<ffffffff801b3f63>{ext2_get_block+0}
<ffffffff80196653>{mpage_readpages+161}
<ffffffff8015a5c3>{read_pages+57}
<ffffffff80158035>{buffered_rmqueue+510}
<ffffffff801580fe>{__alloc_pages+158}
<ffffffff8015ab04>{do_page_cache_readahead+515}
<ffffffff801545e8>{__lock_page+213}
<ffffffff8015acbd>{page_cache_readahead+396}
<ffffffff80154c04>{do_generic_mapping_read+193}
<ffffffff80154e28>{file_read_actor+0}
<ffffffff80155084>{__generic_file_aio_read+360}
<ffffffff80155157>{generic_file_read+116}
<ffffffff80181a75>{link_path_walk+2806}
<ffffffff80165bf4>{vma_merge+166}
<ffffffff802f5707>{thread_return+0} <ffffffff80172e01>{vfs_read+208}
<ffffffff80173006>{sys_read+57} <ffffffff801112ba>{system_call+126}
Code: 7e f9 e9 aa ea ff ff 90 90 90 41 57 41 56 41 55 49 89 fd bf
console shuts up ...
next prev parent reply other threads:[~2004-04-20 11:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 11:37 [PATCH] i2o_block Fix, possible CFQ elevator problem? Warren Togami
2004-04-19 12:12 ` Jens Axboe
2004-04-20 0:42 ` Warren Togami
[not found] ` <40848159.7090605@togami.com>
2004-04-20 7:08 ` Jens Axboe
2004-04-20 7:58 ` Warren Togami
2004-04-20 8:03 ` Jens Axboe
2004-04-20 8:59 ` Warren Togami
2004-04-20 9:05 ` Jens Axboe
2004-04-20 10:53 ` Warren Togami
2004-04-20 10:56 ` Jens Axboe
2004-04-20 11:29 ` Warren Togami [this message]
2004-04-20 11:34 ` Jens Axboe
2004-04-20 11:38 ` 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=40850987.1080603@redhat.com \
--to=wtogami@redhat.com \
--cc=Markus.Lidel@shadowconnect.com \
--cc=alan@redhat.com \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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.