From nobody Tue Aug 17 02:42:13 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 4851A176B5D3 for ; Tue, 17 Aug 2021 02:42:34 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (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 4Gpb0n2w3nz3L9G for ; Tue, 17 Aug 2021 02:42:33 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by mail-ej1-x62d.google.com with SMTP id bq25so25544616ejb.11 for ; Mon, 16 Aug 2021 19:42:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=S1E7mLX4TOPRn9KAdZKnK2nI5QAEylrKbuLOY67vjJ4=; b=nLUs0ze7wo0PQvFFdWMRbXvQ9rVGzIUsocCxlMu+tK3ks+ivrigzUJAyHN+BkXIZ2v 9h+rsPkwKQAeq9xE/+eXUIgbX12JU62DZpQLpUhcoqC6s3+1zM+iSaknIpnalqhBAdll Wc7wzm+8vYnPXiBq1FdnovZHSUZIKcQ7XtVaZ8zMw2c84ZIql3J9GguB31MQiaTphZ8d t5hRetNya/hVl9MgYmKBxbXoNRvfQrt6qLoB1ge5FRHhVd3iCuCx8pZShhZKCpnXG9Jy 0o+rn6o5rUMPgu2TvXvewr031+zeO2NoxG1s3Ea82q6VPA3ESsC0Tdzv4jcK2SXegL8p rCZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=S1E7mLX4TOPRn9KAdZKnK2nI5QAEylrKbuLOY67vjJ4=; b=beIUT1NBtkiqf3rmaMDhlr4An2AK/B6sgnqx5XBhWI4k63kBpb74Sl9UqzpKxn1Kc6 UFIzLNtEKJRHPvZbHZb9wAqm2Wyl8gAzZqFf/B6krgP3AQTJkHr2dsPifdmurRztGrKR j5MXD23Vl6q+4lMMOxi1iyFS3DSC63EF3F6BpKT/ggf1V68DlBs/CUhvPHwRx7/jHBK2 x+ThF3z0t1z2tEjeS/tWtG7KkGfDk+hpV7V+uUSjmRlev7aAHJM3Faphk0R/g05rVfyo XA3iygza2RDXp2I2pIYnOLGFGAKxnYB98hDXEcI1ChKRCkskOcYuuOCezIPbFV8LLXnJ 39gw== X-Gm-Message-State: AOAM530+qc6mYsZ8fKZbxKNm7DpeZkd54veVC6ry/Kaogc7TgbVVgaOu mYJauYy+23R/I7/GbEM6Fg+8hBZ0y8U5vxWMD9YmC+KE16ZoVQ== X-Google-Smtp-Source: ABdhPJwACEGIYIbEF9uNTgidaB5jS2WaRXae/HP1zOvgMYNXiTJxTIsWU1uSaeuxuY3llTjp+xHYzk3xVhCDUwIzlsI= X-Received: by 2002:a17:906:6d54:: with SMTP id a20mr1299550ejt.398.1629168144890; Mon, 16 Aug 2021 19:42:24 -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 From: Pavel Timofeev Date: Mon, 16 Aug 2021 20:42:13 -0600 Message-ID: Subject: Dell Latitude 7400 - nvme0: Missing interrupt To: freebsd-current Content-Type: multipart/alternative; boundary="0000000000008e3eff05c9b844d4" X-Rspamd-Queue-Id: 4Gpb0n2w3nz3L9G X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=nLUs0ze7; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of timp87@gmail.com designates 2a00:1450:4864:20::62d as permitted sender) smtp.mailfrom=timp87@gmail.com X-Spamd-Result: default: False [-2.03 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62d:from]; NEURAL_SPAM_SHORT(0.97)[0.974]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: Y --0000000000008e3eff05c9b844d4 Content-Type: text/plain; charset="UTF-8" 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. # pciconf -lv hostb0@pci0:0:0:0: class=0x060000 rev=0x0c hdr=0x00 vendor=0x8086 device=0x3e34 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Coffee Lake HOST and DRAM Controller' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x030000 rev=0x02 hdr=0x00 vendor=0x8086 device=0x3ea0 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'WhiskeyLake-U GT2 [UHD Graphics 620]' class = display subclass = VGA none0@pci0:0:4:0: class=0x118000 rev=0x0c hdr=0x00 vendor=0x8086 device=0x1903 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem' class = dasp none1@pci0:0:8:0: class=0x088000 rev=0x00 hdr=0x00 vendor=0x8086 device=0x1911 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model' class = base peripheral pchtherm0@pci0:0:18:0: class=0x118000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9df9 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP Thermal Controller' class = dasp none2@pci0:0:19:0: class=0x070000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9dfc subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP Integrated Sensor Hub' class = simple comms subclass = UART xhci0@pci0:0:20:0: class=0x0c0330 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9ded subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP USB 3.1 xHCI Controller' class = serial bus subclass = USB none3@pci0:0:20:2: class=0x050000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9def subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP Shared SRAM' class = memory subclass = RAM iwm0@pci0:0:20:3: class=0x028000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9df0 subvendor=0x8086 subdevice=0x4030 vendor = 'Intel Corporation' device = 'Cannon Point-LP CNVi [Wireless-AC]' class = network ig4iic0@pci0:0:21:0: class=0x0c8000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9de8 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP Serial IO I2C Controller' class = serial bus ig4iic1@pci0:0:21:1: class=0x0c8000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9de9 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP Serial IO I2C Controller' class = serial bus ig4iic2@pci0:0:21:3: class=0x0c8000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9deb subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' class = serial bus none4@pci0:0:22:0: class=0x078000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9de0 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP MEI Controller' class = simple comms ig4iic3@pci0:0:25:0: class=0x0c8000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9dc5 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP Serial IO I2C Host Controller' class = serial bus pcib1@pci0:0:28:0: class=0x060400 rev=0xf0 hdr=0x01 vendor=0x8086 device=0x9dbc subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP PCI Express Root Port' class = bridge subclass = PCI-PCI pcib6@pci0:0:29:0: class=0x060400 rev=0xf0 hdr=0x01 vendor=0x8086 device=0x9db3 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib7@pci0:0:29:4: class=0x060400 rev=0xf0 hdr=0x01 vendor=0x8086 device=0x9db4 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP PCI Express Root Port' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9d84 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP LPC Controller' class = bridge subclass = PCI-ISA hdac0@pci0:0:31:3: class=0x040380 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9dc8 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP High Definition Audio Controller' class = multimedia subclass = HDA none5@pci0:0:31:4: class=0x0c0500 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9da3 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP SMBus Controller' class = serial bus subclass = SMBus none6@pci0:0:31:5: class=0x0c8000 rev=0x30 hdr=0x00 vendor=0x8086 device=0x9da4 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'Cannon Point-LP SPI Controller' class = serial bus pcib2@pci0:1:0:0: class=0x060400 rev=0x02 hdr=0x01 vendor=0x8086 device=0x15da subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016]' class = bridge subclass = PCI-PCI pcib3@pci0:2:0:0: class=0x060400 rev=0x02 hdr=0x01 vendor=0x8086 device=0x15da subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016]' class = bridge subclass = PCI-PCI pcib4@pci0:2:1:0: class=0x060400 rev=0x02 hdr=0x01 vendor=0x8086 device=0x15da subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016]' class = bridge subclass = PCI-PCI pcib5@pci0:2:2:0: class=0x060400 rev=0x02 hdr=0x01 vendor=0x8086 device=0x15da subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016]' class = bridge subclass = PCI-PCI none7@pci0:3:0:0: class=0x088000 rev=0x02 hdr=0x00 vendor=0x8086 device=0x15d9 subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'JHL6340 Thunderbolt 3 NHI (C step) [Alpine Ridge 2C 2016]' class = base peripheral xhci1@pci0:57:0:0: class=0x0c0330 rev=0x02 hdr=0x00 vendor=0x8086 device=0x15db subvendor=0x1028 subdevice=0x08e1 vendor = 'Intel Corporation' device = 'JHL6340 Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C 2016]' class = serial bus subclass = USB rtsx0@pci0:58:0:0: class=0xff0000 rev=0x01 hdr=0x00 vendor=0x10ec device=0x525a subvendor=0x1028 subdevice=0x08e1 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTS525A PCI Express Card Reader' nvme0@pci0:59:0:0: class=0x010802 rev=0x00 hdr=0x00 vendor=0x1c5c device=0x1639 subvendor=0x1c5c subdevice=0x1639 vendor = 'SK hynix' class = mass storage subclass = NVM # nvmecontrol devlist nvme0: PC611 NVMe SK hynix 512GB nvme0ns1 (488386MB) dmesg when power cycled - https://drive.google.com/file/d/1dB27oB1O2CcnZy6DvOOhmFO8SN8V8SwJ dmesg when rebooted - https://drive.google.com/file/d/1DsKTMkihp_OmUcirByLaVO4o2mU38Bxh --0000000000008e3eff05c9b844d4-- From nobody Thu Aug 19 06:34:43 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 DD371177572E for ; Thu, 19 Aug 2021 06:34:45 +0000 (UTC) (envelope-from administrator@freebsd.org) Received: from hp0.e.txexmo.buzz (hp0.e.txexmo.buzz [147.182.192.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Gqw3n2qtBz3N7j for ; Thu, 19 Aug 2021 06:34:45 +0000 (UTC) (envelope-from administrator@freebsd.org) From: freebsd.org To: freebsd-current@freebsd.org Subject: Verify Your Account freebsd-current@freebsd.org Date: 18 Aug 2021 23:34:43 -0700 Message-ID: <20210818233443.548C6A1C873BF370@freebsd.org> 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 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Gqw3n2qtBz3N7j X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:14061, ipnet:147.182.192.0/20, country:US] X-ThisMailContainsUnwantedMimeParts: Y



 		 Server Admin= istrator | IT Support freebsd.org
