From: Punit Agrawal <punitagrawal@gmail.com>
To: u-boot@lists.denx.de
Cc: patrick@blueri.se, kever.yang@rock-chips.com,
awilliams@marvell.com, linux-rockchip@lists.infradead.org,
jagan@amarulasolutions.com, bmeng.cn@gmail.com
Subject: NVMe boot issues on RockPro64
Date: Sat, 29 Aug 2020 09:30:24 +0900 [thread overview]
Message-ID: <87a6yepa3j.fsf@tinker> (raw)
Hi,
I get the following errors when booting Linux from an ADATA XPG SX8200
NVMe on a RockPro64.
[ 3.705205] rockchip-pcie f8000000.pcie: unexpected IRQ, INT0
[ 3.705226] rockchip-pcie f8000000.pcie: unexpected IRQ, INT0
[ 3.705247] rockchip-pcie f8000000.pcie: unexpected IRQ, INT0
[ 3.705331] rockchip-pcie f8000000.pcie: unexpected IRQ, INT0
[ 3.705352] rockchip-pcie f8000000.pcie: unexpected IRQ, INT0
[ 3.705373] rockchip-pcie f8000000.pcie: unexpected IRQ, INT0
At which point boot hangs. Has anybody come across these errors when
using NVMe?
Using an alternate device (sd card) to load the kernel / initrd doesn't
cause the issue and the drive works fine when used as a root device in
Linux subsequently.
On digging further, I found that uboot exits with the NVME interrupt
line (PCI legacy interrupt) active when making any access to the
device. Even just running "nvme scan" leads to the active interrupt
line.
After sprinkling some prints in the uboot NVMe driver, it seems that the
interrupt goes active right at the beginning of setting up the IO queues
(nvme_setup_io_queues). This is also the first time the admin queue is
used; when issuing the command to setup the number of queues
(NVME_FEAT_NUM_QUEUES). For some reason, updating the CQ head doorbell
doesn't clear the interrupt.
The active interrupt doesn't bother uboot as it ignores the device
interrupt but causes an issue latter when linux boots.
Has anybody faced similar issues with NVMe and uboot? Any idea on how to
stop the interrupt line from triggering? Or de-activating it on exit?
Let me know if there's anything I can provide to help debug the
problem. Also, happy to try any patches or suggestions.
Thanks,
Punit
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2020-08-29 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 0:30 Punit Agrawal [this message]
2020-08-29 7:03 ` NVMe boot issues on RockPro64 Bin Meng
2020-08-30 0:16 ` Punit Agrawal
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=87a6yepa3j.fsf@tinker \
--to=punitagrawal@gmail.com \
--cc=awilliams@marvell.com \
--cc=bmeng.cn@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=patrick@blueri.se \
--cc=u-boot@lists.denx.de \
/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).