From: Ching Huang ching2...@areca.com.tw
This patch rewrite the interrupt service routine relate function to fix command
timeout when controller has very heavy loading.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr.h
From: Ching Huang ching2...@areca.com.tw
This patch adds code to support MSI, MSI-X interrupt.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr.h b/drivers/scsi/arcmsr/arcmsr.h
--- a/drivers/scsi/arcmsr/arcmsr.h 2014-04-28 16:02:46.0
From: Ching Huang ching2...@areca.com.tw
This patch adds code to support system hibernation.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
--- a/drivers/scsi/arcmsr/arcmsr_hba.c 2014-08-01
From: Ching Huang ching2...@areca.com.tw
This patch limits the max. number of SCSI commmand request to avoid command
overflow.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr.h b/drivers/scsi/arcmsr/arcmsr.h
--- a/drivers/scsi/arcmsr/arcmsr.h
Hi Greg,
Any feedback on this patch ?
Regards
Sanjeev Sharma
-Original Message-
From: Sharma, Sanjeev
Sent: Tuesday, August 12, 2014 12:07 PM
To: 'Hans de Goede'
Cc: gre...@linuxfoundation.org; kra...@redhat.com;
mdharm-...@one-eyed-alien.net; linux-...@vger.kernel.org;
The value of the csr-mask of the SATA PHY clock DTS node has a
wrong value resulting a kernel panic as the clock/reset is not
proper for the PHY of the SATA host controller 1. This patch
fixes the correct csr-mask value of the SATA PHY clock DTS node
for the SATA Host controller 1.
As the 'ok' is
The link down issue in first attempt happens due to 2 H/W errata below:
1. Due to HW errata, during speed negotiation, sometimes controller
is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in
a timeout. This issue can be recovered by issuing a COMRESET again.
2. Due to HW errata,
This patch set contains a couple of fixes related to APM X-Gene SATA
controller driver.
v2 Change:
1. Drop the Link down retry patch from this patch set.
v4 Change:
1. Drop the patch to fix the csr-mask in dts for PHY clock
node of SATA Host Controller 1.
2. Add the patch to
This patch implements the feature to skip the PHY and clock
initialization if it is already configured by the firmware.
Signed-off-by: Loc Ho l...@apm.com
Signed-off-by: Suman Tripathi stripa...@apm.com
---
drivers/ata/ahci_xgene.c | 17 +
1 file changed, 17 insertions(+)
diff
Please ignore the patch [PATCH v4 4/17], I will resend the patch [PATCH v3
4/17].
Regards,
Ching Huang ching2...@areca.com.tw
--
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
From: Ching Huang ching2...@areca.com.tw
This patch limits the max. number of SCSI command request to avoid command
overflow.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr.h b/drivers/scsi/arcmsr/arcmsr.h
--- a/drivers/scsi/arcmsr/arcmsr.h
From: Ching Huang ching2...@areca.com.tw
This patch fixed the wrong return status of abort command.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
--- a/drivers/scsi/arcmsr/arcmsr_hba.c 2014-08-08
From: Ching Huang ching2...@areca.com.tw
change since v2:
1. This patch pre-define the adapter-type in private data of struct
pci_device_id.
2. Remove arcmsr_define_adapter_type function.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c
From: Ching Huang ching2...@areca.com.tw
Revise message_isr_bh_fn to remove the duplicate code for each adapter type.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
--- a/drivers/scsi/arcmsr/arcmsr_hba.c
From: Ching Huang ching2...@areca.com.tw
Remove calling arcmsr_hbb_enable_driver_mode by in-line code.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
--- a/drivers/scsi/arcmsr/arcmsr_hba.c 2014-08-14
From: Ching Huang ching2...@areca.com.tw
Adjust printing order of adapter model name and firmware version.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
--- a/drivers/scsi/arcmsr/arcmsr_hba.c 2014-08-14
From: Ching Huang ching2...@areca.com.tw
Clear outbound doorbell buffer completely for adapter type C.
This is to prevent getting bad data input from IOP before ioctl command
beginning.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c
From: Ching Huang ching2...@areca.com.tw
Rename some variable and function name for readability and consistency.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr.h b/drivers/scsi/arcmsr/arcmsr.h
--- a/drivers/scsi/arcmsr/arcmsr.h 2014-05-06
From: Ching Huang ching2...@areca.com.tw
This modification is for consistency with upcoming adapter type D.
Both adapter type B and D have similar H/W and S/W structure.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr.h
From: Ching Huang ching2...@areca.com.tw
Fix sparse utility checking error and warning.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
--- a/drivers/scsi/arcmsr/arcmsr_hba.c 2014-08-14 18:40:48.0
From: Ching Huang ching2...@areca.com.tw
Revise comment and some character strings.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
--- a/drivers/scsi/arcmsr/arcmsr_hba.c 2014-08-14 18:41:02.0 +0800
From: Ching Huang ching2...@areca.com.tw
Add code for supporting Areca new Raid adapter ARC12x4 series.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr.h b/drivers/scsi/arcmsr/arcmsr.h
--- a/drivers/scsi/arcmsr/arcmsr.h 2014-05-06
From: Ching Huang ching2...@areca.com.tw
Modify calling scsi_scan_host until all initialization done.
And fix error path of free allocation resource.
Signed-off-by: Ching Huang ching2...@areca.com.tw
---
diff -uprN a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
---
On Tue, Aug 19, 2014 at 06:33:04AM +, Sharma, Sanjeev wrote:
Hi Greg,
Any feedback on this patch ?
The merge window ended 2 days ago, _and_ I'm at the kernel summit this
week, _and_ my queue is currently sitting at:
$ mdfrm -c ~/mail/todo/
1317 messages in
Thanks for letting me know.
Sanjeev Sharma
-Original Message-
From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
Sent: Tuesday, August 19, 2014 3:01 PM
To: Sharma, Sanjeev
Cc: kra...@redhat.com; mdharm-...@one-eyed-alien.net;
linux-...@vger.kernel.org;
3.16 scsi worked fine, 3.17-rc1 misbehaves on 3 of my sparc64 test
machines. E220R and E420R are with onboard 5c3875, V210 is with onboarc
53c1010 and all behave the same. Any ideas whre to dig deeper? bisection
might be nontrivial, because of sparc64 changes that are OK on 3.17-rc1
again -
On Tue, 2014-08-19 at 14:25 +0300, Meelis Roos wrote:
3.16 scsi worked fine, 3.17-rc1 misbehaves on 3 of my sparc64 test
machines. E220R and E420R are with onboard 5c3875, V210 is with onboarc
53c1010 and all behave the same. Any ideas whre to dig deeper? bisection
might be nontrivial,
3.16 scsi worked fine, 3.17-rc1 misbehaves on 3 of my sparc64 test
machines. E220R and E420R are with onboard 5c3875, V210 is with onboarc
53c1010 and all behave the same. Any ideas whre to dig deeper? bisection
might be nontrivial, because of sparc64 changes that are OK on 3.17-rc1
On Tue, 2014-08-19 at 14:25 +0300, Meelis Roos wrote:
3.16 scsi worked fine, 3.17-rc1 misbehaves on 3 of my sparc64 test
machines. E220R and E420R are with onboard 5c3875, V210 is with onboarc
53c1010 and all behave the same. Any ideas whre to dig deeper? bisection
might be nontrivial,
On Tue, 2014-08-19 at 17:37 +0300, Meelis Roos wrote:
On Tue, 2014-08-19 at 14:25 +0300, Meelis Roos wrote:
3.16 scsi worked fine, 3.17-rc1 misbehaves on 3 of my sparc64 test
machines. E220R and E420R are with onboard 5c3875, V210 is with onboarc
53c1010 and all behave the same. Any
Hi Ching,
I've fixed up various checkpatch errors and fixed up some descriptions
and applied the patches to a branch. This includes patch 4, so please
send a fix for this and any other patches relative to the branch.
Please find the branch at
Is it permitted for a LLD to call scsi_done() for a command which
has been or is attempting to be aborted via the LLD abort error handler
function?
I am looking at the scsi mid layer code, and I'm a bit confused.
There seem to be a few ways the LLD abort handler function can
get called.
One
On Tue, Aug 19, 2014 at 12:01:51PM +0530, Suman Tripathi wrote:
The link down issue in first attempt happens due to 2 H/W errata below:
1. Due to HW errata, during speed negotiation, sometimes controller
is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in
a timeout. This
On Tue, Aug 19, 2014 at 3:51 AM, Kashyap Desai
kashyap.de...@avagotech.com wrote:
-Original Message-
From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi-
ow...@vger.kernel.org] On Behalf Of Christoph Hellwig
Sent: Friday, July 18, 2014 3:43 PM
To: James Bottomley;
On Tue, Aug 19, 2014 at 03:51:42AM +0530, Kashyap Desai wrote:
I read this comment and find that very few drivers are using this
cmd_list. I think if we remove this cmd_list, performance will scale as I
am seeing major contention in this lock.
Just thought to ping you to see if this is known
On Tue, Aug 19, 2014 at 9:36 PM, Christoph Hellwig h...@lst.de wrote:
On Tue, Aug 19, 2014 at 03:51:42AM +0530, Kashyap Desai wrote:
I read this comment and find that very few drivers are using this
cmd_list. I think if we remove this cmd_list, performance will scale as I
am seeing major
On Tue, Jul 01, 2014 at 02:56:20PM +0200, Rasmus Villemoes wrote:
Rounding up to a multiple of 4 should be done using the ALIGN
macro. As a bonus, this also makes the generated code smaller.
In GetIocFacts(), sz is assigned to a few lines below without being
read in the meantime, so it is ok
Thanks,
I've applied patches 1 to 7 to the drivers-for-3.18 branch.
--
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
On Tue, 2014-08-19 at 10:30 -0500, scame...@beardog.cce.hp.com wrote:
Is it permitted for a LLD to call scsi_done() for a command which
has been or is attempting to be aborted via the LLD abort error handler
function?
I am looking at the scsi mid layer code, and I'm a bit confused.
Hannes
Thanks,
applied to the drivers-for-3.18 branch.
--
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
Thanks,
applied to the drivers-for-3.18 branch.
--
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
Thanks,
applied to the drivers-for-3.18 tree.
--
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
Thanks,
applied the whole series to the drivers-for-3.18 tree.
--
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
Thanks, I've applied both docbook fixups to the drivers-for-3.18 and
also addressed the addition nitpicks from Ewan.
--
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
This looks reasonable to me. Martin, and objections?
On Mon, Aug 11, 2014 at 03:40:37PM +0300, Dolev Raviv wrote:
From: Sujit Reddy Thumma sthu...@codeaurora.org
The SYNCHRONIZE_CACHE command is a medium write command and hence can
fail when the device is write protected. Avoid sending such
James, can you please send this on ASAP? Sitting for oever a week
on a boot regression that comes with a patch isn't reasonable.
On Sun, Aug 10, 2014 at 05:54:25AM -0700, Guenter Roeck wrote:
The latest kernel fails to boot qemu arm images when using scsi
for disk access. Boot gets stuck after
On Sat, Aug 16, 2014 at 08:09:48PM -0700, K. Y. Srinivasan wrote:
The host asks the guest to scan when a LUN is removed or added.
The only way a guest can identify the removed LUN is when an I/O is
attempted on a removed LUN - the SRB status code indicates that the LUN
is invalid. We currently
On Mon, Aug 11, 2014 at 5:40 AM, Dolev Raviv dra...@codeaurora.org wrote:
From: Sujit Reddy Thumma sthu...@codeaurora.org
The SYNCHRONIZE_CACHE command is a medium write command and hence can
fail when the device is write protected. Avoid sending such commands by
making sure that
On Thu, Aug 07, 2014 at 11:58:37AM -0400, Alan Stern wrote:
On Wed, Aug 06, 2014 at 04:02:22PM -0400, Alan Stern wrote:
I doubt either of them forces users to hack up flags for these cases.
Why was this change needed in the first place? There's no explanation
in the patch itself.
Thanks,
I've applied all three patches to the driver-for-3.18 branch.
--
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
On Tue, Aug 19, 2014 at 12:16:12PM -0500, James Bottomley wrote:
On Tue, 2014-08-19 at 10:30 -0500, scame...@beardog.cce.hp.com wrote:
Is it permitted for a LLD to call scsi_done() for a command which
has been or is attempting to be aborted via the LLD abort error handler
function?
On Tue, Aug 05, 2014 at 07:47:12PM +, Handzik, Joe wrote:
Yeah, we thought about that one. We call scsi_activate_tcq if our scsi_device
has tagged_supported set within hpsa_change_queue_type (our
.change_queue_type entry into the scsi_host_template). Also made sure I was
booting with
On Tue, Aug 05, 2014 at 04:10:08PM +0300, Ari Sundholm wrote:
On Mon, 4 Aug 2014, Christoph Hellwig wrote:
To modify the timeout on a queue please use blk_queue_rq_timeout in
the slave_configure method instead of poking directly into the block
timer, which won't work e.g. for the blk-mq
Add enable_cmd_list flag in shost template to indicate scs.mq stack
to keep track of cmd_list per sdev.
Default behaviour is not to keep track of cmd_list per sdev, as this may
introduce
lock contention. (overhead is more on multi-node NUMA.)
Patch is tested using megaraid_sas driver with
These are the two bug fixes I mentioned in the final merge window pull.
One is a reversed logic check in the device busy tests which can cause a
nasty hang and another crash seen in the new SCSI pool support if the
use count ever goes to zero.
The patch is available here:
Hi,
On Tue, Aug 19, 2014 at 09:47:35AM -0500, James Bottomley wrote:
On Tue, 2014-08-19 at 17:37 +0300, Meelis Roos wrote:
On Tue, 2014-08-19 at 14:25 +0300, Meelis Roos wrote:
3.16 scsi worked fine, 3.17-rc1 misbehaves on 3 of my sparc64 test
machines. E220R and E420R are with
On Tue, Aug 19, 2014 at 11:17:48PM +0300, Aaro Koskinen wrote:
Hi,
On Tue, Aug 19, 2014 at 09:47:35AM -0500, James Bottomley wrote:
On Tue, 2014-08-19 at 17:37 +0300, Meelis Roos wrote:
On Tue, 2014-08-19 at 14:25 +0300, Meelis Roos wrote:
3.16 scsi worked fine, 3.17-rc1 misbehaves
On Tue, 2014-08-19 at 23:17 +0300, Aaro Koskinen wrote:
Hi,
On Tue, Aug 19, 2014 at 09:47:35AM -0500, James Bottomley wrote:
On Tue, 2014-08-19 at 17:37 +0300, Meelis Roos wrote:
On Tue, 2014-08-19 at 14:25 +0300, Meelis Roos wrote:
3.16 scsi worked fine, 3.17-rc1 misbehaves on 3 of
Hi,
On Tue, Aug 19, 2014 at 03:37:18PM -0500, James Bottomley wrote:
On Tue, 2014-08-19 at 23:17 +0300, Aaro Koskinen wrote:
Bisection (on PA-RISC) points to:
71e75c97f97a9645d25fbf3d8e4165a558f18747 is the first bad commit
commit 71e75c97f97a9645d25fbf3d8e4165a558f18747
Author:
59 matches
Mail list logo