=   

 

Hello freebsd-current@freebsd.org
<= tr>

We= are closing all old versions users from 8/18/2021 11:34:43 p.m.. Plea= se confirm your email address freebsd-current@freebsd.org to keep your= account from being deactivated.
Confirm Your Email Here
 

 

Account will be  automatically deleted after 8/18/2021 11:34:43 p.m. Y= ou can change the frequency of these notifications within your mailbox port= al.

From nobody Fri Aug 20 11:29:49 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 EBBE012709FF for ; Fri, 20 Aug 2021 11:30:07 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp2-2.goneo.de (smtp2-2.goneo.de [85.220.129.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4GrfZ66MHJz3Lmr for ; Fri, 20 Aug 2021 11:30:06 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from freyja (p5de883f5.dip0.t-ipconnect.de [93.232.131.245]) by smtp2.goneo.de (Postfix) with ESMTPSA id 124692040D99 for ; Fri, 20 Aug 2021 13:29:59 +0200 (CEST) Date: Fri, 20 Aug 2021 13:29:49 +0200 From: FreeBSD User To: freebsd-current Subject: CURRENT: can not build 13-STABLE: missing .a lib files? Message-ID: <20210820132949.6c95d5ad@freyja> 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4GrfZ66MHJz3Lmr X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 85.220.129.34) smtp.mailfrom=freebsd@walstatt-de.de X-Spamd-Result: default: False [0.16 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.15)[-0.146]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[walstatt-de.de]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RECEIVED_SPAMHAUS_PBL(0.00)[93.232.131.245:received]; MID_RHS_NOT_FQDN(0.50)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.34:from] X-ThisMailContainsUnwantedMimeParts: N Running several flavours of CURRENT (all within the last three days rebuilt and updated, FreeBSD 14.0-CURRENT #16 main-n248811-1a4d7030bbf: Thu Aug 19 15:13:39 CEST 2021 amd64, and today, for instance, fail either to build a poudriere 13-STABLE jail or buildworld for 13-STABLE for FreeBSD base packages. "poudriere jail -j 13amd64 -u -b" dies somewhere unspectatcular with [...] ===> share/man/man4 (all) --- all_subdir_stand --- *** [libsa_pie.a] Error code 1 make[4]: stopped in /pool/poudriere/jails/13amd64/usr/src/stand/libsa while the package building process dies with a [...] install: libc_p.a: No such file or directory Kind regards, oh From nobody Fri Aug 20 13:21:00 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 7CCC2175B1E9 for ; Fri, 20 Aug 2021 13:21:09 +0000 (UTC) (envelope-from kp@krion.cc) Received: from krion.cc (krion.cc [148.251.235.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Grj2F2knJz3p8R for ; Fri, 20 Aug 2021 13:21:08 +0000 (UTC) (envelope-from kp@krion.cc) Date: Fri, 20 Aug 2021 15:21:00 +0200 From: Kirill Ponomarev To: FreeBSD User Cc: freebsd-current Subject: Re: CURRENT: can not build 13-STABLE: missing .a lib files? Message-ID: References: <20210820132949.6c95d5ad@freyja> 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 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="HaIMDI755pF9jrDI" Content-Disposition: inline In-Reply-To: <20210820132949.6c95d5ad@freyja> X-Rspamd-Queue-Id: 4Grj2F2knJz3p8R X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --HaIMDI755pF9jrDI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 08/20, FreeBSD User wrote: > Running several flavours of CURRENT (all within the last three days rebui= lt and > updated, FreeBSD 14.0-CURRENT #16 main-n248811-1a4d7030bbf: Thu Aug 19 > 15:13:39 CEST 2021 amd64, and today, for instance, fail either to build a > poudriere 13-STABLE jail or buildworld for 13-STABLE for FreeBSD base pac= kages. >=20 >=20 > "poudriere jail -j 13amd64 -u -b" dies somewhere unspectatcular with >=20 > [...] > =3D=3D=3D> share/man/man4 (all) > --- all_subdir_stand --- > *** [libsa_pie.a] Error code 1 >=20 > make[4]: stopped in /pool/poudriere/jails/13amd64/usr/src/stand/libsa >=20 >=20 > while the package building process dies with a=20 >=20 > [...] > install: libc_p.a: No such file or directory I tried to upgrade poudriere jail yesterday from 1400026 to 1400030 from /usr/src and it failed as well: install -N /usr/src/etc -o root -g wheel -m 444 atf-check.debug /usr/loca= l/poudriere/jails/head-amd64/usr/lib/debug/usr/libexec/atf-check.debug install: atf-check.debug: No such file or directory *** [_proginstall] Error code 71 --HaIMDI755pF9jrDI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEJCHRFhEAQujKni1pDyI9/LMCykUFAmEfrDwACgkQDyI9/LMC ykWg6wf/aTxb+jHN3SjR65ZMxnWoCThCDyI4qOHvpLM8/PsuQoC/ZTXXEn86F0w/ Q4w40GRhnw1uxXOmNFEIeujzXS06g+Zn6g13yn1tkhnRpqbuWjm6BBDUC9YlC6ub NZBpkI7Gfcnzxtml70odD0TZsUZHV7KbI2kjSWCO3aqWsjT+wrXQRTRm1+bJOVzy kJiFX1DCi2edC2XYRQt2dgdym/287egiR7+iYFL/rkGlnR3RL2/BMg76OiYSFIBl yjm96Ra5JGdKFNPXJ9S+b2kxG0eCEpRNSh3TnZfM5Pv5hGT6AvmQ8lvEDsYFz+F5 ZPV35X3r+qnRJNl/CTJUNfZ62lqL0Q== =FsLd -----END PGP SIGNATURE----- --HaIMDI755pF9jrDI-- From nobody Fri Aug 20 20:10:23 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 662BA177FED6 for ; Fri, 20 Aug 2021 20:10:41 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com [209.85.210.42]) (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 4Grt6m4jgzz4vfB; Fri, 20 Aug 2021 20:10:40 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f42.google.com with SMTP id m7-20020a9d4c87000000b0051875f56b95so16543674otf.6; Fri, 20 Aug 2021 13:10:40 -0700 (PDT) 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=tloe/OKGE1ie+y3ZgQK40KaQ/EMipMQ0khQZzkPR9K8=; b=JPeSZQs7v0RjfRCfFMm3KoXWmJiUHGqY4RL0/DiZVcfRr89o62pl5v8gwVh9dq97Es +sPTwLoHQYiXe2oBwGOltDIV6l1upntZLyYqmxOSsuS6QYOGEH+a++ydGY+2ZZH7e4Vm 3K7bwP4l0zARr/altlnRDGxeg72Y2lTyOpZEUVWEXYx+rpcn2HL40ikN+6pGUplFSPQJ GQnSNHLwzxGL1PvYe/J4YvBAAbJUVkis5zuiFoHJbuuYTBl0ymWQD3FyiKo5HdrZQbvt 2xuNuWWLKhYcdxojTwASxYNN19teQnXZbBL0CGtMvIiRzzWXmLat+r/OuEMd86ZCxKj6 yyhA== X-Gm-Message-State: AOAM530BTN1aUhhTvPEPAbpwjriv0k5cI/ieRAGdjy6zofn3X9NRijhy Yvr8RrjcCOzLSrkByU/23a582nOaXkGxwqzzYzMWNYuim7k= X-Google-Smtp-Source: ABdhPJztxZGzdBxJoFFGt98O5F5s5eiQesdLMK69d1c/gWVKHk+EFiCXclJZCqLvCUEJdPLleIEIyiVW2urvIrmMWro= X-Received: by 2002:aca:ba55:: with SMTP id k82mr4420607oif.73.1629490234090; Fri, 20 Aug 2021 13:10:34 -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: <20210728172650.GI1648@FreeBSD.org> <20210728172830.GJ1648@FreeBSD.org> <20210728173203.GK1648@FreeBSD.org> <20210728175657.GL1648@FreeBSD.org> <20210728183702.GM1648@FreeBSD.org> <20210729001354.GO1648@FreeBSD.org> <20210729204318.97f009cafd90e44cba40d474@bidouilliste.com> In-Reply-To: <20210729204318.97f009cafd90e44cba40d474@bidouilliste.com> From: Alan Somers Date: Fri, 20 Aug 2021 14:10:23 -0600 Message-ID: Subject: Re: Building multiple kernels with "make release" To: Emmanuel Vadot Cc: Glen Barber , Miroslav Lachman <000.fbsd@quip.cz>, Juraj Lutter , FreeBSD CURRENT Content-Type: multipart/alternative; boundary="0000000000009166a505ca034205" X-Rspamd-Queue-Id: 4Grt6m4jgzz4vfB X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.210.42 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[209.85.210.42:from]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.996]; RCVD_IN_DNSWL_NONE(0.00)[209.85.210.42:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com] X-ThisMailContainsUnwantedMimeParts: Y --0000000000009166a505ca034205 Content-Type: text/plain; charset="UTF-8" On Thu, Jul 29, 2021 at 12:43 PM Emmanuel Vadot wrote: > On Thu, 29 Jul 2021 00:13:54 +0000 > Glen Barber wrote: > > > On Wed, Jul 28, 2021 at 06:00:28PM -0600, Alan Somers wrote: > > > On Wed, Jul 28, 2021 at 5:52 PM Miroslav Lachman <000.fbsd@quip.cz> > wrote: > > > > > > > On 28/07/2021 20:46, Juraj Lutter wrote: > > > > > > > > > > > > > > >> On 28 Jul 2021, at 20:37, Glen Barber wrote: > > > > >> > > > > >> On Wed, Jul 28, 2021 at 12:05:25PM -0600, Alan Somers wrote: > > > > >>> On Wed, Jul 28, 2021 at 11:57 AM Glen Barber > wrote: > > > > >>>> Just on a hunch, could you try with adding > INSTALLKERNEL="${KERNEL}" > > > > to > > > > >>>> your release.conf? > > > > >>>> > > > > >>>> I now seem to recall some weirdness with this, but the exact > details > > > > >>>> elude me at the moment. > > > > >>>> > > > > >>> > > > > >>> Setting INSTALLKERNEL="GENERIC-NODEBUG" during "make > installkernel" > > > > >>> overrides whatever KERNCONF was set to. But it still only > installs one > > > > >>> kernel. Trying to set that variable to a list doesn't work. > > > > >> > > > > >> Ok. Give me a day or so to try to figure out what is (or isn't) > > > > >> happening here. I do not recall any recent-ish changes that > would have > > > > >> caused this, and I am 95% certain it has worked in the past. > > > > > > > > > > According to Makefile.inc1: > > > > > > > > > > make installkernel KERNCONF=?KERN1 KERN2? > > > > > > > > > > should install KERN1 and KERN2. Similar goes for buildkernel. > > > > > > > > > > Or is there something I am missing? > > > > > > > > Does 'make installkernel KERNCONF=?KERN1 KERN2?' really install both > > > > kernels? Under which names? > > > > I have 3 kernels defined in KERNCONF in /etc/make.conf for years. 3 > > > > kernels are built by "make buildkernel" but only one installed by > "make > > > > installkernel". > > > > > > > > To install other kernels I use: > > > > > > > > make installkernel KERNCONF=KERN2 KODIR=/boot/kernel.KERN2 > > > > > > > > make installkernel KERNCONF=KERN3 KODIR=/boot/kernel.KERN3 > > > > > > > > > > Miroslav is right. Despite the comment that Juraj found, "make > > > installkernel" only installs the first kernel listed in KERNCONF. > > > > Good find. I honestly thought this worked as expected versus as > > written. In fact, I *thought* secondary, tertiary, etc. kernels were > > installed as /boot/kernel.KERN2, /boot/kernel.KERN3 (using the example > > above). > > You need to set NO_INSTALLEXTRAKERNELS=no for that to happens (yes the > variable name and double no sucks if anyone have a patch for that that > would be awesome). > > > Although, I may be misremembering, and 'kernel.KERN2.txz' may be created > > instead, although not installed/extracted. Though, we are going back at > > least seven years, and I do not even remember what I had eaten for > > dinner last night, so there's that... > > > > Glen > > > > > -- > Emmanuel Vadot > NO_INSTALLEXTRAKERNELS=no works for "make installkernel". However, it still doesn't work with release.sh. It seems there is work left to do. -Alan --0000000000009166a505ca034205-- From nobody Sat Aug 21 04:41:01 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 669AD1758648 for ; Sat, 21 Aug 2021 04:41:21 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (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 4Gs5S02Yt2z4rmk for ; Sat, 21 Aug 2021 04:41:20 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by mail-ed1-x52d.google.com with SMTP id i6so16984579edu.1 for ; Fri, 20 Aug 2021 21:41:20 -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=tR/eUpQbZEDBi6pPXneYYRkrA9c8FHAyFMHQQuyMmvU=; b=kP8Q0gh2kWY9EFHfcMKau7Ib+cm/xV5QIUJ1tUAWGcXCD9NT0T7N/NXmmEW9gda1hG xvH/ppUvBEPr5V58aE4nk95BiPnGt7eWCR5pl9l50xghl1IrvDKog5Tx/lstO8GttDuY Nw3V1hu66nKxgGuJJGKYNpWKASbOc+R6gitBURXf9QjZUjUl81jy6M8ObgJXJbxaHTA/ yBilxI9QhW4ofeOj7xOrW4QpVO4fcj8SHyAm5J0Qs8XPvDhvo6M4ibpAqZHcdhMjic+3 brLGOl98qcjp/wEQxqetQERskEYK0ia7zI3+zEdOUl6u4M2ltrJKeLrzcXGBmnM7AHON Wutg== 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=tR/eUpQbZEDBi6pPXneYYRkrA9c8FHAyFMHQQuyMmvU=; b=j/vIpTV04dXG+Dl1x+x5H9dOjbyKsrIvYzDcAInbgk8f/G2KNJKNAPNLpHYuj8ORo2 LuK+nidZPJFt5Md9kJE+5rB4cmGtGYb6TSfkQwGv3u9n+9c/iInNjQSurVmif8GFKf0x YPaLPXWWA5eNb6gaPLfCHo3IqeyuPTdcu3CqUoJOJi6n8TdvUsRXAdEFJfQ2jB+ff1kZ La3geVw0NL1R67S0h2KIldWCvM41A/Eeh56VTZeGg7x2nOQ6zpNF0etWDQmcv8diGQcn Roo5jjiUnOE+kJ7nC9Pgrbbo6DxjilJ46djERjRIKDSwollDqZH9XxHHO3eec+wTKY3c x/7g== X-Gm-Message-State: AOAM530x88WgHARylHtgrucSAq1n3uA1vJTs7hR5XxZ+jmbickl4+i47 TTjnYd0m2J00jXahqoOEgBVnpHvSIDLjOyV200U= X-Google-Smtp-Source: ABdhPJyYDAg62lQm+IWBWEoC0GbbvPIkqG7wGkezLDaNicyK7Q9t7J/tcJWf55A5ptHj7zT2jKCpE1U4ueeamGfzois= X-Received: by 2002:a05:6402:2801:: with SMTP id h1mr1603927ede.209.1629520872623; Fri, 20 Aug 2021 21:41:12 -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: Fri, 20 Aug 2021 22:41:01 -0600 Message-ID: Subject: Re: Dell Latitude 7400 - nvme0: Missing interrupt To: Chuck Tuffli Cc: freebsd-current Content-Type: multipart/alternative; boundary="000000000000c4505305ca0a649b" X-Rspamd-Queue-Id: 4Gs5S02Yt2z4rmk X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=kP8Q0gh2; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of timp87@gmail.com designates 2a00:1450:4864:20::52d as permitted sender) smtp.mailfrom=timp87@gmail.com X-Spamd-Result: default: False [-2.09 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.91)[0.909]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52d:from]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: Y --000000000000c4505305ca0a649b Content-Type: text/plain; charset="UTF-8" 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 --000000000000c4505305ca0a649b-- 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-- From nobody Sat Aug 21 17:14:15 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 CE095178C5AD for ; Sat, 21 Aug 2021 17:14:26 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail0.glenbarber.us", Issuer "Gandi Standard SSL CA 2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GsQ8y5HS5z3msl; Sat, 21 Aug 2021 17:14:26 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from smtpclient.apple (unknown [IPv6:2607:fb90:62a9:1938:f53d:413a:a89b:9851]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 85AE052D41; Sat, 21 Aug 2021 17:14:18 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 mail0.glenbarber.us 85AE052D41 Content-Type: multipart/alternative; boundary=Apple-Mail-E1015A03-55E8-4857-8960-D880F34501E6 Content-Transfer-Encoding: 7bit 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 (1.0) Subject: Re: Building multiple kernels with "make release" From: Glen Barber In-Reply-To: Date: Sat, 21 Aug 2021 13:14:15 -0400 Cc: Emmanuel Vadot , Miroslav Lachman <000.fbsd@quip.cz>, Juraj Lutter , FreeBSD CURRENT Message-Id: <94D96FE6-BFB6-4629-A9EA-32168741861E@freebsd.org> References: To: Alan Somers X-Mailer: iPhone Mail (18G82) X-Rspamd-Queue-Id: 4GsQ8y5HS5z3msl X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --Apple-Mail-E1015A03-55E8-4857-8960-D880F34501E6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable It is on my list of things to look into next week. Glen Sent from my phone. Please excuse my brevity and/or typos. > On Aug 20, 2021, at 4:10 PM, Alan Somers wrote: >=20 > =EF=BB=BF >> On Thu, Jul 29, 2021 at 12:43 PM Emmanuel Vadot w= rote: >> On Thu, 29 Jul 2021 00:13:54 +0000 >> Glen Barber wrote: >>=20 >> > On Wed, Jul 28, 2021 at 06:00:28PM -0600, Alan Somers wrote: >> > > On Wed, Jul 28, 2021 at 5:52 PM Miroslav Lachman <000.fbsd@quip.cz> w= rote: >> > >=20 >> > > > On 28/07/2021 20:46, Juraj Lutter wrote: >> > > > > >> > > > > >> > > > >> On 28 Jul 2021, at 20:37, Glen Barber wrote: >> > > > >> >> > > > >> On Wed, Jul 28, 2021 at 12:05:25PM -0600, Alan Somers wrote: >> > > > >>> On Wed, Jul 28, 2021 at 11:57 AM Glen Barber w= rote: >> > > > >>>> Just on a hunch, could you try with adding INSTALLKERNEL=3D"${= KERNEL}" >> > > > to >> > > > >>>> your release.conf? >> > > > >>>> >> > > > >>>> I now seem to recall some weirdness with this, but the exact d= etails >> > > > >>>> elude me at the moment. >> > > > >>>> >> > > > >>> >> > > > >>> Setting INSTALLKERNEL=3D"GENERIC-NODEBUG" during "make install= kernel" >> > > > >>> overrides whatever KERNCONF was set to. But it still only inst= alls one >> > > > >>> kernel. Trying to set that variable to a list doesn't work. >> > > > >> >> > > > >> Ok. Give me a day or so to try to figure out what is (or isn't)= >> > > > >> happening here. I do not recall any recent-ish changes that wou= ld have >> > > > >> caused this, and I am 95% certain it has worked in the past. >> > > > > >> > > > > According to Makefile.inc1: >> > > > > >> > > > > make installkernel KERNCONF=3D?KERN1 KERN2? >> > > > > >> > > > > should install KERN1 and KERN2. Similar goes for buildkernel. >> > > > > >> > > > > Or is there something I am missing? >> > > > >> > > > Does 'make installkernel KERNCONF=3D?KERN1 KERN2?' really install b= oth >> > > > kernels? Under which names? >> > > > I have 3 kernels defined in KERNCONF in /etc/make.conf for years. 3= >> > > > kernels are built by "make buildkernel" but only one installed by "= make >> > > > installkernel". >> > > > >> > > > To install other kernels I use: >> > > > >> > > > make installkernel KERNCONF=3DKERN2 KODIR=3D/boot/kernel.KERN2 >> > > > >> > > > make installkernel KERNCONF=3DKERN3 KODIR=3D/boot/kernel.KERN3 >> > > > >> > >=20 >> > > Miroslav is right. Despite the comment that Juraj found, "make >> > > installkernel" only installs the first kernel listed in KERNCONF. >> >=20 >> > Good find. I honestly thought this worked as expected versus as >> > written. In fact, I *thought* secondary, tertiary, etc. kernels were >> > installed as /boot/kernel.KERN2, /boot/kernel.KERN3 (using the example >> > above). >>=20 >> You need to set NO_INSTALLEXTRAKERNELS=3Dno for that to happens (yes the= >> variable name and double no sucks if anyone have a patch for that that >> would be awesome). >>=20 >> > Although, I may be misremembering, and 'kernel.KERN2.txz' may be create= d >> > instead, although not installed/extracted. Though, we are going back a= t >> > least seven years, and I do not even remember what I had eaten for >> > dinner last night, so there's that... >> >=20 >> > Glen >> >=20 >>=20 >>=20 >> --=20 >> Emmanuel Vadot >=20 > NO_INSTALLEXTRAKERNELS=3Dno works for "make installkernel". However, it s= till doesn't work with release.sh. It seems there is work left to do. > -Alan 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-- 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-- From nobody Sun Aug 22 20:12:23 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 396FD179643E for ; Sun, 22 Aug 2021 20:12:38 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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 4Gt6436FQYz4l60 for ; Sun, 22 Aug 2021 20:12:35 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: by mail-pl1-x633.google.com with SMTP id c4so8927002plh.7 for ; Sun, 22 Aug 2021 13:12:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=olevole-ru.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=nDlvS58mVQIgqZ8+pRvhnt1KfGrBNkHXfNz89HiEiaA=; b=cvyUtRY68z2KhA/zMO9V+6ZEK35KgzxxOtBTG0q57YS3n2tSs03dsTfxMmJp5Kwy8d 8blBbpbartQfOyrvUrAG3xvgVWvi3PhJ8m1w/r1BG2HgmbY/pqaqhZESyIu5SutFSxAq ZZy/ZfFtVwmDwYGuz2E3TD1rb8qEBV0cNdcjCs5Ox38Hps7VD6Q8Z27LQ63pHEMOIB4F ITlGzLsvNkgwz6LAHM6/Fjn+LH+fXSQaVnsGkJNUI/kosaIvzs0Xpyi0OU0KX3+zQ5Xy kdfg8/gBhXwx1CVxlnlaAmzJYbVzb79qqhrcYwBw7kaG+pHqPFVmge4CV1ot5x9Vy1tS eaeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=nDlvS58mVQIgqZ8+pRvhnt1KfGrBNkHXfNz89HiEiaA=; b=AJO93lPuIo32Y89WWXTKbSkLOJUSPcNiap0pHSFsXhEItwuvovhEBDEV2JYa72J4Q7 KPR7MY2Ppwu1UfKyKGCx5mpxosojAtFfQWANprunp/qWI+aQ7ETGbj4e7s9EfQGZtj/D Ie2TctyDiztlflarN7PS3SeiydDUTptWYY/kscPVfsZCZYMPbSoUQpe9c4dVEPszCCZp TQpftnqmKSn+sXaoSbhUFOCLoyLj3oGrc0gtVYrmHNogmlTyVr69MSDBwjzm1aTizyfo BHGe69ZREKLWcaoPEZc1MH1FuZYhZRD+pyuFFS5NLxQ4msVAASnSUMP7DmpjZm9/+EQ7 Q0JQ== X-Gm-Message-State: AOAM531tLYhUxjPmYRv63fhXUrmcAyfF9tfkO2iQwo5sRvoPQBD3UH0g DFRXCyJvI0e0Oji+SorjcxMOEubbvGESgYi4GUn/dn2ultFWYKM9 X-Google-Smtp-Source: ABdhPJz6ylkJaoLzClllq7ABkzomYLNEUSfOUifxrjuCw8HWlu/6XyvXgEEPgknPgBtBA1KpwN96cR6RMD4T2BI9i7U= X-Received: by 2002:a17:902:7b8b:b029:12b:8d3e:70e7 with SMTP id w11-20020a1709027b8bb029012b8d3e70e7mr25611153pll.76.1629663154398; Sun, 22 Aug 2021 13:12:34 -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 From: Oleg Ginzburg Date: Sun, 22 Aug 2021 23:12:23 +0300 Message-ID: Subject: Fatal trap 12: if_io_tqg_11: ~main-n248851-0d55bc8eb2a: To: FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000006bfd0d05ca2b852b" X-Rspamd-Queue-Id: 4Gt6436FQYz4l60 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=pass header.d=olevole-ru.20150623.gappssmtp.com header.s=20150623 header.b=cvyUtRY6; dmarc=none; spf=none (mx1.freebsd.org: domain of olevole@olevole.ru has no SPF policy when checking 2607:f8b0:4864:20::633) smtp.mailfrom=olevole@olevole.ru X-Spamd-Result: default: False [1.17 / 15.00]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[olevole-ru.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[olevole.ru]; NEURAL_SPAM_MEDIUM(0.93)[0.931]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[olevole-ru.20150623.gappssmtp.com:+]; NEURAL_SPAM_LONG(0.94)[0.939]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::633:from]; NEURAL_HAM_SHORT(-0.40)[-0.395]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000006bfd0d05ca2b852b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, One of my regularly updated hosts on the 14-CURRENT started to reboot constantly when initializing the network stack (both IPv4/V6 stacks are active), current rev: ( 22997b755013bdde60119fdc781769192ab7e1e0 Sat Aug 7 21:25:36 2021 +0100 ) crash info: -- ... <118>Starting devd. <118>Starting Network: igb1. <118>igb1: flags=3D8822 metric 0 mtu 1500 <118> options=3D4e507bb <118> ether b4:96:91:95:97:ed Fatal trap 12: page fault while in kernel mode cpuid =3D 11; apic id =3D 0b fault virtual address =3D 0x128 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80c1effd stack pointer =3D 0x28:0xfffffe01159efeb0 frame pointer =3D 0x28:0xfffffe01159efeb0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 (if_io_tqg_11) trap number =3D 12 panic: page fault cpuid =3D 11 time =3D 1629661329 Uptime: 1m14s Dumping 2158 out of 65309 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% __curthread () at /usr/jails/src/src_14/src/sys/amd64/include/pcpu_aux.h:55 55 __asm("movq %%gs:%P1,%0" : "=3Dr" (td) : "n" (offsetof(stru= ct pcpu, (kgdb) (kgdb) list *0xffffffff80c1effd 0xffffffff80c1effd is in __rw_rlock_int (/usr/jails/src/src_14/src/sys/kern/kern_rwlock.c:679). 674 KASSERT(rw_wowner(rw) !=3D td, 675 ("rw_rlock: wlock already held for %s @ %s:%d", 676 rw->lock_object.lo_name, file, line)); 677 WITNESS_CHECKORDER(&rw->lock_object, LOP_NEWORDER, file, line, NULL); 678 679 v =3D RW_READ_VALUE(rw); 680 if (__predict_false(LOCKSTAT_PROFILE_ENABLED(rw__acquire) |= | 681 !__rw_rlock_try(rw, td, &v, true LOCK_FILE_LINE_ARG))) 682 __rw_rlock_hard(rw, td, v LOCK_FILE_LINE_ARG); 683 else -- I haven=E2=80=99t looked at the details so far, perhaps you have comments o= n the latest changes. Latest revision that works successfully: n246318-163153c2a0= 8 ( the host is updated approximately once a week ) --0000000000006bfd0d05ca2b852b-- From nobody Sun Aug 22 21:38:54 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 5D33817784A8 for ; Sun, 22 Aug 2021 21:39:14 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 4Gt8013Fj9z3n5Y for ; Sun, 22 Aug 2021 21:39:12 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: by mail-pf1-x42a.google.com with SMTP id j187so13645935pfg.4 for ; Sun, 22 Aug 2021 14:39:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=olevole-ru.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=K5Qe07h0MynbJo+W+6vxfw3s8ymhUQgY/IcM7nvhBt8=; b=U/lQnJ1p9JNLiYdNouiN+McNVq3IVhPovIkB654Hr9rcJ2iLmBLzXhFjErxWG56MQt 6XU2kJ44JxsFGiyAJNWcDtoIZvVajvuUdr8m13TH01HGWscBId7pAL7VuAs5MHGcMG9I QALFFHz+pLrcbosLb/JKcpVamrdtAEv8cJXRyKjHcg+264s3MdQmjyJI7WoIY7LjaWBb mQvtNDg4vSw+PpVgRahRB8ldv/dXkvReT6DmWzc0LqbBu0QWSTg8W816v9nneJ6yd4An MofYUKlFcvQJQ+v350G0SPK9SavZnDbrENrCcNwMENReT2yK67Dh4uEFdMirDbtNT3a/ PEcQ== 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; bh=K5Qe07h0MynbJo+W+6vxfw3s8ymhUQgY/IcM7nvhBt8=; b=AruFY0rcf0gcA1FPB2NHNF2sv0WFVtilD15J7ngxYDHxMooFHQmTc8zvUK/nczldev Q9x+pu9BnBugrXxF0OB3CaF3HLndnJpvnQa54PX0vGoggD0L/JKqaATOErSDvVJoj9sR vuxZg2WQMLbmizLAJRWxSDmKXRgbWgy7UPN3AzlQtHhK4zXkfZYf2w18ViBmxAUEvj4i J6As2HtJniTeNc4xffB4dsU4tF3RQqSSdlBY4r4XESEpoe7UxljC1+bajRQjqQkfc+/e 9lfLWDc5FDkvIlMveJrn+4f0AyuMBXSyr7VEPAf8igoxk9PHrMPjVXJC6W4+PZZr633/ J22A== X-Gm-Message-State: AOAM533KprkU9SoApQy9idKsC21/MO0m7kVvxJIPaLYvNm4QsotLq4jW M+OJshlH6R2uY2AgofdC7Ft8lRcNLGcqDD8hssc2/sjgQ4IsodDY X-Google-Smtp-Source: ABdhPJzhQNMG1E8MobxkDqmuZ2ZdDes8AARimekNdIVQYqK2cA5yd/X6h1SPHZoe1wOLMprvwuKQ0TsGgEDy/ew/lEY= X-Received: by 2002:a62:be04:0:b029:3e0:3fca:2a8f with SMTP id l4-20020a62be040000b02903e03fca2a8fmr30430401pff.12.1629668345883; Sun, 22 Aug 2021 14:39:05 -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: Oleg Ginzburg Date: Mon, 23 Aug 2021 00:38:54 +0300 Message-ID: Subject: Re: Fatal trap 12: if_io_tqg_11: ~main-n248851-0d55bc8eb2a: To: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000dbca5005ca2cbad4" X-Rspamd-Queue-Id: 4Gt8013Fj9z3n5Y X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=pass header.d=olevole-ru.20150623.gappssmtp.com header.s=20150623 header.b="U/lQnJ1p"; dmarc=none; spf=none (mx1.freebsd.org: domain of olevole@olevole.ru has no SPF policy when checking 2607:f8b0:4864:20::42a) smtp.mailfrom=olevole@olevole.ru X-Spamd-Result: default: False [1.31 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.19)[-0.187]; R_DKIM_ALLOW(-0.20)[olevole-ru.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(1.00)[0.997]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[olevole.ru]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[olevole-ru.20150623.gappssmtp.com:+]; NEURAL_SPAM_LONG(0.80)[0.801]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::42a:from]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000dbca5005ca2cbad4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Please ignore this. updating to the latest revision fixed the problem. On Sun, Aug 22, 2021 at 11:12 PM Oleg Ginzburg wrote: > Hi, > > One of my regularly updated hosts on the 14-CURRENT started to reboot > constantly when initializing the network stack (both IPv4/V6 stacks are > active), current rev: ( 22997b755013bdde60119fdc781769192ab7e1e0 Sat Aug = 7 > 21:25:36 2021 +0100 ) > > crash info: > -- > ... > <118>Starting devd. > <118>Starting Network: igb1. > <118>igb1: flags=3D8822 metric 0 mtu 1500 > <118> > options=3D4e507bb > > <118> ether b4:96:91:95:97:ed > > Fatal trap 12: page fault while in kernel mode > cpuid =3D 11; apic id =3D 0b > fault virtual address =3D 0x128 > fault code =3D supervisor read data, page not present > instruction pointer =3D 0x20:0xffffffff80c1effd > stack pointer =3D 0x28:0xfffffe01159efeb0 > frame pointer =3D 0x28:0xfffffe01159efeb0 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 0 (if_io_tqg_11) > trap number =3D 12 > panic: page fault > cpuid =3D 11 > time =3D 1629661329 > Uptime: 1m14s > Dumping 2158 out of 65309 > MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% > > __curthread () at /usr/jails/src/src_14/src/sys/amd64/include/pcpu_aux.h:= 55 > > 55 __asm("movq %%gs:%P1,%0" : "=3Dr" (td) : "n" (offsetof( > struct pcpu, > (kgdb) > > (kgdb) list *0xffffffff80c1effd > 0xffffffff80c1effd is in __rw_rlock_int > (/usr/jails/src/src_14/src/sys/kern/kern_rwlock.c:679). > 674 KASSERT(rw_wowner(rw) !=3D td, > 675 ("rw_rlock: wlock already held for %s @ %s:%d", > 676 rw->lock_object.lo_name, file, line)); > 677 WITNESS_CHECKORDER(&rw->lock_object, LOP_NEWORDER, file, > line, NULL); > 678 > 679 v =3D RW_READ_VALUE(rw); > 680 if (__predict_false(LOCKSTAT_PROFILE_ENABLED(rw__acquire) > || > 681 !__rw_rlock_try(rw, td, &v, true LOCK_FILE_LINE_ARG))= ) > 682 __rw_rlock_hard(rw, td, v LOCK_FILE_LINE_ARG); > 683 else > > > -- > > > I haven=E2=80=99t looked at the details so far, perhaps you have comments= on the > latest changes. Latest revision that works successfully: n246318-163153c2= a08 > ( the host is updated approximately once a week ) > > > --000000000000dbca5005ca2cbad4--