[Bug 151661] Adaptec 3805 prints "AAC: Host adapter dead -1" every 10 seconds but works fine anyway

https://bugzilla.kernel.org/show_bug.cgi?id=151661 Chris "SKip" Mac-Stoker changed: What|Removed |Added CC|

Re: [PATCH v2 2/2] libata-core: do not set dev->max_sectors for LBA48 devices

On 12 August 2016 at 10:01, Martin K. Petersen wrote: > > Again, the point of max_hw_sectors and max_dev_sectors is to enforce the > hard limits of controller and device respectively. Nothing else. > Sounds like libata-scsi is doing something wrong then. It should not

Re: [RFC] libata-scsi: make sure Maximum Write Same Length is not too large

On 12 August 2016 at 09:34, Martin K. Petersen wrote: >> "Tom," == tom ty89 writes: > > Tom, > > + put_unaligned_be64(65535 * ATA_MAX_TRIM_RNUM / > + (sector_size / 512), [36]); > > MAXIMUM WRITE

Re: [RFC] sd: dynamically adjust SD_MAX_WS16_BLOCKS as per the actual logical block size

On 12 August 2016 at 11:10, Martin K. Petersen wrote: > > However, the CDB transfer length limit is really not the main issue > here, it's bi_size that we need to enforce. > > After contemplating a bit I think it would be cleanest to add > BLK_MAX_BIO_SECTORS and clamp

Re: [RFC] sd: dynamically adjust SD_MAX_WS16_BLOCKS as per the actual logical block size

> "Tom" == tom ty89 writes: Tom, Tom> However, SD_MAX_WS16_BLOCKS is used to check values that are, for Tom> example, orignated from Maximum Write Same Length field on the Tom> Block Limit VPD. Such field expresses the number of blocks in terms Tom> of the actual logical

Re: [PATCH 0/2] ibmvfc: FC-TAPE Support

> "Tyrel" == Tyrel Datwyler writes: Tyrel> On 08/03/2016 02:36 PM, Tyrel Datwyler wrote: >> This patchset introduces optional FC-TAPE/FC Class 3 Error Recovery >> to the ibmvfc client driver. >> >> Tyrel Datwyler (2): ibmvfc: Set READ FCP_XFER_READY DISABLED bit

Re: [PATCH] Update WRITE_SAME timeout in sd_setup_discard_cmnd

> "Shaun" == Shaun Tancheff writes: Shaun, Shaun> In sd_setup_discard_cmnd() there are a some discard methods that Shaun> fall back to using WRITE_SAME. It appears that those paths using Shaun> WRITE_SAME should also use the SD_WRITE_SAME_TIMEOUT instead of Shaun> the

Re: [PATCH v2 2/2] libata-core: do not set dev->max_sectors for LBA48 devices

> "Tom" == Tom Yan writes: Hey Tom, Tom> Shouldn't we use Maximum Transfer Length to derive max_sectors (and Tom> get rid of the almost useless max_dev_sectors)? MAXIMUM TRANSFER LENGTH could be gigabytes. Some disks report it as the full capacity of the device. Again,

Re: [RFC] libata-scsi: make sure Maximum Write Same Length is not too large

> "Tom," == tom ty89 writes: Tom, + put_unaligned_be64(65535 * ATA_MAX_TRIM_RNUM / + (sector_size / 512), [36]); MAXIMUM WRITE SAME LENGTH is in units of the device's logical block size. -- Martin K. Petersen Oracle

RE: [PATCH V4 0/2] smartpqi: initial commit of Microsemi smartpqi driver

> -Original Message- > From: Martin K. Petersen [mailto:martin.peter...@oracle.com] > Sent: Wednesday, August 10, 2016 9:26 PM > To: Don Brace > Cc: Martin K. Petersen; j...@linux.vnet.ibm.com; Viswas G; Mahesh > Rajashekhara; h...@infradead.org; Scott Teel; Kevin Barnett; Justin Lindley;

[RFC] sd: dynamically adjust SD_MAX_WS16_BLOCKS as per the actual logical block size

From: Tom Yan WRITE SAME (16) command can technically handle up to 32-bit number of blocks. However, since 32-bit is also the limitation of the maximum number of bytes that can be represented in the block layer, the current SD_MAX_WS16_BLOCKS was hence derived from the

Re: [PATCH 0/3] nvme-fabrics: Add NVME FC Transport support to lpfc

