https://bugzilla.kernel.org/show_bug.cgi?id=35282 --- Comment #3 from Anonymous Emailer <anonymous@xxxxxxxxxxxxxxxxxxxx> 2011-05-21 20:31:19 --- Reply-To: James.Bottomley@xxxxxxxxxxxxxxxxxxxxx On Thu, 2011-05-19 at 19:44 +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > --- Comment #2 from Fabio Coatti <fabio.coatti@xxxxxxxxx> 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) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
