From: John Garry <john.garry@huawei.com>
To: <Ajish.Koshy@microchip.com>
Cc: <jinpu.wang@cloud.ionos.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <Viswas.G@microchip.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<damien.lemoal@opensource.wdc.com>, <Niklas.Cassel@wdc.com>,
<Vasanthalakshmi.Tharmarajan@microchip.com>
Subject: Re: [PATCH] scsi: pm8001: Fix phys_to_virt() usage on dma_addr_t
Date: Thu, 9 Dec 2021 12:19:40 +0000 [thread overview]
Message-ID: <f41d2bed-f320-1b70-7d63-fe77caa2534d@huawei.com> (raw)
In-Reply-To: <PH0PR11MB51120361EB6F6931CCE023D6EC709@PH0PR11MB5112.namprd11.prod.outlook.com>
On 09/12/2021 12:04, Ajish.Koshy@microchip.com wrote:
> Was testing the patch on arm server. Didn't see crash there but observing timeouts and error
> handling getting triggered for drives. But the same code works fine on x86.
>
> At your end do you still face similar situation on arm server ?
Yeah, I see that as well even without enabling the IOMMU.
root@(none)$ [ 163.974907] sas: Enter sas_scsi_recover_host busy: 222
failed: 222
[ 163.981108] sas: sas_scsi_find_task: aborting task 0x000000005c703676
root@(none)$
root@(none)$ [ 185.963714] pm80xx0:: pm8001_exec_internal_tmf_task
757:TMF task[1]timeout.
I figured that it was a card FW issue as I have been using what I got
out the box, and I have no tool to update the firmware on an arm host.
It seems that SSP and STP commands are not completing for some reason,
from the "busy: 222" line.
next prev parent reply other threads:[~2021-12-09 12:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 15:35 [PATCH] scsi: pm8001: Fix phys_to_virt() usage on dma_addr_t John Garry
2021-11-29 10:46 ` Ajish.Koshy
2021-12-06 9:42 ` John Garry
2021-12-06 13:24 ` Niklas Cassel
2021-12-07 10:36 ` Ajish.Koshy
2021-12-07 13:54 ` John Garry
2021-12-09 12:04 ` Ajish.Koshy
2021-12-09 12:19 ` John Garry [this message]
2021-12-09 22:38 ` Damien Le Moal
2021-12-09 23:09 ` John Garry
2021-12-09 23:55 ` Damien Le Moal
2021-12-10 10:35 ` John Garry
2021-12-11 0:19 ` Damien Le Moal
2021-12-09 22:26 ` Damien Le Moal
2021-12-09 13:46 ` John Garry
2021-12-10 10:23 ` Ajish.Koshy
2021-12-10 10:44 ` John Garry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f41d2bed-f320-1b70-7d63-fe77caa2534d@huawei.com \
--to=john.garry@huawei.com \
--cc=Ajish.Koshy@microchip.com \
--cc=Niklas.Cassel@wdc.com \
--cc=Vasanthalakshmi.Tharmarajan@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox