[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e3e32fd801cb1270cddec6fc1ea3dabad4473b64.camel@wdc.com>
Date: Thu, 2 Aug 2018 05:04:00 +0000
From: Bart Van Assche <Bart.VanAssche@....com>
To: "linux@...ck-us.net" <linux@...ck-us.net>,
"James.Bottomley@...senPartnership.com"
<James.Bottomley@...senPartnership.com>,
"tom.leiming@...il.com" <tom.leiming@...il.com>
CC: "sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>
Subject: Re: linux-next: Tree for Aug 1
On Wed, 2018-08-01 at 21:58 -0700, Guenter Roeck wrote:
> I am running out of ideas. Any thoughts on how to track this down further ?
Is a shell available when the hang occurs? If so, it would be helpful if you
could provide a dump of the information in /sys/kernel/debug/block. There is
namely detailed information in that directory about pending commands.
Bart.
Powered by blists - more mailing lists