[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151129164947.GA15021@redhat.com>
Date: Sun, 29 Nov 2015 11:49:48 -0500
From: Mike Snitzer <snitzer@...hat.com>
To: Markus Trippelsdorf <markus@...ppelsdorf.de>
Cc: Hannes Reinecke <hare@...e.de>, Jens Axboe <axboe@...com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
Christoph Hellwig <hch@....de>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Ewan Milne <emilne@...hat.com>, Jeff Moyer <jmoyer@...hat.com>
Subject: Re: block: Always check queue limits for cloned requests
On Sun, Nov 29 2015 at 11:15am -0500,
Markus Trippelsdorf <markus@...ppelsdorf.de> wrote:
> On 2015.11.29 at 16:43 +0100, Hannes Reinecke wrote:
> > On 11/29/2015 12:49 PM, Markus Trippelsdorf wrote:
> > >
> > > I'm still seeing the issue (BUG at drivers/scsi/scsi_lib.c:1096!) even
> > > with this patch applied.
> > >
> > > markus@x4 linux % git describe
> > > v4.4-rc2-215-g081f3698e606
> > >
> > Can you generate a crashdump?
> > I would need to cross-check with the other dumps I'm having to figure
> > out if this really is the same issue.
> > There have been other reports (and fixes) which show we're fighting
> > several distinct issues here.
>
> Unfortunately no. The crash happens on the disk where I store my log
> files. And after it happened the magic SysRq keys don't work anymore.
>
> The crash only happens on my spinning rust drive that uses the cfq
> scheduler. The SSDs (deadline) are fine.
>
> The BUG happens reproducibly when building http://www.sagemath.org/ on
> that drive.
Are you using DM multipath? If unsure, please let us know which
device(s) map to the "spinning rust drive", and provide output from:
lsblk
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists