linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Jinpu Wang <jinpu.wang@ionos.com>,
	Viswas G <Viswas.G@microchip.com>,
	Ajish Koshy <Ajish.Koshy@microchip.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"vishakhavc@google.com" <vishakhavc@google.com>,
	<ipylypiv@google.com>, <Ruksar.devadi@microchip.com>
Subject: Re: [issue report] pm8001 issues (was driver crashes with IOMMU enabled)
Date: Fri, 24 Dec 2021 09:02:33 +0000	[thread overview]
Message-ID: <1cc92b2d-3670-7843-d68a-06fe68521d24@huawei.com> (raw)
In-Reply-To: <00505633-c8c0-8213-8909-482bf43661cd@huawei.com>

+ some recent contributors

Hi microchip guys,

Do you have any idea on the 2x outstanding issues I reported for the 
pm8001 driver:
a. my arm system goes into a continuous cycle of SCSI error handling for 
this scsi host
b. maxcpus=1 on commandline crashes during bootup on my arm system - I 
assume that x86 is same also

Thanks,
John

  reply	other threads:[~2021-12-24  9:02 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     ` John Garry [this message]
2021-12-24 11:58       ` [issue report] pm8001 issues (was driver crashes with IOMMU enabled) 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
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=1cc92b2d-3670-7843-d68a-06fe68521d24@huawei.com \
    --to=john.garry@huawei.com \
    --cc=Ajish.Koshy@microchip.com \
    --cc=Ruksar.devadi@microchip.com \
    --cc=Viswas.G@microchip.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).