From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Rob Herring" <robh@kernel.org>, "Pali Rohár" <pali@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Marek Behún" <kabel@kernel.org>, Xogium <contact@xogium.me>,
linux-pci@vger.kernel.org, "Remi Pommarel" <repk@triplefau.lt>,
"Tomasz Maciej Nowak" <tmn505@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] PCI: aardvark: Fix kernel panic during PIO transfer
Date: Thu, 17 Jun 2021 15:15:23 -0500 [thread overview]
Message-ID: <20210617201523.GA3104553@bjorn-Precision-5520> (raw)
In-Reply-To: <162322862108.3345.4160808336030929680.b4-ty@arm.com>
On Wed, Jun 09, 2021 at 09:50:39AM +0100, Lorenzo Pieralisi wrote:
> On Tue, 8 Jun 2021 22:36:55 +0200, Pali Rohár wrote:
> > Trying to start a new PIO transfer by writing value 0 in PIO_START register
> > when previous transfer has not yet completed (which is indicated by value 1
> > in PIO_START) causes an External Abort on CPU, which results in kernel
> > panic:
> >
> > SError Interrupt on CPU0, code 0xbf000002 -- SError
> > Kernel panic - not syncing: Asynchronous SError Interrupt
> >
> > [...]
>
> Applied to pci/aardvark, thanks!
>
> [1/1] PCI: aardvark: Fix kernel panic during PIO transfer
> https://git.kernel.org/lpieralisi/pci/c/f77378171b
Since this fixes a panic and only affects aardvark, I cherry picked
this to my for-linus branch.
Can you drop it, Lorenzo? It's currently the only thing on your
pci/aardvark branch, so I just dropped that whole branch from -next.
Bjorn
next prev parent reply other threads:[~2021-06-17 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 20:36 [RESEND PATCH] PCI: aardvark: Fix kernel panic during PIO transfer Pali Rohár
2021-06-09 8:50 ` Lorenzo Pieralisi
2021-06-17 20:15 ` Bjorn Helgaas [this message]
2021-06-21 9:47 ` Lorenzo Pieralisi
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=20210617201523.GA3104553@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=contact@xogium.me \
--cc=kabel@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pali@kernel.org \
--cc=repk@triplefau.lt \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tmn505@gmail.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