From: John Garry <john.garry@huawei.com>
To: <Ajish.Koshy@microchip.com>, <jinpu.wang@ionos.com>,
<Viswas.G@microchip.com>
Cc: <linux-scsi@vger.kernel.org>, <vishakhavc@google.com>,
<ipylypiv@google.com>, <Ruksar.devadi@microchip.com>,
<damien.lemoal@opensource.wdc.com>,
<Vasanthalakshmi.Tharmarajan@microchip.com>
Subject: Re: [issue report] pm8001 issues (was driver crashes with IOMMU enabled)
Date: Thu, 13 Jan 2022 14:17:53 +0000 [thread overview]
Message-ID: <05bec388-946d-057d-20d7-67ebe5f2cfdf@huawei.com> (raw)
In-Reply-To: <PH0PR11MB5112E3E9787F20EDEB58D481EC539@PH0PR11MB5112.namprd11.prod.outlook.com>
On 13/01/2022 12:52, Ajish.Koshy@microchip.com wrote:
Hi Ajish,
>> From an earlier mail [0] I got the impression that you tested on an arm
>> platform – did you?
> Yes, with respect to my previous mail update, at that time got the chance to
> load the driver on ARM server/enclosure connected in one of our tester's
> arm server after attaching the controller card.
> There this error handling issue was observed.
>
> The card/driver was never tested or validated on ARM server before,
> was curious to see the behavior for the first time. Whereas driver
> loads smoothly on x86 server.
>
> Currently busy with some other issues, debugging on ARM server is not
> planned for now.
>
OK, since you do see this same/similar issue with another card on arm
then I think that it is safe to assume that it is a driver issue.
If you can share the dmesg on the arm machine then at least that would
be helpful.
Thanks,
John
next prev parent reply other threads:[~2022-01-13 14:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 12:28 [issue report] pm8001 driver crashes with IOMMU enabled John Garry
2021-11-24 12:43 ` Jinpu Wang
2021-11-24 16:22 ` John Garry
2021-12-24 9:02 ` [issue report] pm8001 issues (was driver crashes with IOMMU enabled) John Garry
2021-12-24 11:58 ` John Garry
2021-12-27 13:26 ` Ajish.Koshy
2022-01-06 15:49 ` John Garry
2022-01-07 11:12 ` Ajish.Koshy
2022-01-10 20:21 ` John Garry
2022-01-11 12:40 ` Ajish.Koshy
2022-01-11 13:23 ` John Garry
2022-01-13 12:52 ` Ajish.Koshy
2022-01-13 14:17 ` John Garry [this message]
2022-01-14 18:21 ` John Garry
2022-01-17 13:56 ` Ajish.Koshy
2022-01-17 14:02 ` Ajish.Koshy
2022-01-18 15:49 ` John Garry
2022-01-19 13:49 ` Ajish.Koshy
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=05bec388-946d-057d-20d7-67ebe5f2cfdf@huawei.com \
--to=john.garry@huawei.com \
--cc=Ajish.Koshy@microchip.com \
--cc=Ruksar.devadi@microchip.com \
--cc=Vasanthalakshmi.Tharmarajan@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=ipylypiv@google.com \
--cc=jinpu.wang@ionos.com \
--cc=linux-scsi@vger.kernel.org \
--cc=vishakhavc@google.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;
as well as URLs for NNTP newsgroup(s).