From: Badari Pulavarty <pbadari@us.ibm.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Zach Brown <zach.brown@oracle.com>
Subject: DIO panic on 2.6.21.5
Date: Wed, 27 Jun 2007 20:01:45 -0700 [thread overview]
Message-ID: <46832499.40807@us.ibm.com> (raw)
Hi Zach,
One of our perf. team ran into this while doing some runs.
I didn't see anything obvious - it looks like we converted
async IO to synchronous one. I didn't spend much time digging
around.
Is this a known issue ? Any ideas ?
Thanks,
Badari
------------[ cut here ]------------
kernel BUG at fs/direct-io.c:1113!
invalid opcode: 0000 [1] SMP
CPU 11
Modules linked in: oprofile raw capability commoncap qla2xxx ipv6 button
battery ac loop dm_mod tg3 ext3 jbd edd fan thermal processor scsi_transport_fc
sg aic94xx libsas firmware_class scsi_transport_sas serverworks sd_mod scsePid:
9709, comm: db2sysc Not tainted 2.6.21.5-smp #1
RIP: 0010:[<ffffffff802a7a1a>] [<ffffffff802a7a1a>]
__blockdev_direct_IO+0x96c/0xa4a
RSP: 0018:ffff810c3d3efc08 EFLAGS: 00010202
RAX: 0000000000000246 RBX: ffff810041768b24 RCX: ffffffff80406918
RDX: 0000000000000000 RSI: 0000000000000246 RDI: ffff810041768b24
RBP: ffff810041768800 R08: 0000000000000086 R09: ffff81003f0a2370
R10: ffff810c3f3ee9d8 R11: ffffffff802e9716 R12: 0000000000000001
R13: fffffffffffffdef R14: ffff810c5beb42b0 R15: 0000000000000000
FS: 00002b3d14ffe940(0000) GS:ffff810c444c95c0(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002b3e84f57000 CR3: 000000004511c000 CR4: 00000000000006e0
Process db2sysc (pid: 9709, threadinfo ffff810c3d3ee000, task ffff810041fee760)
Stack: ffff810c42f0fbc0 000000004c1f4000 ffff811836306d48 00000011803e7f95
0000000000000009 0000000000000000 0000000000000008 0000000000000000
ffff810041fee760 0000000900000001 0000000000000001 ffff810024ac9948
Call Trace:
[<ffffffff802a67c7>] blkdev_direct_IO+0x45/0x4a
[<ffffffff802a66ec>] blkdev_get_blocks+0x0/0x96
[<ffffffff80260108>] generic_file_direct_IO+0xbd/0xfb
[<ffffffff802601a6>] generic_file_direct_write+0x60/0xf5
[<ffffffff80260b70>] __generic_file_aio_write_nolock+0x2e7/0x410
[<ffffffff8029a0ce>] aio_read_evt+0x9a/0x108
[<ffffffff80260d8e>] generic_file_aio_write_nolock+0x34/0x80
[<ffffffff80260d5a>] generic_file_aio_write_nolock+0x0/0x80
[<ffffffff80299d23>] aio_rw_vect_retry+0x72/0x14a
[<ffffffff8029a63f>] aio_run_iocb+0x9a/0x134
[<ffffffff8029b10a>] io_submit_one+0x311/0x35e
[<ffffffff8029b678>] sys_io_submit+0x9b/0x101
[<ffffffff80229986>] default_wake_function+0x0/0xe
[<ffffffff80209b8e>] system_call+0x7e/0x83
Code: 0f 0b eb fe 4d 85 e4 75 1d 48 8b 74 24 08 44 89 ea 48 89 ef
RIP [<ffffffff802a7a1a>] __blockdev_direct_IO+0x96c/0xa4a
RSP <ffff810c3d3efc08>
next reply other threads:[~2007-06-28 3:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 3:01 Badari Pulavarty [this message]
2007-06-29 22:10 ` DIO panic on 2.6.21.5 Zach Brown
2007-06-30 0:03 ` Badari Pulavarty
2007-07-03 22:28 ` [PATCH] dio: remove bogus refcounting BUG_ON Zach Brown
2007-07-05 2:25 ` Badari Pulavarty
2007-07-05 3:53 ` Suparna Bhattacharya
2007-07-05 17:11 ` Zach Brown
2007-07-05 17:16 ` Badari Pulavarty
2007-07-05 17:21 ` Zach Brown
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=46832499.40807@us.ibm.com \
--to=pbadari@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zach.brown@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).