From nobody Sat Aug 21 04:48: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 B3969175D5B9 for ; Sat, 21 Aug 2021 04:48:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 4Gs5c6440dz4vk6 for ; Sat, 21 Aug 2021 04:48:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x82e.google.com with SMTP id y9so9218526qtv.7 for ; Fri, 20 Aug 2021 21:48:22 -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=VPRp4FB0wDMLCvLSW8F6HYYwm06SLpU/tbKEittsnAE=; b=CYXAP4cKmE02iRh6SQwUyWEQcTZnPgfXNz9S6bNwTzUyV5QFZbI8TLL9M5f/LwjUJn IPZB87EpZ3riAYXsRLhhfHIVjhXMkwf4Wg/znvvsn+9oFwBhKuPDyGOC28ZQe4nHpCpQ HQ84cC271aD7JydrCezopSSI/ojGLa1H3n/PJtQAhmL2VpIOa8OKmLsQWa9bbAc0kOBa HVt4gpDdo2isDy6VZpI+x4BB6KAg3hDoW35GW8cNenRWfeVJA17TE8SleXHRsSFNC4cM Amj1Qfwtd4mw5vVne30bfY5KUzmFAUjZH3aq6skjxH7mi6MbyzzQVX49h5PY+Pfy/PZd M2aA== 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=VPRp4FB0wDMLCvLSW8F6HYYwm06SLpU/tbKEittsnAE=; b=Z5yjmSBQ8VHPuR2p+30tJ/DXmf4UsgAjIHy2gFeb50AZrcbC8R3TvaLVNJfxu4TBvS +e5RbwzbXvT3cYgLq1r690qAjpy9DEocmbIbHu96u33e3Ab61nKLxAY+A4Fp9F9gtIow JIP9oXaj7Nbyah3mEL8X135TrgL4UdXxkjO0kmqayo7qaC7lqYZGsdfNIlUr4BqFJn4J liC5PtOEn2enEdqPg969mU+Ozaj2044Xy5lMamkYNurP2OFmssjyCXSR8q7S2a4YE508 /kuoNffY4jha1AJIVTFwvY1ZhHmoO5BFHfRF6Hv/Fya7ipcDl6StspWRuyWg7Cst3irI cl2w== X-Gm-Message-State: AOAM533TFQZ0eu8854ArxCaXRhKcpEbHCEe+wRf4e5XGbs0v3VXr53aH cynjQSVeD4yLbnpq0fNoKk8Wt0sd1jXWiIwgP20tHg== X-Google-Smtp-Source: ABdhPJxiahs6M03S03rMmxpb/p+OcYAdPJr03ib5NVUwR7xRtIo0gat1/sc0WxmgT45r0h9i79IRgHfYnNB0qpqpAZI= X-Received: by 2002:ac8:6759:: with SMTP id n25mr20566361qtp.49.1629521302011; Fri, 20 Aug 2021 21:48: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: Warner Losh Date: Fri, 20 Aug 2021 22:48:11 -0600 Message-ID: Subject: Re: Dell Latitude 7400 - nvme0: Missing interrupt To: Pavel Timofeev Cc: Chuck Tuffli , freebsd-current Content-Type: multipart/alternative; boundary="0000000000005c54de05ca0a7e56" X-Rspamd-Queue-Id: 4Gs5c6440dz4vk6 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000005c54de05ca0a7e56 Content-Type: text/plain; charset="UTF-8" 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 --0000000000005c54de05ca0a7e56--