If you have nvme configure, but do NOT have ``ld* at nvme?'' you
get an error message with something missing:
...
[ 7.616966] nvme0: for io queue 6 interrupting at msix6 vec 6 affinity to
cpu5
[ 7.616966] nvme0: for io queue 7 interrupting at msix6 vec 7 affinity to
cpu6
[ 7.616966] at nvme0 nsid 1 not configured
...
Note that the "not configured" message doesn't say what is not
configured!
Sidebar: It might seem "pointless" to configure the nvme device but not
configure any ld children. But it actually makes sense when both device
drivers are loaded as modules. When the ld module is eventually loaded,
it correctly displays the attach message:
[ 7.636966] ld0 at nvme0 nsid 1
:)
+--------------------+--------------------------+-----------------------+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org |
+--------------------+--------------------------+-----------------------+