On Fri, Jul 22, 2016 at 05:24:00PM -0700, James Smart wrote: > > This patchset adds NVME support to the lpfc FC driver. It reworks > the core driver for both NVME and SCSI protocol support, then adds the > nvme-over-fabrics host and target interfaces which connect to the > NVME FC transport

Re: [PATCH 5/5] nvme-fabrics: Add FC LLDD loopback driver to test FC host and target transport

On Fri, Jul 22, 2016 at 05:23:59PM -0700, James Smart wrote: > > Add FC LLDD loopback driver to test FC host and target transport within > nvme-fabrics > > To aid in the development and testing of the lower-level api of the FC > transport, this loopback driver has been created to act as if it

Re: [PATCH 4/5] nvme-fabrics: Add target FC transport support

> +config NVME_TARGET_FC > + tristate "NVMe over Fabrics FC target driver" > + select NVME_TARGET this should be a depends, NVME_TARGET is a user visible option. > + /* TODO: better to use dma_map_page() ?*/ > + iod->rspdma = dma_map_single(tgtport->dev,

Re: [PATCH] scsi: fix upper bounds check of sense key in scsi_sense_key_string()

On 08/09/2016 01:08 PM, Bart Van Assche wrote: > On 08/04/2016 02:32 PM, Tyrel Datwyler wrote: >> Commit 655ee63cf371 added a "Completed" sense string with key 0xF to >> snstext[], but failed to updated the upper bounds check of the sense key in >> scsi_sense_key_string(). >> >> Fixes:

Re: [RFC] libata-scsi: make sure Maximum Write Same Length is not too large

The patch isn't about how the request from the block layer will be processed (to form the SCSI commands). What it addresses is blk_queue_max_write_same_sectors() and blk_queue_max_discard_sectors() that are called in the SCSI disk driver. You can see that they are called with an input of the

Re: [PATCH 3/5] nvme-fabrics: Add host FC transport support

This looks mostly fine, a few nitpicks below: > +config NVME_FC > + tristate "NVM Express over Fabrics FC host driver" > + depends on BLK_DEV_NVME This should be select NVME_CORE instead. The existing RDMA and loop drivers also get this wrong, but I'll sned a patch to fix it

Re: [PATCH 2/5] nvme-fabrics: Add FC transport LLDD api definitions

Looks fine, Reviewed-by: Christoph Hellwig -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 1/5] nvme-fabrics: Add FC transport FC-NVME definitions

Looks fine, Reviewed-by: Christoph Hellwig -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH] add u64 number parser

On Sat, Jul 23, 2016 at 08:52:18AM -0700, James Smart wrote: > > On 7/22/2016 6:32 PM, Bart Van Assche wrote: > > On 07/22/16 17:23, James Smart wrote: > > > +buf = kmalloc(len + 1, GFP_KERNEL); > > > +if (!buf) > > > +return -ENOMEM; > > > +memcpy(buf, s->from, len); > > > +

Re: [PATCH] nvme-fabrics: patch target code in prep for FC transport support

Looks fine, Reviewed-by: Christoph Hellwig -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH] nvme-fabrics: set sqe.command_id in core, not transports

This needs to cover the loop and PCI driver a swell. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 0/2] ibmvfc: FC-TAPE Support

On 08/03/2016 02:36 PM, Tyrel Datwyler wrote: > This patchset introduces optional FC-TAPE/FC Class 3 Error Recovery to the > ibmvfc client driver. > > Tyrel Datwyler (2): > ibmvfc: Set READ FCP_XFER_READY DISABLED bit in PRLI > ibmvfc: add FC Class 3 Error Recovery support > >

[PATCH] Update WRITE_SAME timeout in sd_setup_discard_cmnd

In sd_setup_discard_cmnd() there are a some discard methods that fall back to using WRITE_SAME. It appears that those paths using WRITE_SAME should also use the SD_WRITE_SAME_TIMEOUT instead of the default SD_TIMEOUT. Signed-off-by: Shaun Tancheff --- I don't have a

Re: [dm-devel] [PATCH] dm-mpath: always return reservation conflict

ping? On Tue, Aug 02, 2016 at 02:36:32PM +0200, Christoph Hellwig wrote: > From: Hannes Reinecke > > If dm-mpath encounters an reservation conflict it should not fail the > path (as communication with the target is not affected) but should > rather retry on another path. However,

[PATCH 10/14] lpfc: Code cleanup for lpfc_sriov_nr_virtfn parameter

