[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f41d2bed-f320-1b70-7d63-fe77caa2534d@huawei.com>
Date: Thu, 9 Dec 2021 12:19:40 +0000
From: John Garry <john.garry@...wei.com>
To: <Ajish.Koshy@...rochip.com>
CC: <jinpu.wang@...ud.ionos.com>, <jejb@...ux.ibm.com>,
<martin.petersen@...cle.com>, <Viswas.G@...rochip.com>,
<linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<damien.lemoal@...nsource.wdc.com>, <Niklas.Cassel@....com>,
<Vasanthalakshmi.Tharmarajan@...rochip.com>
Subject: Re: [PATCH] scsi: pm8001: Fix phys_to_virt() usage on dma_addr_t
On 09/12/2021 12:04, Ajish.Koshy@...rochip.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.
Powered by blists - more mailing lists