Re: netbsd-current on Starfive Visionfive2 panics while booting from sd-card if nvme is connected

[Slacker Cruise <slackercruise%gmail.com@localhost>]

Thanks for the response Jeff.
I'm new to the NetBSD ecosystem when it comes to interaction within
teams/mailing lists, so I'm still traversing all the options.
But I can confirm I don't see your response to that PR via email/any
other notification. How do I check the updates on a PR (if not via
email)?
My apologies for the ignorance.

Coming to the actual issue, I see your point regarding the NVMe
version. Unfortunately I don't have a 1.3 with me. Is there any other
data I should be looking at to provide here?

On Mon, Aug 24, 2026 at 7:24 PM Jeff Rizzo <riz%tastylime.net@localhost> wrote:
>
> On 8/24/26 02:24, Slacker Cruise wrote:
>
> > Hello team,
> >
> > I raised this bug report for netbsd-11-rc6 a while ago -
> > https://gnats.netbsd.org/60482
> >
> > Just wanted to update that this is still reproducible on netbsd-current.
> > (I'm sure it's already known to the maintainers and I'm not expecting
> > an immediate solution, just wanted to report to maintainers and even
> > assist in anything as I have this hardware, you guys
> > are doing a great job with NetBSD anyways)
> >
> >
> > [   1.0000000] nvme0 at pci3 dev 0 function 0: vendor 1e4b product 1202
> > (rev. 0x01)
> > [   1.0000000] nvme0: NVMe 1.4
> > [   1.0000000] nvme0: interrupting at plic0 irq 57
> > [   1.0000000] nvme0: CONSISTENT NVME S7 128GB, firmware SN16672, serial
> > HA202512040100801
>
>
> As I'm sure you saw when I responded to the PR the other day, I have an
> nvme which does *not* cause this panic.  I'm sure it doesn't comfort
> you, but it may help diagnose the issue, because there are some
> differences, the biggest one I can see being that mine is NVMe 1.3 vs
> your 1.4:
>
> [   1.0000000] nvme0 at pci1 dev 0 function 0: vendor 144d product a809
> (rev. 0x00)
> [   1.0000000] nvme0: NVMe 1.3
> [   1.0000000] nvme0: interrupting at plic0 irq 57
> [   1.0000000] nvme0: SAMSUNG MZALQ256HAJD-000L1, firmware BL1QFXV7,
> serial S4YDNF1R334402
>
> ...unfortunately, I don't have a 1.4 to test with. (Not that this is my
> area of expertise anyway).  I also noticed that the other reports on
> this list also involve nvme 1.4, for what it's worth.
>
>
> +j
>