From nobody Sat Aug 21 21:06:11 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 0DA8E177AC88 for ; Sat, 21 Aug 2021 21:06:25 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 4GsWJc6YGvz3qgC for ; Sat, 21 Aug 2021 21:06:24 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by mail-ej1-x636.google.com with SMTP id e21so11797378ejz.12 for ; Sat, 21 Aug 2021 14:06:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=opUj2Sb3akxuVmIDmP22MEkazh1J6nL803DORxpUtWw=; b=hodn4snq9t0P18lNxAzhWIPvvj2iu8oL9NE7FWifYEau5Lf6K1cGQcMUpFQXM+Hsk4 iuGE8Yx1zyxXUaSN7QviHpZJs9MTQDH3ZK+n3kirXFBRFUGNzzQTbC8Clnxc1dml9KcO +97CqhHaPJNmZnnHhdplVCQOz5RWo3BXEggc0nZrn4Wuxu1oG311grCm1VAxXMpLBTiu /Mohmm2vKLVRO4xb7dcCB1QLmWuhh2L91+Ltf60JHkJlwc3YpVBob0P0eN+J3V/LR7sa j3psV4Pxp2wN2wLvHdpRRICUGXvhdnpeW0PR6SKF2QYTy8boU8/psxbuEcUcqdWt5xbh Hh7Q== 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=opUj2Sb3akxuVmIDmP22MEkazh1J6nL803DORxpUtWw=; b=iJ0s1TlySIw1YSaJ3QZ2k3/Yaus0FPFpltCmWHZV/op9LEKjwwi2+CV2WxqL6HqRyg OLFbatjnlNV8vm8Chiu1aKaNI3nKUVI/HUs0C59vvE9jiO504xSvCNTYL12AlahwAye/ JS/sIv/q6xozNSICT1SZg7X0D0vYvKCQH8qLDChPlDlo4Jy/0fB2StOHqwM8gHCPQ9/H iu+vaV11QHp+Ybd6ijucv1b8+Ac+rLNuJAMucU5eGUQEEP4qiwNdAp0F9OnpRIHY7xFN yQOP5gAtkXrAMCp2yDq0WTqiCa/VDYX+HKIYgNBe48TITE7ZM51EXv9redpRzV2rXL1b YBjQ== X-Gm-Message-State: AOAM531lzuPpBUntWf5RYm2j5DY9z87gLwnQg15eL4mbXWTb+ERLhMWK z1VmnPA6uZapshLa0Sb8m9iYIYckFOYJ9wNdyhQ= X-Google-Smtp-Source: ABdhPJzohDxIteCeBi2/60h2OooTYa9vbSOD0ZraV8IhOplxmT6rzk7dd5dgqPXL4EbrNASKu1PBPV5RzXjRao5BHls= X-Received: by 2002:a17:906:c1d0:: with SMTP id bw16mr28263663ejb.146.1629579982906; Sat, 21 Aug 2021 14:06:22 -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: Pavel Timofeev Date: Sat, 21 Aug 2021 15:06:11 -0600 Message-ID: Subject: Re: Dell Latitude 7400 - nvme0: Missing interrupt To: Warner Losh Cc: Chuck Tuffli , freebsd-current Content-Type: multipart/alternative; boundary="00000000000003a69405ca18282f" X-Rspamd-Queue-Id: 4GsWJc6YGvz3qgC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --00000000000003a69405ca18282f Content-Type: text/plain; charset="UTF-8" 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 --00000000000003a69405ca18282f--