Date: Sat, 21 Aug 2021 15:06:11 -0600 From: Pavel Timofeev <timp87@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: Chuck Tuffli <ctuffli@gmail.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: Dell Latitude 7400 - nvme0: Missing interrupt Message-ID: <CAAoTqfvzxLHF_KGLQQBQmR8cVHPb5RP36Nn7zd0-wJ=DEJNYVQ@mail.gmail.com> In-Reply-To: <CANCZdfocFNXSzax6E=Rhku4iQSu-MGLv7YBifppKcgCnV8eTbw@mail.gmail.com> References: <CAAoTqftwbxBbf96surAWrwqKLDrHAePQnbv_wksPGbKPXedsyw@mail.gmail.com> <CAKAYmM%2B9asxahYJpJB5R%2Byn-Eosmw3xsdOFBTMeyAyDvFkOB1Q@mail.gmail.com> <CAAoTqfuxDCG%2B8agV81NpLdPKJdBOBz0X-FYiApFibx2bjf9Zgg@mail.gmail.com> <CAAoTqfsfvGyhFduoQ3U%2B-Pdcwpp1OVk3aWpDc1Y=WYtgG_a_tA@mail.gmail.com> <CANCZdfocFNXSzax6E=Rhku4iQSu-MGLv7YBifppKcgCnV8eTbw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000003a69405ca18282f Content-Type: text/plain; charset="UTF-8" Warner Losh <imp@bsdimp.com>: > > > On Fri, Aug 20, 2021 at 10:42 PM Pavel Timofeev <timp87@gmail.com> wrote: > >> Pavel Timofeev <timp87@gmail.com>: >> >> > >> > Chuck Tuffli <ctuffli@gmail.com>: >> > >> >> On Mon, Aug 16, 2021 at 7:43 PM Pavel Timofeev <timp87@gmail.com> >> wrote: >> >> > >> >> > Hello >> >> > I've got a Dell Latitude 7400 and tried installing the latest >> >> 14.0-CURRENT >> >> > (main-n248636-d20e9e02db3) on it. >> >> > Despite other things the weird one which concerns me is >> >> > nvme0: Missing interrupt >> >> > message I get sometimes on the console. >> >> > It seems like I get it only after the reboot of the laptop, i. e. not >> >> > getting that message if I power cycle the laptop, at least I haven't >> >> seen >> >> > them for now in such cases. >> >> > So when the laptop is rebooted I can't even take advantage of >> >> > nvmecontrol(8) quickly. >> >> > Well, it still works, but it takes tens of seconds to return the >> output. >> >> ... >> >> > dmesg when power cycled - >> >> > https://drive.google.com/file/d/1dB27oB1O2CcnZy6DvOOhmFO8SN8V8SwJ >> >> > dmesg when rebooted - >> >> > https://drive.google.com/file/d/1DsKTMkihp_OmUcirByLaVO4o2mU38Bxh >> >> >> >> I'm sort of curious about the time stamps for the log messages in the >> >> failing case. Something like: >> >> >> >> $ grep "nv\(me\|d\)" /var/log/messages >> >> >> >> --chuck >> >> >> > >> > Well, I can't see timestamps in the verbose boot log. Am I missing some >> > configuration for that? >> > >> > $ grep "nv\(me\|d\)" /var/log/messages >> > nvme0: <Generic NVMe Device> mem >> > 0xcc100000-0xcc103fff,0xcc105000-0xcc105fff,0xcc104000-0xcc104fff at >> device >> > 0.0 on pci6 >> > nvme0: attempting to allocate 5 MSI-X vectors (17 supported) >> > nvme0: using IRQs 133-137 for MSI-X >> > nvme0: CapLo: 0x140103ff: MQES 1023, CQR, TO 20 >> > nvme0: CapHi: 0x00000030: DSTRD 0, NSSRS, CSS 1, MPSMIN 0, MPSMAX 0 >> > nvme0: Version: 0x00010300: 1.3 >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvme0: Missing interrupt >> > nvd0: <PC611 NVMe SK hynix 512GB> NVMe namespace >> > GEOM: new disk nvd0 >> > nvd0: 488386MB (1000215216 512 byte sectors) >> > >> >> >> Ah, sorry, provided wrong output. >> Here is what you requested: >> $ grep "nv\(me\|d\)" /var/log/messages >> Aug 21 04:34:36 nostromo kernel: nvme0: <Generic NVMe Device> mem >> 0xcc100000-0xcc103fff,0xcc105000-0xcc105fff,0xcc104000-0xcc104fff at >> device >> 0.0 on pci6 >> Aug 21 04:34:36 nostromo kernel: nvme0: attempting to allocate 5 MSI-X >> vectors (17 supported) >> Aug 21 04:34:36 nostromo kernel: nvme0: using IRQs 133-137 for MSI-X >> Aug 21 04:34:36 nostromo kernel: nvme0: CapLo: 0x140103ff: MQES 1023, CQR, >> TO 20 >> Aug 21 04:34:36 nostromo kernel: nvme0: CapHi: 0x00000030: DSTRD 0, NSSRS, >> CSS 1, MPSMIN 0, MPSMAX 0 >> Aug 21 04:34:36 nostromo kernel: nvme0: Version: 0x00010300: 1.3 >> Aug 21 04:34:36 nostromo kernel: nvme0: Missing interrupt >> Aug 21 04:34:36 nostromo kernel: nvme0: Missing interrupt >> Aug 21 04:34:36 nostromo kernel: nvme0: Missing interrupt >> Aug 21 04:34:36 nostromo kernel: nvd0: <PC611 NVMe SK hynix 512GB> NVMe >> namespace >> Aug 21 04:34:36 nostromo kernel: GEOM: new disk nvd0 >> Aug 21 04:34:36 nostromo kernel: nvd0: 488386MB (1000215216 512 byte >> sectors) >> Aug 21 04:34:42 nostromo kernel: nvme0: Missing interrupt >> Aug 21 04:35:36 nostromo kernel: nvme0: Missing interrupt >> Aug 21 04:35:50 nostromo kernel: nvme0: Missing interrupt >> > > What happens if you set hw.nvme.use_nvd=0 and hw.cam.nda.nvd_compat=1 > in the boot loader and reboot? Same thing except nda where nvd was? Or does > it work? > > Something weird is going on in the interrupt assignment, I think, but I > wanted to get any nvd vs nda issues out of the way first. > > Warner > Do you mean kern.cam.nda.nvd_compat instead of hw.cam.nda.nvd_compat? kern.cam.nda.nvd_compat is 1 by default now. So I tried to set hw.nvme.use_nvd to 1 as suggested, but I still see nvme0: Missing interrupt and now also Root mount waiting for: CAM messages besides those --00000000000003a69405ca18282f--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAoTqfvzxLHF_KGLQQBQmR8cVHPb5RP36Nn7zd0-wJ=DEJNYVQ>