Code cleanup for lpfc_sriov_nr_virtfn parameter Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_attr.c | 35 +++ 1 file changed, 3 insertions(+), 32 deletions(-) diff --git

[PATCH 12/14] lpfc: Revise strings with full lpfc parameter name

Revise strings with full lpfc parameter name Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_attr.c | 23 --- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git

[PATCH 09/14] lpfc: Code cleanup for lpfc_max_scsicmpl_time parameter

Code cleanup for lpfc_max_scsicmpl_time parameter Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_attr.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git

[PATCH 11/14] lpfc: Fix crash on adapter reinit

Fix crash on adapter reinit Had unset fields passed to pci_pool_destroy() on teardown. Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_mem.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-)

[PATCH 13/14] lpfc: Fix lost target in pt-to-pt connect

Fix lost target in pt-to-pt connect Change reject code to something that allows a retry Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_els.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH 05/14] lpfc: Code clean up for lpfc_iocb_cnt parameter

Code clean up for lpfc_iocb_cnt parameter Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_attr.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/drivers/scsi/lpfc/lpfc_attr.c

[PATCH 04/14] lpfc: Make lpfc_prot_mask and lpfc_prot_guard per hba parameters

Make lpfc_prot_mask and lpfc_prot_guard per hba parameters Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc.h | 2 ++ drivers/scsi/lpfc/lpfc_attr.c | 23 ++-

[PATCH 07/14] lpfc: Code cleanup for lpfc_aer_support parameter

Code cleanup for lpfc_aer_support parameter Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_attr.c | 43 +++ 1 file changed, 3 insertions(+), 40 deletions(-) diff

[PATCH 06/14] lpfc: Code cleanup for lpfc_enable_rrq parameter

Code cleanup for lpfc_enable_rrq parameter Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_attr.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/scsi/lpfc/lpfc_attr.c

[PATCH 14/14] lpfc: lpfc version change to 11.2.0.2

lpfc version change to 11.2.0.2 Note: expects to be on top of prior lpfc 11.2.0.0. rev and not on top of lpfc rev 11.2.0.1 which has fc-nvme mods as well. The patches in this set should apply to 11.2.0.1, excepting this version change. For now, this patch based on contents in scsi-misc branch of

[PATCH 08/14] lpfc: Code cleanup for lpfc_topology parameter

Code cleanup for lpfc_topology parameter Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_attr.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/scsi/lpfc/lpfc_attr.c

[PATCH 01/14] lpfc: Double WQ element count to keep iops up

Double WQ element count to keep iops up On embedded io queues, use the default element count, which is twice the size of the default large WQE element count. Signed-off-by: Dick Kennedy Signed-off-by: James Smart ---

[PATCH 00/14] lpfc: Update driver to version 11.2.0.2

This patch set updates the lpfc driver to revision 11.2.0.00 The patches were cut against scsi-misc James Smart (14): Double WQ element count to keep iops up Fix sg_reset on SCSI device causing kernel crash Set driver environment data on adapter Make lpfc_prot_mask and lpfc_prot_guard

[PATCH 03/14] lpfc: Set driver environment data on adapter

Set driver environment data on adapter Signed-off-by: Dick Kennedy Signed-off-by: James Smart --- drivers/scsi/lpfc/lpfc_hw4.h | 12 drivers/scsi/lpfc/lpfc_sli.c | 29 + 2 files changed, 41

[PATCH 02/14] lpfc: Fix sg_reset on SCSI device causing kernel crash

Fix sg_reset on SCSI device causing kernel crash Driver could reference stale node pointers in task mgmt call. Changed to use resetting cmd and look up node pointer in task mgmt function. Signed-off-by: Dick Kennedy Signed-off-by: James Smart

Re: [PATCH] SAS: use sas_rphy instead of sas_end_device to obtain address.

On Thu, 2016-08-11 at 18:43 +0200, Johannes Thumshirn wrote: > On Thu, Aug 11, 2016 at 08:09:35AM -0700, James Bottomley wrote: > > On Thu, 2016-08-11 at 09:59 +0200, Johannes Thumshirn wrote: > > > Since commit 3f8d6f2a0 ('ses: fix discovery of SATA devices in > > > SAS > > > enclosures')

Re: [RFC] libata-scsi: make sure Maximum Write Same Length is not too large

On Thu, Aug 11, 2016 at 3:26 AM, wrote: > From: Tom Yan > > Currently we advertise Maximum Write Same Length based on the > maximum number of sectors that one-block TRIM payload can cover. > The field are used to derived discard_max_bytes and >

