[Bug 274974] nvme: resetting controller after mounting a partition

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 08 Nov 2023 22:26:03 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274974

Warner Losh <imp@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |imp@FreeBSD.org

--- Comment #1 from Warner Losh <imp@FreeBSD.org> ---
So, the unknown statis is my fault: Forgot to add something to a table. Ignore
that.

But second, this error message happens when we post a transaction to the card,
and then we don't get an interrupt and we timeout. When we timeout, we go look
at the status registers for the card and find that the card is gone (reads as
0xffffffff) (that's the possible hotplug part). With the card reading that,
there's no hope: it's game over.

So the question is presumably it wasn't like that when we booted the system. It
had to have read these registers, and a lot of others to boot, to find the
card, then later we've had to do I/Os to the card when CAM starts up to get the
card to attach (though these are trivial, they'd freak out if they read back
all ff's). So what happened between probe time and now to get it into this
state? Did a bridge go away, get renumbered, move its memory windows? Was
something else mapped in conflict so the fight over the decoding results in
ff's? Why didn't the interrupt happen so we got into the timeout path?

-- 
You are receiving this mail because:
You are the assignee for the bug.