[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
kern/54275: nvme_poll() called too early?
>Synopsis: nvme_poll() called too early?
>Arrival-Date: Wed Jun 05 23:10:00 +0000 2019
>Originator: Thomas Klausner
>Release: NetBSD 8.99.41
Curiosity is the very basis of education and if you tell me that
curiosity killed the cat, I say only that the cat died nobly.
- Arnold Edinborough
Booting the amd64 USB install image from
on a new Threadripper system with a Samsung SSD 1TB 970 Evo plus, I
panic: prevented jump to null instruction pointer (SMEP)
cpu0: Begin traceback...
vpanic() at netbsd:vpanic+0x160
snprintf() at netbsd:snprintf
trap() at netbsd:trap+0x2ab
--- trap (number 6) ---
?() at 0
nvme_poll() at netbsd:nvme_poll+0x104
nvme_attach() at netbsd:nvme_atached+0x927
nvme_pci_attach() at netbsd_nvme_pci_attach+0x309
cpu0: End traceback
Disabling nvme with "userconf disable nvme*" makes the kernel boot successfully.
OpenBSD 6.5 and FreeBSD 12.0 boot successfully on the same system, including
the nvme device.
dmesg output for the nvme device (on NetBSD):
nvme0 at pci0 dev 0 function 0: vendor 144d product a808 (rev. 0x00) (not sure if it's 808 or 000 or something inbetween, bad screenshot)
nvme0: NVMe 1.3
nvme0: for admin queue interrupting at msix3 vec 0
nvme0: for io queue ... interrupting at msix3 vec ... affinity to cpu ... (where ... goes from 0 to 31)
Boot on the system with nvme enabled (default on).
Main Index |
Thread Index |