Re: [dm-devel] dm-mq and end_clone_request()

- Original Message - > From: "Laurence Oberman" > To: "Bart Van Assche" > Cc: dm-de...@redhat.com, linux-scsi@vger.kernel.org, "Mike Snitzer" > , "Johannes Thumshirn" > > Sent: Wednesday, August

Re: [PATCH] SAS: use sas_rphy instead of sas_end_device to obtain address.

On Thu, Aug 11, 2016 at 08:09:35AM -0700, James Bottomley wrote: > On Thu, 2016-08-11 at 09:59 +0200, Johannes Thumshirn wrote: > > Since commit 3f8d6f2a0 ('ses: fix discovery of SATA devices in SAS > > enclosures') ses_match_to_enclosure() is calling sas_get_address(), > > which is coming from

[Bug 151991] New: HP Help Desk Number 1 (888) 990-8801

https://bugzilla.kernel.org/show_bug.cgi?id=151991 Bug ID: 151991 Summary: HP Help Desk Number 1 (888) 990-8801 Product: SCSI Drivers Version: 2.5 Kernel Version: le Hardware: All OS: Linux Tree: Mainline

[Bug 151661] Adaptec 3805 prints "AAC: Host adapter dead -1" every 10 seconds but works fine anyway

https://bugzilla.kernel.org/show_bug.cgi?id=151661 --- Comment #3 from Piotr Szymaniak --- Created attachment 228391 --> https://bugzilla.kernel.org/attachment.cgi?id=228391=edit dmesg with mentioned Alex patch -- You are receiving this mail because: You are watching the

[Bug 151661] Adaptec 3805 prints "AAC: Host adapter dead -1" every 10 seconds but works fine anyway

https://bugzilla.kernel.org/show_bug.cgi?id=151661 --- Comment #2 from Piotr Szymaniak --- Created attachment 228381 --> https://bugzilla.kernel.org/attachment.cgi?id=228381=edit dmesg vanilla 4.7 -- You are receiving this mail because: You are watching the assignee of

[Bug 151661] Adaptec 3805 prints "AAC: Host adapter dead -1" every 10 seconds but works fine anyway

https://bugzilla.kernel.org/show_bug.cgi?id=151661 --- Comment #1 from Piotr Szymaniak --- (I'm a kernel bugzilla newbie and as newbie I'm not sure how much attention gets kernel bugzilla and do this gets along with mailing lists and the other way around. So I'm posting here

Re: [PATCH] SAS: use sas_rphy instead of sas_end_device to obtain address.

