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: Sun, 22 May 2011 00:30:50 +0400 [thread overview]
Message-ID: <1306009851.12379.16.camel@mulgrave.site> (raw)
In-Reply-To: <201105191944.p4JJiVVm029690@demeter1.kernel.org>
On Thu, 2011-05-19 at 19:44 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> --- Comment #2 from Fabio Coatti <fabio.coatti@gmail.com> 2011-05-19 19:44:30 ---
> Thanks for your answer :)
>
> Just tried (patch applied, compiled with make mrproper beforehand), but the
> result is pretty much the same.
> Interesting enough, If I reboot after using 2.6.38.5 for a while, the first
> boot on .6 is successful; following boots fails as shown so I guess that some
> hardware status can have a role into this, even if I don't know what happens.
> Here you can find the last capture with netconsole, with patch applied. (btw,
> how I can 100% sure to have applied it properly, besides checking the kernel
> date?)
Well, the first patch was just a guess. It looks like another queue
guard problem. However, I think this one is that the code thinks a dead
queue isn't stopped. Could you try this patch instead?
Thanks,
James
---
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index 2ad95fa..8166845 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -473,7 +473,9 @@ static inline void queue_flag_clear(unsigned int flag, struct request_queue *q)
}
#define blk_queue_tagged(q) test_bit(QUEUE_FLAG_QUEUED, &(q)->queue_flags)
-#define blk_queue_stopped(q) test_bit(QUEUE_FLAG_STOPPED, &(q)->queue_flags)
+#define blk_queue_stopped(q) \
+ (test_bit(QUEUE_FLAG_STOPPED, &(q)->queue_flags) || \
+ test_bit(QUEUE_FLAG_DEAD, &(q)->queue_flags))
#define blk_queue_nomerges(q) test_bit(QUEUE_FLAG_NOMERGES, &(q)->queue_flags)
#define blk_queue_noxmerges(q) \
test_bit(QUEUE_FLAG_NOXMERGES, &(q)->queue_flags)
next prev parent reply other threads:[~2011-05-21 20:30 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
2011-05-17 20:33 ` bugzilla-daemon
2011-05-19 19:44 ` bugzilla-daemon
2011-05-21 20:30 ` James Bottomley [this message]
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=1306009851.12379.16.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).