From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jens Axboe <axboe@fb.com>
Cc: Jan Kara <jack@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Brian J King <bjking1@us.ibm.com>
Subject: [BUG] kernel BUG at /.../block/cfq-iosched.c:3145!
Date: Wed, 09 Apr 2014 14:44:07 +1000 [thread overview]
Message-ID: <1397018647.3671.123.camel@pasglop> (raw)
Hi folks !
While testing a branch of fixes before I send it to Linus, which
happens to be based on 18a1a7a1d862ae0794a0179473d08a414dd49234,
I hit this:
kernel BUG at /home/benh/linux-powerpc-test/block/cfq-iosched.c:3145!
cpu 0x3c: Vector: 700 (Program Check) at [c000003ca69bb190]
pc: c00000000033b05c: .cfq_dispatch_requests+0x90/0x99c
lr: c00000000033b038: .cfq_dispatch_requests+0x6c/0x99c
sp: c000003ca69bb410
msr: 9000000000029032
current = 0xc000003ca63d32a0
paca = 0xc00000000ffef000 softe: 0 irq_happened: 0x01
pid = 3487, comm = smartd
kernel BUG at /home/benh/linux-powerpc-test/block/cfq-iosched.c:3145!
enter ? for help
[c000003ca69bb4c0] c00000000032000c .elv_drain_elevator+0x70/0xc8
[c000003ca69bb540] c000000000320140 .__elv_add_request+0xdc/0x27c
[c000003ca69bb5e0] c0000000003286f8 .blk_execute_rq_nowait+0xc0/0xf8
[c000003ca69bb670] c0000000003287ec .blk_execute_rq+0xbc/0xe8
[c000003ca69bb810] c000000000332350 .sg_io+0x218/0x39c
[c000003ca69bb930] c000000000332c3c .scsi_cmd_ioctl+0x270/0x4ac
[c000003ca69bba70] c0000000005d559c .sd_ioctl+0xa4/0xd8
[c000003ca69bbb20] c00000000032eb1c .__blkdev_driver_ioctl+0x34/0x54
[c000003ca69bbb90] c00000000032f83c .blkdev_ioctl+0x7b8/0x850
[c000003ca69bbc40] c00000000018d6e0 .block_ioctl+0x4c/0x60
[c000003ca69bbcb0] c0000000001691cc .do_vfs_ioctl+0x5cc/0x670
[c000003ca69bbd90] c0000000001692b4 .SyS_ioctl+0x44/0x70
[c000003ca69bbe30] c00000000000a024 syscall_exit+0x0/0x98
--- Exception: c00 (System Call) at 00003fffb5240ee0
The storage driver is our usual IBM "IPR".
Is that a known issue ?
Cheers,
Ben.
next reply other threads:[~2014-04-09 4:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 4:44 Benjamin Herrenschmidt [this message]
2014-04-09 13:35 ` [BUG] kernel BUG at /.../block/cfq-iosched.c:3145! Jens Axboe
2014-04-09 23:47 ` Benjamin Herrenschmidt
2014-04-10 0:02 ` Benjamin Herrenschmidt
2014-04-10 1:31 ` Jens Axboe
2014-04-10 1:36 ` Benjamin Herrenschmidt
2014-04-10 1:38 ` Jens Axboe
2014-04-10 2:25 ` Jens Axboe
2014-04-10 3:35 ` Benjamin Herrenschmidt
2014-04-10 3:52 ` Jens Axboe
2014-04-10 6:45 ` Benjamin Herrenschmidt
2014-04-10 13:47 ` Jens Axboe
2014-04-10 18:10 ` 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=1397018647.3671.123.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@fb.com \
--cc=bjking1@us.ibm.com \
--cc=fweisbec@gmail.com \
--cc=jack@suse.cz \
--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