From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Bug 35282] BUG() in 2.6.38.6
Date: Tue, 17 May 2011 23:55:02 +0400 [thread overview]
Message-ID: <1305662102.2667.25.camel@mulgrave.site> (raw)
In-Reply-To: <201105171917.p4HJHUhx019356@demeter2.kernel.org>
On Tue, 2011-05-17 at 19:17 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=35282
> May 15 16:09:32 192.168.42.2 Call Trace:
> May 15 16:09:32 192.168.42.2 <IRQ>
> May 15 16:09:32 192.168.42.2
> May 15 16:09:32 192.168.42.2 [<ffffffff812160eb>] ? __blk_run_queue+0x24/0x7e
> May 15 16:09:32 192.168.42.2 [<ffffffff81216167>] ? blk_run_queue+0x22/0x34
> May 15 16:09:32 192.168.42.2 [<ffffffff812b2fde>] ? scsi_run_queue+0x2ce/0x36d
> May 15 16:09:32 192.168.42.2 [<ffffffff812b39ef>] ? scsi_next_command+0x2d/0x39
> May 15 16:09:32 192.168.42.2 [<ffffffff812b4289>] ?
> scsi_io_completion+0x1ca/0x3fd
This looks like it might be related to the queue guard in
__elv_next_request() again, could you try this patch:
http://marc.info/?l=linux-scsi&m=130348673628282
Thanks,
James
next prev parent reply other threads:[~2011-05-17 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-35282-11613@https.bugzilla.kernel.org/>
2011-05-17 19:17 ` [Bug 35282] BUG() in 2.6.38.6 bugzilla-daemon
2011-05-17 19:55 ` James Bottomley [this message]
2011-05-17 20:33 ` bugzilla-daemon
2011-05-19 19:44 ` bugzilla-daemon
2011-05-21 20:30 ` James Bottomley
2011-05-24 17:18 ` [PATCH] block: fix oops in blk_run_queue() James Bottomley
2011-05-25 11:28 ` Jens Axboe
2011-05-21 20:31 ` [Bug 35282] BUG() in 2.6.38.6 bugzilla-daemon
2011-05-21 21:40 ` bugzilla-daemon
2011-05-27 9:53 ` bugzilla-daemon
2011-05-28 16:56 ` James Bottomley
2011-05-28 16:57 ` bugzilla-daemon
2011-06-12 20:54 ` bugzilla-daemon
2011-06-12 20:55 ` bugzilla-daemon
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=1305662102.2667.25.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=bugzilla-daemon@bugzilla.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 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).