From: Klaus Jensen <its@irrelevant.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: regression on aarch64? panic on boot
Date: Tue, 17 Jan 2023 07:31:59 +0100 [thread overview]
Message-ID: <Y8ZA30EoAFaFPwVC@cormorant.local> (raw)
In-Reply-To: <20230117055819.GB13795@lst.de>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
On Jan 17 06:58, Christoph Hellwig wrote:
> On Mon, Jan 16, 2023 at 10:57:11PM +0100, Klaus Jensen wrote:
> > Hi,
> >
> > I'm getting panics when booting from a QEMU hw/nvme device on an aarch64
> > guest in roughly 20% of boots on v6.2-rc4. Example panic below.
>
> This smells like your setup somehow doesn't wait for async driver
> probe. Does the hack below work around it?
>
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index b13baccedb4a95..f47e19c701d520 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -3508,7 +3508,6 @@ static struct pci_driver nvme_driver = {
> .remove = nvme_remove,
> .shutdown = nvme_shutdown,
> .driver = {
> - .probe_type = PROBE_PREFER_ASYNCHRONOUS,
> #ifdef CONFIG_PM_SLEEP
> .pm = &nvme_dev_pm_ops,
> #endif
Good morning Christoph,
Yep, the above works.
My setup is a buildroot qemu_aarch64_virt_defconfig booting from an
emulated nvme device:
qemu-system-aarch64 -M "virt" -cpu "cortex-a53" -m 512M \
-nodefaults -nographic -snapshot -no-reboot \
-kernel images/Image \
-append "root=/dev/nvme0n1 console=ttyAMA0,115200" \
-drive file=images/rootfs.ext2,format=raw,if=none,id=d0 \
-device nvme,serial=default,drive=d0 \
-nic user,model=virtio \
-serial stdio
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-01-17 6:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 21:57 regression on aarch64? panic on boot Klaus Jensen
2023-01-17 5:58 ` Christoph Hellwig
2023-01-17 6:31 ` Klaus Jensen [this message]
2023-01-17 6:37 ` Christoph Hellwig
2023-01-17 6:39 ` Klaus Jensen
2023-01-17 12:11 ` Martin Wilck
2023-01-19 8:29 ` Klaus Jensen
2023-01-19 16:48 ` Keith Busch
2023-01-24 17:11 ` Ville Syrjälä
2023-01-19 13:10 ` Linux kernel regression tracking (#adding)
2023-01-27 11:11 ` Linux kernel regression tracking (#update)
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=Y8ZA30EoAFaFPwVC@cormorant.local \
--to=its@irrelevant.dk \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.