On 04/08/2013 05:37 PM, Tomas Henzl wrote:
On 04/05/2013 05:24 PM, James Smart wrote:
On 4/4/2013 6:17 AM, Hannes Reinecke wrote:
On 03/31/2013 07:44 PM, Tomas Henzl wrote:
What we can do is to decode the LUN and compare it to max_lun provided by
the driver,
I think that sg_luns is able to
Thanks for your insights Baruch.
The crc count did not increase any further - so this was probably just
small oddity (was zero before when the write-same issue already
happened). The real issue however does persist. I found a way to
reliably trigger the log messages. Using a program called
Add support for sending UFS query requests through tagged command
queuing. This design allows queuing query requests in any open slot
along with other SCSI commands. In this way there is no need to
save a slot in the requests queue and decrease its size.
A query request is posing to a SCSI
Hi James,
On 18:39 Mon 08 Apr , James Bottomley wrote:
On Mon, 2013-04-08 at 13:42 +0200, Oskar Andero wrote:
On 14:36 Thu 07 Mar , oskar.and...@sonymobile.com wrote:
From: syunsuke.x.itou syunsuke.x.i...@sonymobile.com
By repeatadly connecting/disconnecting a USB masstorage
Hello everyone,
an update: I was able to reproduce the problem on my testing
machine (at least sort of) and confirmed that
c8dc9c6 md: raid1,10: Handle REQ_WRITE_SAME flag in write bios
fixes things.
Also applied c8dc9c6 to the main system's 3.8.6 kernel. Working without
any issues.
One
-Original Message-
From: Hannes Reinecke [mailto:h...@suse.de]
Sent: Tuesday, 09 April, 2013 2:38 AM
To: Tomas Henzl
Cc: james.sm...@emulex.com; Chad Dupuis; linux-scsi@vger.kernel.org; James
Bottomley; Jeremy Linton; Elliott, Robert (Server Storage); Bart Van Assche;
Bud Brown
On 04/09/2013 04:27 PM, Elliott, Robert (Server Storage) wrote:
-Original Message-
From: Hannes Reinecke [mailto:h...@suse.de]
Sent: Tuesday, 09 April, 2013 2:38 AM
To: Tomas Henzl
Cc: james.sm...@emulex.com; Chad Dupuis; linux-scsi@vger.kernel.org; James
Bottomley; Jeremy Linton;
It's making checkpatch unusable on most drivers because it's spewing
tons of bogus warnings. The problem is the assumption that studly caps
is always wrong: it isn't if the variables are named after the various
conventions in the hardware programming guides (which are usually
written by Microsoft
8 matches
Mail list logo