From nobody Sat Aug 21 21:22:39 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 1A32E1783F30 for ; Sat, 21 Aug 2021 21:22:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GsWgY6qn7z4RkJ for ; Sat, 21 Aug 2021 21:22:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x830.google.com with SMTP id u21so7573026qtw.8 for ; Sat, 21 Aug 2021 14:22:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7PveNwz6FXIaeHSfMuvac3HujALLtxsLWY4b8YkTlhQ=; b=JKPYU/78BgXeLmYXUGdqrxoF0ascvn0x/u0cuMkXq3y2FREci0CnYLFuuQ7jPs7fKT EQOh5kGwZv+P1Q9MuLyISgDe+3jEJYpX9Dh9nOLUoLZHDD2Li2TjkeGLGITKB59o4Z5A L1CmSuZ/KZjG9MxzcHzThX2KO9xIx7PsCuAHJZRvZMsLbZ2oEwF7wQ84qmdQVwjppbZU JvwIG6rk8jm+ZpQC0HGa36Eg7lA6nzF3XWnUsse3Xx2t2SAwlZqvaEfhYogO2iWcGw8s i9YshfMrw/zuDcor6Y9poSz2aF5tjvJ3VSnmsufAqcmCnVTQQp2g3s3hAVj/1QTLDUFc 8huQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7PveNwz6FXIaeHSfMuvac3HujALLtxsLWY4b8YkTlhQ=; b=DdIzPw97Pqe0/OA0pLFFbaXmiRiDX8wKyzUZRuTQtm0F3h/ZWHCjZSdW+xY2rz2rod xu+H+cJ+5bjyNcw1VIPm1v7mer5DR9W3wyCmN+ozb13j3EmrbRhhHzVmvWH+xSuPfc0x ogR1Q4Y592P1Q1psovd04OPciSqEdc68Yeyv65dj3Wqzb8NE6j1GfzgHKWaVNgQTh75M mOOr+FEV8d9Eak/IKB4DjkcbkrsuCIdqRNO4obDi3VJpPmm3acEi4qd/nFsMezgD6IkY R5GgHhdnpwd8JQFDuk1HLJr03zsuFvPshAlki4fXAdaP503Lqise5GvM6l0HOVY80ycA Z9sg== X-Gm-Message-State: AOAM533OWFnmyi78xqxELxulFYLXhVLA+IeayBtLKy6QC1aHYKNdeUCB 6byPJmeG1EgGcIrnJuXIoeu7zetbxq35pqmeijpU6A== X-Google-Smtp-Source: ABdhPJyDwAqKZ3rWXdvUSotdlgrY55MyUo5+9Xn57pZkEkzw+dR0J8OZvpJinTeStqUUYCEbfRKetBcnIYEEl4Kaq3M= X-Received: by 2002:ac8:777a:: with SMTP id h26mr23230581qtu.235.1629580969459; Sat, 21 Aug 2021 14:22:49 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sat, 21 Aug 2021 15:22:39 -0600 Message-ID: Subject: Re: Dell Latitude 7400 - nvme0: Missing interrupt To: Pavel Timofeev Cc: Chuck Tuffli , freebsd-current Content-Type: multipart/alternative; boundary="000000000000d1520905ca18620e" X-Rspamd-Queue-Id: 4GsWgY6qn7z4RkJ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000d1520905ca18620e Content-Type: text/plain; charset="UTF-8" On Sat, Aug 21, 2021 at 3:06 PM Pavel Timofeev wrote: > > > Warner Losh : > >> >> >> On Fri, Aug 20, 2021 at 10:42 PM Pavel Timofeev wrote: >> >>> Pavel Timofeev : >>> >>> > >>> > Chuck Tuffli : >>> > >>> >> On Mon, Aug 16, 2021 at 7:43 PM Pavel Timofeev >>> 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: 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: 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: 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: 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 > OK. That all makes sense. I'd forgotten that nvd_compat=1 by default these days. I'll take a look on monday starting at the differences in interrupt assignment that are apparent when you cold boot vs reboot. Thanks for checking... I'd hoped this was a cheap fix, but also didn't really expect it to be. Warner --000000000000d1520905ca18620e--