On Thu, 2016-08-11 at 09:59 +0200, Johannes Thumshirn wrote: > Since commit 3f8d6f2a0 ('ses: fix discovery of SATA devices in SAS > enclosures') ses_match_to_enclosure() is calling sas_get_address(), > which is coming from commit bcf508c13385 ('scsi_transport_sas: add > function to get SAS

Re: [PATCH 10/10] zfcp: trace full payload of all SAN records (req,resp,iels)

On 08/10/2016 06:30 PM, Steffen Maier wrote: > This was lost with commit 2c55b750a884b86dea8b4cc5f15e1484cc47a25c > ("[SCSI] zfcp: Redesign of the debug tracing for SAN records.") > but is necessary for problem determination, e.g. to see the > currently active zone set during automatic port scan.

Re: [PATCH 09/10] zfcp: fix payload trace length for SAN request

On 08/10/2016 06:30 PM, Steffen Maier wrote: > commit 2c55b750a884b86dea8b4cc5f15e1484cc47a25c > ("[SCSI] zfcp: Redesign of the debug tracing for SAN records.") > started to add FC_CT_HDR_LEN which made zfcp dump random data > out of bounds for RSPN GS responses because u.rspn.rsp > is the largest

Re: [PATCH 08/10] zfcp: fix D_ID field with actual value on tracing SAN responses

On 08/10/2016 06:30 PM, Steffen Maier wrote: > With commit 2c55b750a884b86dea8b4cc5f15e1484cc47a25c > ("[SCSI] zfcp: Redesign of the debug tracing for SAN records.") > we lost the N_Port-ID where an ELS response comes from. > With commit 7c7dc196814b9e1d5cc254dc579a5fa78ae524f7 > ("[SCSI] zfcp:

Re: [PATCH 07/10] zfcp: restore tracing of handle for port and LUN with HBA records

On 08/10/2016 06:30 PM, Steffen Maier wrote: > This information was lost with > commit a54ca0f62f953898b05549391ac2a8a4dad6482b > ("[SCSI] zfcp: Redesign of the debug tracing for HBA records.") > but is required to debug e.g. invalid handle situations. > > Signed-off-by: Steffen Maier

Re: [PATCH 06/10] zfcp: trace on request for open and close of WKA port

On 08/10/2016 06:30 PM, Steffen Maier wrote: > Since commit a54ca0f62f953898b05549391ac2a8a4dad6482b > ("[SCSI] zfcp: Redesign of the debug tracing for HBA records.") > HBA records no longer contain WWPN, D_ID, or LUN > to reduce duplicate information which is already in REC records. > In contrast

Re: [PATCH 05/10] zfcp: restore: Dont use 0 to indicate invalid LUN in rec trace

On 08/10/2016 06:30 PM, Steffen Maier wrote: > bring back > commit d21e9daa63e009ce5b87bbcaa6d11ce48e07bbbe > ("[SCSI] zfcp: Dont use 0 to indicate invalid LUN in rec trace") > which was lost with > commit ae0904f60fab7cb20c48d32eefdd735e478b91fb > ("[SCSI] zfcp: Redesign of the debug tracing for

Re: [PATCH 04/10] zfcp: retain trace level for SCSI and HBA FSF response records

On 08/10/2016 06:30 PM, Steffen Maier wrote: > While retaining the actual filtering according to trace level, > the following commits started to write such filtered records > with a hardcoded record level of 1 instead of the actual record level: > commit 250a1352b95e1db3216e5c5d4f4365bea5122f4a >

Re: [PATCH 03/10] zfcp: close window with unblocked rport during rport gone

On 08/10/2016 06:30 PM, Steffen Maier wrote: > On a successful end of reopen port forced, > zfcp_erp_strategy_followup_success() re-uses the port erp_action > and the subsequent zfcp_erp_action_cleanup() now > sees ZFCP_ERP_SUCCEEDED with > erp_action->action==ZFCP_ERP_ACTION_REOPEN_PORT > instead

Re: [PATCH 02/10] zfcp: fix ELS/GS request length for hardware data router

On 08/10/2016 06:30 PM, Steffen Maier wrote: > In the hardware data router case, introduced with kernel 3.2 > commit 86a9668a8d29 ("[SCSI] zfcp: support for hardware data router") > the ELS/GS request length needs to be initialized > as in the chained SBAL case. > > Otherwise, the FCP channel

Re: [PATCH 01/10] zfcp: fix fc_host port_type with NPIV

On 08/10/2016 06:30 PM, Steffen Maier wrote: > For an NPIV-enabled FCP device, zfcp can erroneously show > "NPort (fabric via point-to-point)" instead of "NPIV VPORT" > for the port_type sysfs attribute of the corresponding > fc_host. > s390-tools that can be affected are dbginfo.sh and ziomon. >

RE: [PATCH] mpt3sas: Fix resume on WarpDrive flash cards

Hi, Please consider this patch as Acked-by: Chaitra P B Thanks, Chaitra -Original Message- From: Greg Edwards [mailto:gedwa...@fireweed.org] Sent: Saturday, July 30, 2016 9:36 PM To: Sathya Prakash; Chaitra P B; Suganath Prabu Subramani; James E.J.

Re: [PATCH v2 2/2] libata-core: do not set dev->max_sectors for LBA48 devices

On 11 August 2016 at 11:37, Martin K. Petersen wrote: >> "Tom" == Tom Yan writes: > > I don't agree with conflating the optimal transfer size and the maximum > supported ditto. Submitting the largest possible I/O to a device does > not

[RFC] libata-scsi: make sure Maximum Write Same Length is not too large

From: Tom Yan Currently we advertise Maximum Write Same Length based on the maximum number of sectors that one-block TRIM payload can cover. The field are used to derived discard_max_bytes and write_same_max_bytes limits in the block layer, which currently can at max be

[PATCH] SAS: use sas_rphy instead of sas_end_device to obtain address.

Since commit 3f8d6f2a0 ('ses: fix discovery of SATA devices in SAS enclosures') ses_match_to_enclosure() is calling sas_get_address(), which is coming from commit bcf508c13385 ('scsi_transport_sas: add function to get SAS endpoint address'). sas_get_address() itself calls sas_sdev_to_rdev() which