Observing Softlockup's while running heavy IOs

Hi, Problem statement: Observing softlockups while running heavy IOs on 8 SSD drives connected behind our LSI SAS 3004 HBA. System configuration: OS & kernel version: Fedora 23, v4.2.3-300.fc23.x86_64 NUMA : disabled, CPUs : 24 logical cpus, SCSI_MQ: enabled Driver : mpt3sas, MSIx vectors: we

Re: [PATCH 1/6] cxlflash: Avoid mutex when destroying context

Acked-by: Manoj N. Kumar On 8/9/2016 6:39 PM, Matthew R. Ochs wrote: Context information structures are protected by a mutex that is held when accessing/manipulating the context. When the code that manages these structures was authored, a decision was made to include

[Bug 101841] iommu memory handling cause mmblock devices stop working

https://bugzilla.kernel.org/show_bug.cgi?id=101841 ingvarthorv...@gmail.com changed: What|Removed |Added CC||ingvarthorv...@gmail.com ---

[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 #8 from David Gravereaux --- The 3405 in my lab computer exhibits the same symptoms. Ubuntu 16.04 LTS with kernel 4.4.0-34-generic, also. Both Adaptec 3805 and 3405 models -- You are receiving this mail

[REPOST PATCH 2/5] scsi: bnx2fc: convert per-CPU thread to kworker

The driver creates its own per-CPU threads which are updated based on CPU hotplug events. It is also possible to use kworkers and remove some of the infrastructure get the same job done while saving a few lines of code. bnx2fc_percpu_io_thread() becomes bnx2fc_percpu_io_work() which is mostly the

[REPOST PATCH 1/5] scsi: bnx2i: convert to kworker

The driver creates its own per-CPU threads which are updated based on CPU hotplug events. It is also possible to use kworkers and remove some of the infrastructure get the same job done while saving a few lines of code. The DECLARE_PER_CPU() definition is moved into the header file where it

[REPOST PATCH 3/5] scsi: bnx2fc: clean up header definitions

- All symbols which are only used within one .c file are marked static and removed from the bnx2fc.h file if possible. - the declarion of bnx2fc_percpu is moved into the header file This patch was only compile-tested due to -ENODEV. Cc: qlogic-storage-upstr...@qlogic.com Cc: Christoph Hellwig

[REPOST PATCH 4/5] scsi: bnx2fc: annoate unlock + release for sparse

The caller of bnx2fc_abts_cleanup() holds the tgt->tgt_lock lock and it is expected to release the lock during wait_for_completion() and acquire the lock afterwards. This patch was only compile-tested due to -ENODEV. Cc: qlogic-storage-upstr...@qlogic.com Cc: Christoph Hellwig

[REPOST PATCH 5/5] scsi: bnx2fc: convert bnx2fc_l2_rcv_thread() to worker

This is not driven by the hotplug conversation but while I am at it looks like a good candidate. Converting the thread to a kworker user removes also the kthread member from struct fcoe_percpu_s. This driver uses the struct fcoe_percpu_s but it does not need the crc_eof_page member, only the work

Re: [PATCH v3 1/3] sas: provide stub implementation for scsi_is_sas_rphy

Hi Johannes, [auto build test WARNING on scsi/for-next] [also build test WARNING on v4.8-rc2 next-20160817] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Johannes-Thumshirn/Fix-panic-when

[PATCH v4 2/3] ses: use scsi_is_sas_rphy instead of is_sas_attached

Use scsi_is_sas_rphy() instead of is_sas_attached() to decide whether we should obtain the SAS address from a scsi device or not. This will prevent us from tripping on the BUG_ON() in sas_sdev_to_rdev() if the rphy isn't attached to the SAS transport class, like it is with hpsa's logical devices.

[PATCH v4 3/3] sas: remove is_sas_attached()

As there are no more users of is_sas_attached() left, remove it. Signed-off-by: Johannes Thumshirn --- drivers/scsi/scsi_transport_sas.c | 16 include/scsi/scsi_transport_sas.h | 6 -- 2 files changed, 22 deletions(-) diff --git

[PATCH v4 0/3] Fix panic when a SES device is attached to a hpsa logical volume.

The first patch provides stub implementations for scsi_is_sas_phy() and sas_get_address() for the case that CONFIG_SCSI_SAS_ATTRS is not defined. The second patch implements the actual fix in ses.c by changing the is_sas_attached() call to scsi_is_sas_rphy(). The third and last patch removes

[PATCH v4 1/3] sas: provide stub implementation for scsi_is_sas_rphy

Provide a stub implementation for scsi_is_sas_rphy for kernel configurations which do not have CONFIG_SCSI_SAS_ATTRS defined. Reported-by: kbuild test robot Suggested-by: James Bottomley Signed-off-by: Johannes Thumshirn ---

Re: [PATCH v3 1/3] sas: provide stub implementation for scsi_is_sas_rphy

Hi Johannes, [auto build test ERROR on scsi/for-next] [also build test ERROR on v4.8-rc2 next-20160817] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Johannes-Thumshirn/Fix-panic-when-a-SES

[PATCH v3 1/3] sas: provide stub implementation for scsi_is_sas_rphy

Provide a stub implementation for scsi_is_sas_rphy for kernel configurations which do not have CONFIG_SCSI_SAS_ATTRS defined. Reported-by: kbuild test robot Suggested-by: James Bottomley Signed-off-by: Johannes Thumshirn ---

[PATCH v3 2/3] ses: use scsi_is_sas_rphy instead of is_sas_attached

Use scsi_is_sas_rphy() instead of is_sas_attached() to decide whether we should obtain the SAS address from a scsi device or not. This will prevent us from tripping on the BUG_ON() in sas_sdev_to_rdev() if the rphy isn't attached to the SAS transport class, like it is with hpsa's logical devices.

[PATCH v3 3/3] sas: remove is_sas_attached()

As there are no more users of is_sas_attached() left, remove it. Signed-off-by: Johannes Thumshirn --- drivers/scsi/scsi_transport_sas.c | 16 include/scsi/scsi_transport_sas.h | 6 -- 2 files changed, 22 deletions(-) diff --git

[PATCH v3 0/3] Fix panic when a SES device is attached to a hpsa logical volume.

The first patch provides stub implementations for scsi_is_sas_phy() and sas_get_address() for the case that CONFIG_SCSI_SAS_ATTRS is not defined. The second patch implements the actual fix in ses.c by changing the is_sas_attached() call to scsi_is_sas_rphy(). The third and last patch removes