From nobody Sun Jul 16 15:51:46 2023 X-Original-To: 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 4R3qTG5Lj5z4n9s6 for ; Sun, 16 Jul 2023 15:51:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R3qTG3Vpkz4WnW for ; Sun, 16 Jul 2023 15:51:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689522706; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=gMEGnieUe/ukMhyQusscjCKZVVXxHpypTBtQhCoH/AU=; b=fULbGPZ7cDZXg+mAKNMKJD2F8FyI2kpnH37CikhEU61gTvUG4YAqWk27TQ95chC1gz9vUG ZgGN02P9pichHEeoBvjvDt/AsJDfKR7WrdEuFJOGHUw+UTTvQ/WAYN39BKXmjurYtwJU8E TsUt33DR08aQZ12Spt4l1/Ibj2ZaFzCtxVnkBFLGpYprYGjN2sBTlY0o388Y8QzpqYbPs7 ZWxOauAY48ps950Ema3XzLnqxrDBKWYm6QqGFNT31CLOSLaslKDQGRP3C74al462LeslCT tGceWq5V0+X+WpjnKtTlwtdgXKQAP9/LJxmFwTjBSJwqXhai947+CgNlV5A4TA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1689522706; a=rsa-sha256; cv=none; b=cZ+dzGfpY1NMDxRkg3gwMGDQADjosxKmJbYJy/lavigifx2Ry+Eu4Cs8kflrXyl2ddXFtV XuAQUP4WLhuv3rPMxwWFp2Vr+ohMWmZov2zfR1Mo3bSwfLNWpuXYkcX01YaZdzr1rd4qH8 rmpDRqg5jED/MrmvLsIJmhcG7dgNIxperShdtFqyB7hIkuut3dcfECvlbg23J5HqcqF6OR 1uSzmFeQsNFa/S/ajVjbxzLvvQLHLWjx9WK5oOmIm+B4UADsLHY54q23Z8SrUgiIBkfN/r BkLf6zhGSElxw5EKj2+Oi4tEaXDpt5GBQ4w6XLzYY9lR85A0XaeoXUC+ZMdg+A== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4R3qTG2ZZnznSK for ; Sun, 16 Jul 2023 15:51:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 36GFpkvn003948 for ; Sun, 16 Jul 2023 15:51:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 36GFpkWR003947 for current@FreeBSD.org; Sun, 16 Jul 2023 15:51:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page Date: Sun, 16 Jul 2023 15:51:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yuri@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: current@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_file_loc assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272536 Yuri Victorovich changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://people.freebsd.org/ | |~yuri/screenshot-clang-kill | |ed-on-FreeBSD-14.png Assignee|bugs@FreeBSD.org |current@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sun Jul 16 16:38:06 2023 X-Original-To: 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 4R3rVk3PpRz4md6f for ; Sun, 16 Jul 2023 16:38:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R3rVk1bfwz3J7Q for ; Sun, 16 Jul 2023 16:38:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689525486; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=TTcnX1AQ/hmegc+zkYgI4ixKbFUjOl2KJtqUHHdnkvM=; b=Cn2HRWtf6szdiAuGFy81obLF/9ST5fqSJQF9p5+EQvwjJu+5z0qgQIhJyFp4AB0PVYUbQx JtbqfHMO3hgkbYyefAGS+o+StDnEZIpFA4Dq8+dxOYhZZxmwfStMN6H/tPHLvsEEdE/LBv x9DRpbJXspEo69Xk2Y3OPtGgfo/cgJVrKsDYlAv0I4+JBuGQ2f5Q3851gsMNZuX7vxF2ts /VUWfdUW2/2idnmwERKFVPz2Itoki40Leo7Rc9tGgA4CbY+1woWgRave9i8YSx+xNRTVE4 zym4IIM7JtWSKDd/LBqoZY7G6iEHTLsixw1FwVwxAgcn1r02Gye7ZGG4lQma1g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1689525486; a=rsa-sha256; cv=none; b=yHe2U4m9XA3yVKsxM/pD0k5R6Dy0X6Pg3krpY+KiUtfxyxJI7eucfB2Wlq9GD5H5OXIasA bHqLQ8OjR8ldyASXjOVdEcOkgdvb2ezXJ37jWZ08wPgA/vKZvDHRZQF2WO/CSD3GHokOsc lJKP91G5FlB3RtfSLHiOYEJSVgXHsYJhgI2i2H9duh5y1dGcGAmuDYGmE6Kvo4jnh/NuY+ uuxyIzwkf61xEfbCji3YATsxyXlzSJWzcWjDFQ4oiQWDqOdaxehunBldXzeoyGUszpJl+9 cKdPJoT90jWR2z5NQFbvlxYDpLsnkQhzPmNjAIWuebiWuCyTAGNPdsJ58SDDFA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4R3rVk0YJSzpWq for ; Sun, 16 Jul 2023 16:38:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 36GGc5BN075082 for ; Sun, 16 Jul 2023 16:38:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 36GGc5Iw075081 for current@FreeBSD.org; Sun, 16 Jul 2023 16:38:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page Date: Sun, 16 Jul 2023 16:38:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: current@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272536 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #1 from Mark Millard --- The actual message is from sys/vm/vm_pageout.c (looking in modern source): case VM_OOM_MEM_PF: reason =3D "a thread waited too long to allocate a = page"; break; ("waited" instead of "waiting"). Do you have anything specific for what controls getting VM_OOM_MEM_PF: # sysctl -d vm.pfault_oom_wait vm.pfault_oom_attempts vm.pfault_oom_wait: Number of seconds to wait for free pages before retrying the page fault handler vm.pfault_oom_attempts: Number of page allocation attempts in page fault handler before it triggers OOM handling The defaults are: # sysctl vm.pfault_oom_wait vm.pfault_oom_attempts vm.pfault_oom_wait: 10 vm.pfault_oom_attempts: 3 What sort of storage media was the swap space on? Spinning Rust? Sometimes VM environments have accuracy problems with various forms of time handling. So that might be another direction involved for this issue. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sun Jul 16 16:43:02 2023 X-Original-To: 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 4R3rcQ4t4cz4mfbr for ; Sun, 16 Jul 2023 16:43:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R3rcQ20m2z3KhF for ; Sun, 16 Jul 2023 16:43:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689525782; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BXG/013QGmq8zMeH4RQCCDoOSsHbug9a6MyqtMsFS3w=; b=VVLLNiRsmY21Qhh/CFnz4ANEYyGZEuH+1cErguLkYVE4/8ZD2nqbS4IcsowiO7zA64asQy a9NYc1OuTCNPtOOdN5/nlfKi0MSTiNeAc7Znp8OEm6G6OBmPlkhftdFlfa+gKS+X7YHCnw m7T2b0UpLi/M3e3JD0OppQ8Rl7gKFKRS8sOlDM0zw9oBQCg30RsUr32tLNbW4J8cRcDCQ1 TNWIIatq8KJufJLdPooTLc85TF3+dO7VLnJKwTRzitmb+IwyCmcpNC2448zRiZO+BGE86V YVEitSB9aaRAplX6QsfRuYpD3O1dV7H18IK9Hai37vaSl+kytC/uWP4FdvSExQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1689525782; a=rsa-sha256; cv=none; b=LDoKnqaIJh3H1pK4sBHbd6du5ibkunGnWeD+xPwkniWJ4S3iVr1XG0lunMtYQbNlZNrEFe AfUlTtrVWTUj2rK6noYagOv/682h7pCdqVjd/q+D9xTQMsT47B3oHKO7oOijpOweCoTq7z 4i82U+S9RNZmsCBUCQRgemB4txic0RUdGXMMR5kOjvdSHktAfwLmCd5dXG0Fj8owLdRbTa 9k3jvoBLhzJuN+WedBbnqsZRFDhyzkEFnzwbkUgcjtlU7WkKNfdDSuVUT0SjlXpH8RKmuq 0JeBkjlfP+LK5B+uFYyvZrV3Juw9LWTrCIN9hN4HmF2mBMC77bKKNfx4CsfKEw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4R3rcQ0RDlzpyL for ; Sun, 16 Jul 2023 16:43:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 36GGh2Uk086502 for ; Sun, 16 Jul 2023 16:43:02 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 36GGh2Rr086501 for current@FreeBSD.org; Sun, 16 Jul 2023 16:43:02 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page Date: Sun, 16 Jul 2023 16:43:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yuri@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: current@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272536 --- Comment #2 from Yuri Victorovich --- (In reply to Mark Millard from comment #1) Swap is on /dev/ada0p2. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sun Jul 16 16:43:48 2023 X-Original-To: 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 4R3rdK00VWz4mfcV for ; Sun, 16 Jul 2023 16:43:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R3rdJ5Qxvz3Ljg for ; Sun, 16 Jul 2023 16:43:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689525828; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XhvsucAcfAMLpX7CHryfFUn/dhtV2qEkUVX8/ahqWso=; b=jL/j86J5R/ZL9jCiN23M5Tp/H65DKdz70rHyHk2Ftj0oV8Ww8L0ISQe+NoTxqYFn9Wud60 30/DqMGFV6IK2ApwyzXjXWfmkMZHPgjQM6OuJw0r8YCy2lrwNqOx1Qvo2UPd5XpH+prl8r NrHZXkmWUPx68yfg3IbeKg2pvWlUnr9sA5STzO0bJEco8ic1fANxLi2QevnQo9W1EDDMcy FcC6Q7JNM4K45u2T1405AvOFRIcvakh0LvVXN1BJSNRMFa+6hDv/GTbSNf+d8hlUb1evZs lrvVKnwrCUkjsxn1LI2rmgLNA2unH/ab5xhbFa+E+r11wtCGnAuSKL94/EZFPA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1689525828; a=rsa-sha256; cv=none; b=wxNgpv93tJORtkwR2WLQ35lT33uZK4X4YB412z4GgxMys5Dv9et8GiZhilwwz01etcosdb CvhpD3oVapgQ7lqBcQi9ssCU0vEvB4wwTI68MwxPDua6y7J2jMzlf5iAsEzrqLBZRoT58F 8yuOmXh+zWzEZ/WGoFY1yO5hnI6x9rkqZ26Oe6zZoOP8Za23acEcLUR4hdAeLyUCKVKKrv OUDBgRmkBdcvoKReDg+Pm/iEN21N7eRAGhAkXxkI28yazOAOoOsEa/ZZtt6n42Piw4sHNj 5KSHc8Jb+U05ql2tJoeClS6Z7x6l3FPUeanh2zuxVLPIaLmaao2wBSAFsYrW/w== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4R3rdJ4WWWzqCQ for ; Sun, 16 Jul 2023 16:43:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 36GGhm3p086700 for ; Sun, 16 Jul 2023 16:43:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 36GGhmFm086699 for current@FreeBSD.org; Sun, 16 Jul 2023 16:43:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page Date: Sun, 16 Jul 2023 16:43:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yuri@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: current@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272536 --- Comment #3 from Yuri Victorovich --- (In reply to Mark Millard from comment #1) > Do you have anything specific for what controls getting [...]. This is a generic install. No specific options of any kind were set. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sun Jul 16 17:14:42 2023 X-Original-To: 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 4R3sJy4TVWz4n0Zb for ; Sun, 16 Jul 2023 17:14:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R3sJy3R44z3lj8 for ; Sun, 16 Jul 2023 17:14:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689527682; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=8hDwVIqEBSCejhXGQ0H9i5QMp7J/ITfu5u34lzPBZkg=; b=UJXkS10XROS4iFuj/YVpQJoCOyBEwb12coB7pk8RXNNsdttm5wW6nh4EE21UDTDEw8s1Wd SYlQX1d6rHp+gHWJy7Q+4rHmD6HNLYpyQp3Fyzsp81C5jMS0qMfuOZMcJkXjthjVSJC3S1 E5ZXVMVJyHx+7JjnLTbZ3GpUPyBad/pE5meznwDgB6qPU4fnKyzU0wopzAW4+lMyb07/dv QEsUmLBfKqgDl+wIKdm51qUOlBFd3weVdNUaA48kJ0RoVGOy2eMXEjXytKiN4xwZEAwqmZ lDfrct6NxYUvZlFqYCSCPQfsC+l2+RpW2QYlotVz9JS+qrvfKSkFoQCWVZK3WQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1689527682; a=rsa-sha256; cv=none; b=eH7lYDWvz8jjT2Ck6PWeScpcrepVUkbyIeGvGXfyqS9eszQ5DXkM/6nYOeJaWaN/81dG8f RC0sPsfYCDWGJWOGxjFIzdhKp5gcDucHYEBnyHAYEWQoD/KWRQG+9my2qpfNi5LbNhinlo jL2zYvYCYRWamwnqjYyPCprmqiipCMbDAU572yRysMEmRPxqCnIRYa5wNzH1S6ooUHY+1m lIYvK6Cd0rZKgNsjHixmTm09jVHp41mZV3Ga6LAeSJmFX1vtVZTRIgFOMqenVK5PwmRWEd wOzxX3wySH67710BP/OHstd2WszF7zFpFlGdkzsA9MVOu+ly3aF6H0zOug34/A== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4R3sJy2TWqzqf8 for ; Sun, 16 Jul 2023 17:14:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 36GHEgDA030145 for ; Sun, 16 Jul 2023 17:14:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 36GHEgG3030144 for current@FreeBSD.org; Sun, 16 Jul 2023 17:14:42 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page Date: Sun, 16 Jul 2023 17:14:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: current@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272536 --- Comment #4 from Mark Millard --- (In reply to Yuri Victorovich from comment #2) Being in a VirtualBox VM the /dev/ada0p2 may not indicate much about the actual media involved. Microsd card and spinning rust media are more likely than some other types of media to end up with larger than desirable delays. The environment running the VM (outside the VM) could be relevant as well. I was mostly after if the media was more vs. less likely to contribute to such a problem when the swap space is under heavy use. Other relevant things to know would include the actual RAM available to the FreeBSD instance, the number of hardware threads actually present for FreeBSD to run on, and probably more that I'm not managing to think of at the moment. Another would be if the system that was running the VM was also busy with other activities vs. being basically dedicated to running the one VM instance that was running the FreeBSD instance. But . . . It may be that, unless you end up showing repeatability, trying to make notes for such a range of issues is not worth the time and effort. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sun Jul 16 17:18:53 2023 X-Original-To: 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 4R3sPp0WCzz4n2jm for ; Sun, 16 Jul 2023 17:18:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R3sPn4Gbnz3nN2 for ; Sun, 16 Jul 2023 17:18:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689527933; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=O4F0GPAZUfPcE0ZnBui9kgtkknfe1vF8hAqI/gUtOQM=; b=oLswOjR6pHPmpisgWl0lYTKTWp8oYtSp205vz3ZesDP63L/MPkDjA3MJivjWFi4/oBMHGV NJ1J6XtfwtsznTmkDyv0jeWacakAtFCnPdUTQdWV9sHPigGRPx3rDboOLT9PQ9Xh3ixtg9 al1UjgMLXRtTEk69/I7D89AfD9aF4CRMDM1cU6I1cC85CK0MJvWX2ZCLGzARN+Ms3Tw0hu /lM2eVzQ2yLi2Mj6VH2V8j/4cTm1nkkwbeCOEN5FVk6xzo0mgomZRM8YPd+PZ8IEhq5HeG bhqk+Zud4AeuAJXPvCQbUOj0tOj54hUjcyf0u02QUOaQG3VreHFEK8XR/8TyUw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1689527933; a=rsa-sha256; cv=none; b=lUnp2eiHFuuxUgg+Eyrvfn61Sa50r5zXRlTAhSPaCV6ViHSypeKBb+t/QfdGv2Ymxdkg3r 7ajdBS5gxlXYPkjIltFn9BbFjV6bzgjkUyYkw5wZziDwy3SBpTR/6Mp/Fem/okh7h5TCv6 7v2F1GmpxdQUUOkaOPJsWHNJgS1KJq0VGXlphlWW5L9X8H5Gvu+8MdKI1SiOPvcYuizUSM KAZUyWnP6MFrK7AU9C0UNmzR+b3O7aGtaOMl2XbK7zDqnwnLr+aW2QCrtmpEeiCQ2FIj6n N4iegUgkMahULkbr/Ks+mht/4lEbNRrUw7nESj2qDadz4HSax1cvA1ZumVuVyw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4R3sPn3N6Czqf9 for ; Sun, 16 Jul 2023 17:18:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 36GHIrcc031555 for ; Sun, 16 Jul 2023 17:18:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 36GHIr3S031554 for current@FreeBSD.org; Sun, 16 Jul 2023 17:18:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page Date: Sun, 16 Jul 2023 17:18:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yuri@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: current@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272536 --- Comment #5 from Yuri Victorovich --- (In reply to Mark Millard from comment #4) > Being in a VirtualBox VM the /dev/ada0p2 may not indicate > much about the actual media involved. The physical medium is a traditional spinning HD with the UFS file system. The host OS is FreeBSD 13.2 amd64. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sun Jul 16 20:56:44 2023 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 4R3yFR36jMz4n2mT for ; Sun, 16 Jul 2023 20:56:59 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic316-55.consmr.mail.gq1.yahoo.com (sonic316-55.consmr.mail.gq1.yahoo.com [98.137.69.31]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4R3yFQ25fvz3qV9 for ; Sun, 16 Jul 2023 20:56:58 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=ifkZy1gV; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.69.31 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1689541016; bh=Rnbhs+CjtDJi3lWDAMhCPShM0SOCkMR9lfKf2f8BpLE=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=ifkZy1gV0pxNjELOZ/H//sJZdq2X2d6HzKoYjCHlRlj7qPFxhaBCNoEXEn+3KZXF7TxI/CIjAQvmz44H2yB5MtLyg80gfUgfsQ7NyUiEteNe51j349GHM6sKupwuKYY64NihcA6hfKBul4yv6hrhrC28sh72k5iVxSjRX+or5SYf5phMAaC1DDKtgDEYYa0X2J4L4Crzvev3gsfCNP2og0VpY9BJSkNPyjXlmCT16G90fqg8tt1vjVwwrkW8QQ+9MWBWodw2vW3bu6EIUql9lcFADe3ZHJ1Pa29yhURc35T6AITnjHV6a+UjJFVBeyaNce9OQXX1a/OB7MEqNvmNDA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1689541016; bh=BzBS7OCnfQ34lmeeQsqitOCNfYRHYD2MIm+jbmMaR6F=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=RcYk97Cv3oieogp+HMfvWCMywW49fsR9vq7B5AXz8mnytuExU3jj2st7ZE0Dw7yMFJ5UlOHChXAr5peqWbDPRox2fP8BgpeBiDUyM/cQqSMlGDKK/Q8YAAzqADOO4Qse+iTrLPIMBjZYvj3DPbZXYc5NErXplsbeTWMmVo5OJGW3uuAGir6KBgMU55iT3QVXO/vPkoG6upA+HVFv99N7lMpLG4eImimnIdo75s89MJ7YmedO/vmZrETW5BI7MwrV0Ic8bRj91zG2SN/goZ4BXFOJ+px8E01zrQPqMniXjOEg4CbOmrr+QLeIJ19ETgWT8yju4r/KLl2oLXdnEqRUww== X-YMail-OSG: ItH9H58VM1k7607Xnzi2VmNuc6_cqRWWhRLm52erRH7dhAHx.FeCdbrpM6q5U_g iid9G6bwGptQfTv4zk.vPTNfY1XwHUqBzRdsZ4HaFDPgEjlyqaYQi8mXDAyPb9GooZHSQyGiCwgF GXUF1Lt2sPNvOD1Gq_N1wCXWUd6KQ_1MIMZu_cZy1zBC1US.SqhQCvJEKKgI51I6Q3OBPiqFI0C1 3l.bLQX03nZXGwr4LdBV8Or6zYU4UqmlXDRxndXB8_azTtM67ejrldEul39VwxWS60jFl_R5nkYL Qibn34pfNE2aZzCCZ2T96Gbb8uk7NmNuzVLfQdOfm4Hsj9b78tNLWsowv5OtGZMRKaZ5nkPlCao3 hNmkc8zKABsuVXrmZVv_QKLu3Ga5oY2a4rHuqgbMXFZPtANi1a2at8hq5oN4H3Juirysd_JFu4lg 26c2ttkxB9N_YD835bwefWWb68W_aS.9cESqKTHZ5LAZYIpPN6vSwsVDg4F5cKUakOWbdwkd7of4 D5x.0hXLrOxk.sRnjXHVC4x52zVA0RZ_u6aNWodOnYpC9DxkoCPRnwui4x9jULNx6OGL9boVe0l2 tmZxeA4fYZOPKq2mU8kEOYIDZPfNAYYZjhzuvNV29E7_qdyxe9Ue7wN0j0RhhvqnNwTOERZof50Q nD8SLQuI6hICq4zbfLa4_gdhGtieKBh5Ewcp4yR7zslVBw7iWTOor3BbQaYJp9IxdoaRUH5toMUd WTrUcktwgDIQeNwt89HkLL0Y8fCQZsWOtfxPAnXShVlnGv0AZAgUYnrs5To2ihxxANMtIgoBPBAH 1MCgQlCMtACjRo35qrzeGJ.KPu9OfNnjm67XgjqPsDVHKgiUcgrdOEENkgEklwEbY1wxggzl.JKM ig5vGRhimzkQ5iOVe5tRR.WgyuJofHjL.MZNnUMzfhc6nP6WT9ajcAPH8N2fEjqNaXg_muTyEIIL cSfutZuLjhumQmrr7lE0U_exuCazDrM5l8BbhVhZmnHEb2U2wZ5neOugxlyNofFmudGsQYbObmvE hWeQgukuUt22vDSLUL2rkt.6eVWZ.JVHY88LIsQ.B1RJQr46OuhrzoOf3tbRl4.qEtERZVmiPDRV Lx1ghRhUjmnD7a7KON7F7Sq1DZ0gaYPdgA6hrGkDX8GVt5VRzyAG8Hp1bZlrc5P7y1N.mR54D6St RxeOjgbhRVKbkvcPw.8RYUfOeOJCMbCDM03Ta25wG7Djgb8p5RPfU3f80LOeYLid7ds_GAadYtbQ JdqHfkhEOB2jTajdRErCDiF0Rsi0FxvegofOSBRn4ss.8F69mMvRkXdQIFNVCzuTb3og6UYWHD9W u2BKrlYxza33BMrqdMLZLVD21N.MyG_.MkYpIjYpqN2kLERBa1ufMMZAF0uMsC84brShpeacQh9U QlrP1SpV2XAQwaiqCFAQJflEjufB1bWXQXzfAdGOucmwWVws_Lw6g6neP9o8n2n1wSydJsDBACWN nhjGUvCQlWIZUjPDqf3TdXbCziN07mAS4kadAIr3ZOdehBp0gGKBe0BQ.8ucvLqLhBNxOIrZnEGc K3aq.SBRRBSrzg5gLQpQHRbu5l_QJQbca5uZw1bsiUT6NXHnxqgReFHsulma95_6vXorS3CC7gmz mUseI_.DHW.3PbM2yC.Uh1PLk4hnkxCGqYGsWnUr9G9BbTaT2zB1yH87sEQuki0swAyC8sWNZq5v jKzu7VJM96AEXjjZPdLXZ6o..euRKWEPuLaaupKhJ14QKo6JvnlXkT04XM8NVPpadeRDQf2nGx09 fBIhQBHi4hkShUePH7jQrKAAburLO0x_JIimAc2KI9.U5sZD0skWuG8tNN.G7Pniet4dtl2M7p7e FqmipKj4bRAA9bX13LzEbp1ta9np.UgZF2FiIvx1unhHRpHlL2p5dixNvgRmHydrUlIxMma8eV55 dfVa2Mv9TJSPMZeZmw0TgHI4dk7I3Zuko4m2AHJXFiMBtf83LN1Q7nICwbLPcdR8JMAeIc.wEAOZ j3rYrrN3cBRZzCvGay6GCslA.wFDjTVMUG0L_O4F6EnburIqh1LTqIbrfv2hV.6ECYIB_KF2WVHM 3E_EKTNMSfsvEGUTNhLsJhYkD97Sk0uzUG7OODmeYc_ySl8xiIHDbf68fulYZvvaPXM9fE7utUyR dkBvs7zYPyeugZF2Dg3K.6SRCSx48dxTElxqQKSaGvAa3qvrYQThA9yCxAyKqBeL0g1v7pJppAsD TkL4aAO.Zm2tMn46vKmx70vLZj_Sw74HRcOqLoPyC8f3D..uvtChyWCe17w-- X-Sonic-MF: X-Sonic-ID: 3a98fff9-1d18-4239-89dc-7d04a4d85db0 Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Sun, 16 Jul 2023 20:56:56 +0000 Received: by hermes--production-gq1-5748b5bccb-wvpnt (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID b371673fe17a63728fd851fae2b5e4c4; Sun, 16 Jul 2023 20:56:54 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: rsync use with -tmsdosfs mounted file system? file has vanished: . . . Message-Id: <485EB974-5EF4-4569-9B40-81A474983F33@yahoo.com> Date: Sun, 16 Jul 2023 13:56:44 -0700 To: Current FreeBSD X-Mailer: Apple Mail (2.3731.600.7) References: <485EB974-5EF4-4569-9B40-81A474983F33.ref@yahoo.com> X-Spamd-Result: default: False [-3.18 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.996]; NEURAL_HAM_LONG(-0.98)[-0.978]; NEURAL_HAM_MEDIUM(-0.71)[-0.706]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.31:from]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; SUBJECT_HAS_QUESTION(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.31:from] X-Rspamd-Queue-Id: 4R3yFQ25fvz3qV9 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N I used a sequence that looked like: mount -onoatime -tmsdosfs /dev/gpt/CA72optM2efi /CA72optM2efi-media/ \ && rsync -x --delete -aAUHhh --info=3Dprogress2 /boot/efi/ = /CA72optM2efi-media/ that got: file has vanished: "/CA72optM2efi-media/BCM271~5.DTB" file has vanished: "/CA72optM2efi-media/BCM271~6.DTB" 73.77K 0% 1.63MB/s 0:00:00 (xfr#7, to-chk=3D0/493) = rsync warning: some files vanished before they could be transferred = (code 24) at main.c(1357) [sender=3D3.2.7] After that, activity reported the likes of: rsync: [generator] delete_file: unlink(overlays/VC4-KM~8.DTB) failed: = Read-only file system (30) and: rsync: [receiver] mkstemp "/CA72optM2efi-media/.fixup4.dat.2Wonu9" = failed: Read-only file system (30) More than rsync was odd at that point: # ls -Tld /CA72optM2efi-media/*.DTB ls: /CA72optM2efi-media/BCM271~5.DTB: No such file or directory ls: /CA72optM2efi-media/BCM271~6.DTB: No such file or directory # rm /CA72optM2efi-media/*/*.DTB override rwxr-xr-x root/wheel uarch for = /CA72optM2efi-media/overlays/SDHOST~1.DTB? y rm: /CA72optM2efi-media/overlays/SDHOST~1.DTB: Read-only file system . . . But: # mount | grep media /dev/gpt/CA72optM2efi on /CA72optM2efi-media (msdosfs, local, noatime) So the mount itself was not the source of the read-only status so far. I then tried: # umount /CA72optM2efi-media # newfs_msdos /dev/da0p1 # mount -onoatime -tmsdosfs /dev/gpt/CA72optM2efi /mnt # cp -aRx /boot/efi/ /mnt/ cp: utimensat: /mnt: Invalid argument (which is normal). # umount /mnt No more oddities , so far after that. For reference: # uname -apKU FreeBSD CA72-16Gp-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #99 = main-n264171-2a0c0aea4209-dirty: Fri Jul 14 21:00:44 PDT 2023 = root@CA72-16Gp-ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm6= 4.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400093 1400093 # pkg info rsync rsync-3.2.7 Name : rsync Version : 3.2.7 Installed on : Sat Jul 15 14:53:48 2023 PDT Origin : net/rsync Architecture : FreeBSD:14:aarch64 . . . Annotations : FreeBSD_version: 1400092 build_timestamp: 2023-07-02T06:57:44+0000 built_by : poudriere-git-3.3.99.20220831 cpe : cpe:2.3:a:samba:rsync:3.2.7:::::freebsd14:aarch64 port_checkout_unclean: no port_git_hash : f45cd5bd9d4b ports_top_checkout_unclean: yes ports_top_git_hash: 880f72e54deb =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Mon Jul 17 01:17:09 2023 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 4R441z5S7cz4nHnx for ; Mon, 17 Jul 2023 01:17:27 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R441z3kFzz43tq for ; Mon, 17 Jul 2023 01:17:27 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb2b.google.com with SMTP id 3f1490d57ef6-bad0c4f6f50so5687057276.1 for ; Sun, 16 Jul 2023 18:17:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689556646; x=1692148646; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=W6SZRIwBCvUdhNVj4tfegkNuK0u5O1RAENCWDrQJO4w=; b=BlvDH8R2GnkNE3oWq8CXnOs9WDGn4HLR3JCOYVg3M5fJVAA4TDIa7HHiSnVKp1Zbus cR0plSM/h8BoOFsQHTCNNikAUX//AVGXE6aHBtIkSxXWyM81Gvnt0adrcFKqCVr2q56I kOmbEfo4I2Ub9GD2ISEAbHJw+tR7ujPWEB1DJzhdS/p/l5/aAJiwRR+kfLMWIP33Gz02 QEQB7J5xsTBgiq6bpabnLGhW11MoiLCSLOmPp1perGtXisKaxT/hVNhEA0QOcNBLwNI5 5C58nXl0Ut5YW7EIhg/7Sd3ZFN+lM59huTb2IS5/9RygJ48nWid7P+quGRb3NHzypGQm WTVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689556646; x=1692148646; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=W6SZRIwBCvUdhNVj4tfegkNuK0u5O1RAENCWDrQJO4w=; b=Wb3kjnnKtUoZ25S5uzjNN0YKRsTaxq0HoYKhqnYaNDkPlT98Nu5I1RrU++DxalYB24 04SUKKPGQ77fu+Ve+d8C0JTYwbvfyCF6wqVPRl0vsk/drRXraiiq6JOOB1JnDySu2vQN CnUQce7omrn3NG2v2QeQ7lGmNxkO2UQzd5CmZsPVqfVhZiWimEL0YXQo8nTlRyil4ydM jbzlgIALF5sVKaSJYGQzDtA7vGzo5aBUbYi9Yv5g/tWrNJnK1mjXRyFitV65JeKCxeRY Qwx0tOk+3iampvrV86Ihz/+4Y02r3pm2coVbtkLEYoBE2fbTZf+fCRNVJALNmrOeEUw+ Yysw== X-Gm-Message-State: ABy/qLZqbARaCiVLPip4O1tCHLn6FAA+Qw/J6liraw3FfmaY4lTuijpP w6zqS/Hb5DSNgsHTXRxXVNmVf8nXQH3loel+2V18BZG1S78= X-Google-Smtp-Source: APBJJlHKw93Nn1i7tc5mv3bXuUVTnQA/0wiwruZbZI4d/oIK3CdkjDAbtsCgaHgeVt/BJzvqOvYVQNNZeqUDTmgOZAA= X-Received: by 2002:a25:a184:0:b0:cb8:a812:a91 with SMTP id a4-20020a25a184000000b00cb8a8120a91mr8596480ybi.0.1689556646080; Sun, 16 Jul 2023 18:17:26 -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: <485EB974-5EF4-4569-9B40-81A474983F33.ref@yahoo.com> <485EB974-5EF4-4569-9B40-81A474983F33@yahoo.com> In-Reply-To: <485EB974-5EF4-4569-9B40-81A474983F33@yahoo.com> From: Kevin Oberman Date: Sun, 16 Jul 2023 18:17:09 -0700 Message-ID: Subject: Re: rsync use with -tmsdosfs mounted file system? file has vanished: . . . To: Mark Millard Cc: Current FreeBSD Content-Type: multipart/alternative; boundary="000000000000b7b2ec0600a48f90" X-Rspamd-Queue-Id: 4R441z3kFzz43tq X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000b7b2ec0600a48f90 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Jul 16, 2023 at 1:57=E2=80=AFPM Mark Millard wr= ote: > I used a sequence that looked like: > > mount -onoatime -tmsdosfs /dev/gpt/CA72optM2efi /CA72optM2efi-media/ \ > && rsync -x --delete -aAUHhh --info=3Dprogress2 /boot/efi/ > /CA72optM2efi-media/ > > that got: > > file has vanished: "/CA72optM2efi-media/BCM271~5.DTB" > file has vanished: "/CA72optM2efi-media/BCM271~6.DTB" > 73.77K 0% 1.63MB/s 0:00:00 (xfr#7, to-chk=3D0/493) rsy= nc > warning: some files vanished before they could be transferred (code 24) a= t > main.c(1357) [sender=3D3.2.7] > > After that, activity reported the likes of: > > rsync: [generator] delete_file: unlink(overlays/VC4-KM~8.DTB) failed: > Read-only file system (30) > and: > rsync: [receiver] mkstemp "/CA72optM2efi-media/.fixup4.dat.2Wonu9" failed= : > Read-only file system (30) > > More than rsync was odd at that point: > > # ls -Tld /CA72optM2efi-media/*.DTB > ls: /CA72optM2efi-media/BCM271~5.DTB: No such file or directory > ls: /CA72optM2efi-media/BCM271~6.DTB: No such file or directory > > # rm /CA72optM2efi-media/*/*.DTB > override rwxr-xr-x root/wheel uarch for > /CA72optM2efi-media/overlays/SDHOST~1.DTB? y > rm: /CA72optM2efi-media/overlays/SDHOST~1.DTB: Read-only file system > . . . > > But: > > # mount | grep media > /dev/gpt/CA72optM2efi on /CA72optM2efi-media (msdosfs, local, noatime) > > So the mount itself was not the source of the read-only status so far. > > I then tried: > > # umount /CA72optM2efi-media > # newfs_msdos /dev/da0p1 > # mount -onoatime -tmsdosfs /dev/gpt/CA72optM2efi /mnt > # cp -aRx /boot/efi/ /mnt/ > cp: utimensat: /mnt: Invalid argument > > (which is normal). > > # umount /mnt > > No more oddities , so far after that. > > > For reference: > > # uname -apKU > FreeBSD CA72-16Gp-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #99 > main-n264171-2a0c0aea4209-dirty: Fri Jul 14 21:00:44 PDT 2023 > root@CA72-16Gp-ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/ar= m64.aarch64/sys/GENERIC-NODBG-CA72 > arm64 aarch64 1400093 1400093 > > # pkg info rsync > rsync-3.2.7 > Name : rsync > Version : 3.2.7 > Installed on : Sat Jul 15 14:53:48 2023 PDT > Origin : net/rsync > Architecture : FreeBSD:14:aarch64 > . . . > Annotations : > FreeBSD_version: 1400092 > build_timestamp: 2023-07-02T06:57:44+0000 > built_by : poudriere-git-3.3.99.20220831 > cpe : cpe:2.3:a:samba:rsync:3.2.7:::::freebsd14:aarch64 > port_checkout_unclean: no > port_git_hash : f45cd5bd9d4b > ports_top_checkout_unclean: yes > ports_top_git_hash: 880f72e54deb > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.co This looks a bit like an issue I was hitting on a 4 CPU, 4 thread Alder Lake processor and 500GB SSD running 13.2-RELEASE. I saw several very strange corruptions, at least one "rsync warning: some files vanished before they could be transferred". In one (the last) case, the system crashed. The 'disc' was corrupted badly enough that fsck failed and I could not boot up the system. The disk was UFS2 GPT format and EFI boot. The interface is SATA, not nVME. In this case, I was installing on a new system and copying the majority of the file system from my old system. The 'fix' is strange and probably not one many other can use. I installed a spinning rust drive of 500GB and installed FreeBSD and used rsync again and it worked. I can't say whether it was a fluke that it worked, but it really smells like some sort of race condition. Could be rsync , VFS, or device driver. Since then I have seen one crash while backing up the system disk using rsync. No corruption and doing another rsync after reboot worked fine, but it was a much smaller run as the first attempt was nearly complete when the system crashed. Maybe unrelated. I do have the core file from the crash. Stil, something weird has been going on. Same issue on two identical systems, so not likely hardware. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000b7b2ec0600a48f90 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Jul 16, 2023 at 1:57=E2= =80=AFPM Mark Millard <marklmi@yaho= o.com> wrote:
I used a sequence that looked like:

mount -onoatime -tmsdosfs /dev/gpt/CA72optM2efi /CA72optM2efi-media/ \
&& rsync -x --delete -aAUHhh --info=3Dprogress2 /boot/efi/ /CA72opt= M2efi-media/

that got:

file has vanished: "/CA72optM2efi-media/BCM271~5.DTB"
file has vanished: "/CA72optM2efi-media/BCM271~6.DTB"
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A073.77K=C2=A0 =C2=A00%=C2=A0 =C2=A0 1.63MB= /s=C2=A0 =C2=A0 0:00:00 (xfr#7, to-chk=3D0/493)=C2=A0 =C2=A0rsync warning: = some files vanished before they could be transferred (code 24) at main.c(13= 57) [sender=3D3.2.7]

After that, activity reported the likes of:

rsync: [generator] delete_file: unlink(overlays/VC4-KM~8.DTB) failed: Read-= only file system (30)
and:
rsync: [receiver] mkstemp "/CA72optM2efi-media/.fixup4.dat.2Wonu9"= ; failed: Read-only file system (30)

More than rsync was odd at that point:

# ls -Tld /CA72optM2efi-media/*.DTB
ls: /CA72optM2efi-media/BCM271~5.DTB: No such file or directory
ls: /CA72optM2efi-media/BCM271~6.DTB: No such file or directory

# rm /CA72optM2efi-media/*/*.DTB
override rwxr-xr-x root/wheel uarch for /CA72optM2efi-media/overlays/SDHOST= ~1.DTB? y
rm: /CA72optM2efi-media/overlays/SDHOST~1.DTB: Read-only file system
. . .

But:

# mount | grep media
/dev/gpt/CA72optM2efi on /CA72optM2efi-media (msdosfs, local, noatime)

So the mount itself was not the source of the read-only status so far.

I then tried:

# umount /CA72optM2efi-media
# newfs_msdos /dev/da0p1
# mount -onoatime -tmsdosfs /dev/gpt/CA72optM2efi /mnt
# cp -aRx /boot/efi/ /mnt/
cp: utimensat: /mnt: Invalid argument

(which is normal).

# umount /mnt

No more oddities , so far after that.


For reference:

# uname -apKU
FreeBSD CA72-16Gp-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #99 main-n264171-2a= 0c0aea4209-dirty: Fri Jul 14 21:00:44 PDT 2023=C2=A0 =C2=A0 =C2=A0root@CA72= -16Gp-ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/= sys/GENERIC-NODBG-CA72 arm64 aarch64 1400093 1400093

# pkg info rsync
rsync-3.2.7
Name=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: rsync
Version=C2=A0 =C2=A0 =C2=A0 =C2=A0 : 3.2.7
Installed on=C2=A0 =C2=A0: Sat Jul 15 14:53:48 2023 PDT
Origin=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: net/rsync
Architecture=C2=A0 =C2=A0: FreeBSD:14:aarch64
. . .
Annotations=C2=A0 =C2=A0 :
FreeBSD_version: 1400092
build_timestamp: 2023-07-02T06:57:44+0000
built_by=C2=A0 =C2=A0 =C2=A0 =C2=A0: poudriere-git-3.3.99.20220831
cpe=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : cpe:2.3:a:samba:rsync:3.2.7:= ::::freebsd14:aarch64
port_checkout_unclean: no
port_git_hash=C2=A0 : f45cd5bd9d4b
ports_top_checkout_unclean: yes
ports_top_git_hash: 880f72e54deb


=3D=3D=3D
Mark Millard
marklmi at yahoo.co

This looks a bit like a= n issue I was hitting on a 4 CPU, 4 thread Alder Lake processor and 500GB S= SD running 13.2-RELEASE.

I saw several v= ery strange corruptions, at least one "rsync warning: some files vanis= hed before they could be transferred". In one (the last) case, the sys= tem crashed. The 'disc' was corrupted badly enough that fsck failed= and I could not boot up the system. The disk was UFS2 GPT format and EFI b= oot. The interface is SATA, not nVME. In this case, I was installing on a n= ew system and copying the majority of the file system from my old system. <= br>

The 'fix' is strange and pro= bably not one many other can use. I installed a spinning rust drive of 500G= B and installed FreeBSD and used rsync again and it worked. I can't say= whether it was a fluke that it worked, but it really smells like some sort= of race condition. Could be rsync , VFS, or device driver. Since then I ha= ve seen one crash while backing up the system disk using rsync. No corrupti= on and doing another rsync after reboot worked fine, but it was a much smal= ler run as the first attempt was nearly complete when the system crashed. M= aybe unrelated. I do have the core file from the crash. Stil, something wei= rd has been going on. Same issue on two identical systems, so not likely ha= rdware.
--
Kevin Oberman, Part ti= me kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
P= GP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
<= /div>
--000000000000b7b2ec0600a48f90-- From nobody Mon Jul 17 03:46:30 2023 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 4R47LG6lVyz4nP77 for ; Mon, 17 Jul 2023 03:46:46 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic314-21.consmr.mail.gq1.yahoo.com (sonic314-21.consmr.mail.gq1.yahoo.com [98.137.69.84]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4R47LG49Byz3F0V for ; Mon, 17 Jul 2023 03:46:46 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1689565604; bh=ptq24cP22eHXwP1Mlqpa4RSj8172v6slzcOpfXaKsQw=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=KhphRCSdM28Mtgp0n/4uE8PvB16HRedMC/8Gh1wm5hSF/bTOJC5mTG/eRc79c2k0Az5IB6qVaIwAUZhRVBvfJeH5qg9Ub3FY0AGz4qBEp9d8R771UKXMQFo3j3TaJ6p3nEH39VijHRxUH15+uPPA3b9FKxVL1ejTuJ8jRfSPj9r3ZOPDVtoI1hLXPmf2JvOMsh3s0YhLZUbcBvIQD2EL3TXQ6C+G0FKDPCO/dafOle/7eXqeroTR+VDPdh0fY4/utVxT8U4/Ixj1I5Cl9LNIXWBiqdlINCCRNb+sq5gVYEYLMrTLMB3a+jtHbUISL8CUfx+oi8wNtkaceBUn4fsBBg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1689565604; bh=m2k6GKTx3zUh7m6h1ha6AJGFpqCuk4i9zJkcWvZi5ET=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=oORSQIKD8PPKOGplWQ0BJFkcTg10bMEpYjcwY1HuhxY8lKxW6ir8FL/vAfn61VrU12VnPo9pv/ImHghGCGhvd3Lhgq+N5YZMOjAnigpF0RQmltTWoWtMv77C8hScIZuKaluQcSGuzM7ItwjhiLCqfL5Bd/ZhrD4qYBKoejAzx6VTGSLfJIVsV7PUGquByYKnCMGQQY/pBarK6nK37Lzr/TZ/QKn3zTC8jJggn9/Mgcq+c73J1xmNZu2qv8zCN7hPRYa9Z1Qq5y41oNi+Csl8MJzm3EAbQUlCDYslOFVTyY0Vdd6ajagRtUxF2qscAHQ9zpVWsq7BM4XsCB3F7rjISA== X-YMail-OSG: kRvf7LYVM1lDfwQbejqLIv7V2dRBqkK._k7FGgg3LzGMTOrZLjkMVxsgMfyM8vb sGbrXF7dqf7SJlOi8sWZauebHnTfu.wTX87dH4VYnY4ZHgUZSAMs9ymllMMIM1Jqxtqj2ivIqcjj slx0ba.6Pe2grEPuqKBquiLUIftynOx6r83x00jiA2wu3u90hdQCdkDgHHf2ya_XqQf7Fy9R0eSi I1DrggA_jaUBF1J34gT9u4l4ghBQHxFVujPXkqPpLWEXyx.2lFvlyVEKcB1pENdrrScHxVkVRiM6 vZAh7BLhcgfMzVG9olqlWRINyx8mIcEGHxr6b95us1CeuQ._oKoV2zccpl6QW.ymLe0D.XSR8IsB NekP5KahMJs6P2om0aVdHmuK3l9Xo8c0YwuagxILXKuzKN.a_m5Vk4qye3zbYWPQ9c59Jz4JAPFn jQztvNoXHLzPdfsA1Oonf_DpNdwjMPuRngevTurlRYfuumd7cR2j6MURzL1xe_hU_uXJGb_1Y.W9 5wqKsycDn5hJU.SrZ7ocqgssftGqiNc9bbL2yXvZBiEidlqPRNGUHa9hcoF3SjjRHSeBscZkiyMf RvYGwrMWjWf8vZpoGr18IPCN9t2w837cNaX2o6dGDCWGbW2tE9Qir5CXAz1y47uWpfF1QaIVGuGq OVgl_5CvbYRMBmpY8qZ4FeqBc_X7Y7Kfa0.d8sUmoehtvaN7iDS4g9bn0vgtlkff2U3YbQDsPCKn H14ndOkpLCtAM6t3_njj1mpU5pfSsk7VoFmWvXqUIEnGt4Y1yfmVpsgvFWEwIjjiSCbDGG9aV9Ij hZo84T0ePfKhlRq74o5khBpakH_1FTwY_zXI.kBf9GzvG4fyolBXc.P0tH6ckajLIPkBV.pDCqHz ONoOjgNdLWP9L..ruDlJg8XG1BV3x0rim6hdR5OZtqo4YL9L3KeLXc_6hivYA8kOEgB59ic.iVVv IQoN.JNXQiUnWgkPG68eRB5QdSSXcC5oSb2w4R4pnNd4ysIy0TsUofmsCWULD8O4o6NJodzxJDZc s7gG_0BkKTMO9eXtfSLo62k5ISLHjaB2cqCm1x2hu3fQdDPjBo5kFTC2q_rG4OSSBb0ZDvsb3yop p_4QVB7VVw5IXkifievQTk.Pks.9t4RoxiUxgrEAeDDJJz07Fb_yPaVbNoeBLZ5KHI1XVq0F0kY2 8RKTMNvxHESn6JnufG.F2ZhBF6sqHeDYDlBrjyczrSZMV0XChyjRtw.2oePmW9bzv.BZ.jte8jXO .qLZ772Iwi1QJxL__QL1j5LV81eolFFLSEMbxUlT_yDJy5LeSUlFzxo.Asp4qCXWVGRxGObkBE71 Y8MOxdYcBHzjuriVCUJiVjRmL2tcELVz4GD7SKkxNW3LYQpXQ0x2Qh7tI4iX7DjeUXZOtzH.BhDJ RgNvhx7oAg.w224MYxyFbUsr.5Q8a33cHHWJZccn4MppJA_GimiRkucDDep1IQ9ftIparDa1D1Kq uJav59Foj6VVKfY.yB_l_iM45PnJWvctrc7EH45ZYSwkK.BWZTyrCt3XqM7WVWPhPZH_hzVZDiBD g_Q1HgteJGAwKUEoixuQ6OGJFzemKdujkpnz9B9RNIaV6RlchSxxl1dydhoMIar08OMJR88HjcyR AaneqmJZ1gM4ZjY5.ohe86vJ5mdkua8m6VA.h5u454JRcjod7O7TUiFrDAN7vfRqycOZ_R6205aT zS4p8HLj.U_nH_.MAi.1LhhkEB9E8zNnB.cQKoOte0YI_9gWA_7jQ2cA0DfPtYrvRP22nP.qBjzU GGakfi6fmXztC4f19O.JInahMAjab4W1s6L8mCjVgWMgWfa_rbDV7tbiBxjJN60SnT45ceDA2U_4 XfMQLq4TkJf_a9nxryeT3glbb.NJfaMtOvEqqNo1x_xlnnM3PKBLgfTNikF7Hb64XjZBtrak54zz vyUROBerMQbaoeri7prgNLXb2EVW1BdBu9uuFhmTvDvW9mxD6HUNsbN.1dpjiUyZMYB6vdxuGnt6 rbepL97IZHPfETDDHWa7zb6Cbgv84.3Oq00GKb.5PQs_pi4kbcA.MwyA1xm8.YHmn0ChEWg5G4fJ VXVrNw8ta6rlUMx536XjqX9LImlXYh8Knp3MdwKaZUItW_A7O85ACoplr40Em7RbpXCyQ9qA4toT NeqwGX90miseVH.OPBic1nn8_QMAgvK_8HjuBcU03zNLMVE.qlX9Ygs8n9eL8cfiNe7qVLH50WIr NwbF4vX4Hf0pGTYwwWjBZgWmVjURpY78QcC4K38dUIeZhcTvhsdAj3nLPDsmwJ3vwS4hSVjwSTyJ V X-Sonic-MF: X-Sonic-ID: c1020d3b-7825-4db4-8fda-c4aa3fd324aa Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.gq1.yahoo.com with HTTP; Mon, 17 Jul 2023 03:46:44 +0000 Received: by hermes--production-ne1-6d679867d5-8p72p (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 58927c5c2008f3f146cf299dc095a3f7; Mon, 17 Jul 2023 03:46:42 +0000 (UTC) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: rsync use with -tmsdosfs mounted file system? file has vanished: . . . From: Mark Millard In-Reply-To: Date: Sun, 16 Jul 2023 20:46:30 -0700 Cc: Current FreeBSD Content-Transfer-Encoding: quoted-printable Message-Id: <4B7DD1D6-00F8-436F-A107-2BFD970FAA01@yahoo.com> References: <485EB974-5EF4-4569-9B40-81A474983F33.ref@yahoo.com> <485EB974-5EF4-4569-9B40-81A474983F33@yahoo.com> To: Kevin Oberman X-Mailer: Apple Mail (2.3731.600.7) X-Rspamd-Queue-Id: 4R47LG49Byz3F0V X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Jul 16, 2023, at 18:17, Kevin Oberman wrote: > On Sun, Jul 16, 2023 at 1:57=E2=80=AFPM Mark Millard = wrote: >> I used a sequence that looked like: >>=20 >> mount -onoatime -tmsdosfs /dev/gpt/CA72optM2efi /CA72optM2efi-media/ = \ >> && rsync -x --delete -aAUHhh --info=3Dprogress2 /boot/efi/ = /CA72optM2efi-media/ >>=20 >> that got: >>=20 >> file has vanished: "/CA72optM2efi-media/BCM271~5.DTB" >> file has vanished: "/CA72optM2efi-media/BCM271~6.DTB" >> 73.77K 0% 1.63MB/s 0:00:00 (xfr#7, to-chk=3D0/493) = rsync warning: some files vanished before they could be transferred = (code 24) at main.c(1357) [sender=3D3.2.7] >>=20 >> After that, activity reported the likes of: >>=20 >> rsync: [generator] delete_file: unlink(overlays/VC4-KM~8.DTB) failed: = Read-only file system (30) >> and: >> rsync: [receiver] mkstemp "/CA72optM2efi-media/.fixup4.dat.2Wonu9" = failed: Read-only file system (30) >>=20 >> More than rsync was odd at that point: >>=20 >> # ls -Tld /CA72optM2efi-media/*.DTB >> ls: /CA72optM2efi-media/BCM271~5.DTB: No such file or directory >> ls: /CA72optM2efi-media/BCM271~6.DTB: No such file or directory >>=20 >> # rm /CA72optM2efi-media/*/*.DTB >> override rwxr-xr-x root/wheel uarch for = /CA72optM2efi-media/overlays/SDHOST~1.DTB? y >> rm: /CA72optM2efi-media/overlays/SDHOST~1.DTB: Read-only file system >> . . . >>=20 >> But: >>=20 >> # mount | grep media >> /dev/gpt/CA72optM2efi on /CA72optM2efi-media (msdosfs, local, = noatime) >>=20 >> So the mount itself was not the source of the read-only status so = far. >>=20 >> I then tried: >>=20 >> # umount /CA72optM2efi-media >> # newfs_msdos /dev/da0p1 >> # mount -onoatime -tmsdosfs /dev/gpt/CA72optM2efi /mnt >> # cp -aRx /boot/efi/ /mnt/ >> cp: utimensat: /mnt: Invalid argument >>=20 >> (which is normal). >>=20 >> # umount /mnt >>=20 >> No more oddities , so far after that. >>=20 >>=20 >> For reference: >>=20 >> # uname -apKU >> FreeBSD CA72-16Gp-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #99 = main-n264171-2a0c0aea4209-dirty: Fri Jul 14 21:00:44 PDT 2023 = root@CA72-16Gp-ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm6= 4.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400093 1400093 >>=20 >> # pkg info rsync >> rsync-3.2.7 >> Name : rsync >> Version : 3.2.7 >> Installed on : Sat Jul 15 14:53:48 2023 PDT >> Origin : net/rsync >> Architecture : FreeBSD:14:aarch64 >> . . . >> Annotations : >> FreeBSD_version: 1400092 >> build_timestamp: 2023-07-02T06:57:44+0000 >> built_by : poudriere-git-3.3.99.20220831 >> cpe : cpe:2.3:a:samba:rsync:3.2.7:::::freebsd14:aarch64 >> port_checkout_unclean: no >> port_git_hash : f45cd5bd9d4b >> ports_top_checkout_unclean: yes >> ports_top_git_hash: 880f72e54deb >=20 >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.co >=20 > This looks a bit like an issue I was hitting on a 4 CPU, 4 thread = Alder Lake processor and 500GB SSD running 13.2-RELEASE. >=20 > I saw several very strange corruptions, at least one "rsync warning: = some files vanished before they could be transferred". In one (the last) = case, the system crashed. The 'disc' was corrupted badly enough that = fsck failed and I could not boot up the system. The disk was UFS2 GPT = format and EFI boot. The interface is SATA, not nVME. In this case, I = was installing on a new system and copying the majority of the file = system from my old system.=20 >=20 > The 'fix' is strange and probably not one many other can use. I = installed a spinning rust drive of 500GB and installed FreeBSD and used = rsync again and it worked. I can't say whether it was a fluke that it = worked, but it really smells like some sort of race condition. Could be = rsync , VFS, or device driver. Since then I have seen one crash while = backing up the system disk using rsync. No corruption and doing another = rsync after reboot worked fine, but it was a much smaller run as the = first attempt was nearly complete when the system crashed. Maybe = unrelated. I do have the core file from the crash. Stil, something weird = has been going on. Same issue on two identical systems, so not likely = hardware. Adding background from my example, helping identify the variety of = contexts that sometimes the message: The target drive was a 894 GiByte USB3 drive, of all things a Optane U2 = used via a USB3 adapter. GPT. Per the mount that I showed: msdosfs partition, the = one that has FreeBSD's UEFI loader copy that would be used in booting. (In my = context, it also gets RPi* related boot materials to allow booting RPi4B's, a RPi3B, and = a RPi2B v1.2. There are directories used as holding areas for alternate RPi* = related materials (versions), the holding area for the ready-to-use materials = being empty at the time: the mterials are out where they would be used.) The booted world/kernel media was a PCIe Optane. Its msdosfs also has = the RPi* materials, despite the PCIe Optane not being bootable on an RPi* = configuration that I can form. These materials where what rsync was copying from. So = the rsync was between 2 msdosfs, not across file system types. aarch64 with 16 Cortex-A72 's and 64 GiBytes of RAM. main (so: 14). So a fair number of things are not in common with your examples, which = might at least help limit the range of potential answers to: "what all is common = to all the failures?". =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Mon Jul 17 14:51:04 2023 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 4R4Q4t5x6Cz4n1CT for ; Mon, 17 Jul 2023 14:51:10 +0000 (UTC) (envelope-from sm@codenetworks.net) Received: from relayout03-q02.dominioabsoluto.net (relayout03-q02.dominioabsoluto.net [217.116.26.244]) (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 4R4Q4s1r2vz3Lq2 for ; Mon, 17 Jul 2023 14:51:08 +0000 (UTC) (envelope-from sm@codenetworks.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=codenetworks.net header.s=domabs header.b=cU5OQQLO; spf=pass (mx1.freebsd.org: domain of sm@codenetworks.net designates 217.116.26.244 as permitted sender) smtp.mailfrom=sm@codenetworks.net; dmarc=none Received: from relayout03-redir.dominioabsoluto.net (relayout03-redir.dominioabsoluto.net [217.116.26.247]) by relayout03.dominioabsoluto.net (Postfix) with ESMTP id 4R4Q4n4xNmz1y0W; Mon, 17 Jul 2023 16:51:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codenetworks.net; s=domabs; t=1689605465; bh=DG+e+BcerJB2G2mFlYkM4Otf62rC64SfGMQq2jM5mA0=; h=Date:Subject:To:References:From:In-Reply-To:From; b=cU5OQQLO3EF2y4Te89Duf14WaNwCrDNxQOXOdSEFfTb3VUkvI6o8SI+oHpDsB9sz4 NKrXt5nSsYcfUlN3aGBL6/YLxBfVWlhJqHxTebA3+37y4P5+zcZ7WLw9Icavzaqjyf SAqvwsrfiRN+muh7/ZzuDdMHKJg4c4J9Sxt0SGkI= Received: from [192.168.3.100] (unknown [5.159.168.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sm.codenetworks.net) by relayout03-dsp.dominioabsoluto.net (Postfix) with ESMTPSA id 4R4Q4n03sRz1y0W; Mon, 17 Jul 2023 16:51:04 +0200 (CEST) Message-ID: <37faf1c5-d991-0abc-d70f-f1653d2da0ce@codenetworks.net> Date: Mon, 17 Jul 2023 16:51:04 +0200 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: huge amount laundry memory not being cleaned up Content-Language: en-US To: Pete Wright , Olivier Certner , freebsd-current@freebsd.org References: <3394311.dRNa8Ay4eR@ravel> From: Santiago Martinez In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-PostalOut-Country: IP: 5.159.168.225 | Country: ES X-PostalOut-Information: AntiSPAM and AntiVIRUS on relayout03 X-PostalOut-MsgID: 4R4Q4n03sRz1y0W.A1DCA X-PostalOut-SpamCheck: no es spam, clean X-PostalOut-From: sm@codenetworks.net X-PostalOut-Watermark: 1690210265.53746@7rHvhpo7bbdakm4DsrCvAQ X-Spam-Status: No X-Spamd-Result: default: False [-3.90 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; RWL_MAILSPIKE_VERYGOOD(-0.20)[217.116.26.244:from]; R_SPF_ALLOW(-0.20)[+ip4:217.116.26.0/24]; RCVD_IN_DNSWL_LOW(-0.20)[217.116.26.244:from,217.116.26.247:received]; R_DKIM_ALLOW(-0.20)[codenetworks.net:s=domabs]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_TO(0.00)[nomadlogic.org,free.fr,freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:16371, ipnet:217.116.24.0/21, country:ES]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[codenetworks.net:+]; RCPT_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[codenetworks.net]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4R4Q4s1r2vz3Lq2 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Hi Pete, I run into the same issue around 4 weeks ago. This was with 13.2-p0. Been using the same setup for a few years and it the first time it happens to "run out of memory". The blame was also for plasmashell. Santi On 7/11/23 19:43, Pete Wright wrote: > > > On 7/11/23 10:37 AM, Olivier Certner wrote: >> Le mardi 11 juillet 2023, 01:51:02 CEST Pete Wright a écrit : >>> sorry for the noise folks, this is almost certainly an issue with my >>> local env.  this is helpful for me, as i'll have a better idea as to >>> where i should focus my efforts trying to find this memory hog next >>> time. >> >> I have had what I suspect to be the same issue on 13.2-STABLE with >> KDE and very long sessions.  I say "suspect" since I seem to remember >> that laundry usage went down by unlogging (or restarting kwin or >> plasmashell), but I'm not completely sure now. >> >> So may not be specific to your local env after all, nor to CURRENT. >> >> Regards. >> > > oh interesting.  i've found myself having to restart plasma once a > week or so to fix some glitches with the tool bar.  i just run: > > kquitapp5 plasmashell && kstart5 plasmashell > > so it's certainly possible thats where the issue lies.  i'd try > another window manager, but i really like plasma5 lol. > > maybe i'll take one for the team and run mate or xfce for a few weeks > and see if see similar behavior. > > -pete > > From nobody Tue Jul 18 23:59:12 2023 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 4R5GBp4TcHz4nQDT for ; Tue, 18 Jul 2023 23:59:14 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R5GBp43X3z3mKc for ; Tue, 18 Jul 2023 23:59:14 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689724754; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lb+mCIlroU0QgnVtXbfWZpXvblzhiBDCSu19eDgL/bc=; b=dSfxApUW+S62GQ4xynF/O7x7J3PMTBoNZqD0v8DWxbnx5dByvmTFzIf7p8JWAbyEWFvDcU KH7oqqhdorhBWZyDrHnc/lNi8/j3jd62Cvh9zScPkjzbv5/LGepcxdPh48+tK61dM5Z+LY T1JszV3hkDnY14zMNnYQbLhnzV8AXivQ7G8emDDXrac6GcbAvxpH54FR8YeYzHiFfFOdAN C8mr88HVBQ+BJquonJeBeC7lMIQUBnCeqPnQRlXWYiKeT6gZnVsVsSwXni15NrOUeQsmy8 8XRUPGkMXU9Ek5q6nt/Lp3ERVNbMJ10wKmJcXp9kSoap3Xk0dkb6+2v/aSMcVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689724754; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lb+mCIlroU0QgnVtXbfWZpXvblzhiBDCSu19eDgL/bc=; b=uqyRRqScZ22Fzhv3x0G7oyU+JjlVs2EiNTmIqhwCpedS+BDo1UGGmv9LE4qMfVTFAr40Ej QfGO7uaw9yyqn/8hlfzOIipJqhOzGlfFMD2W6XktQNEGeARC8qdElXhtoKtkayDxedHdO0 mpTojxrSWOgmeqBsYfhyXMoQsa3JywHwT/aH4VMJAszQSrQCAiSLB0KcFHNDhK1r1TRB4f zqoyndQ7lB4Zox5K5Vg86TSpytD2BDEPNW3p42fqh+Y6qNXyJ4Mthr2TvWBDOOkMBc17Ux UuckUfUSr67eTbyiwHrRLvuQLBLsTv0SmppYLNBVBy9Jy68ezakNqZsoOSwe3Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1689724754; a=rsa-sha256; cv=none; b=wp5JsZchs3J0kUpkO7EZ2t4WiVyI3Fmlumx2E/tjZaakurIpU4MpKH4KGhnhB3YEEzHTL8 id1AXZEiWn19qwqX2aVdOoE30kaz8btP0fJ21hSBI6BQ3OTXqan9crIXpz0/vYULlWcWHI vdGC44JhWkxOdmqsYAxs9xS3AdERERhiE7L6O8ksRf3MlTXys8gZr/v9hn5bGc4WH2kQZE WYj9bG0HovjWArc9CHbe+zT8r7ZuGDqKXLUhzH7vy3C1ECHxNovYRr8PR7nC4p3ZrrDO2J smkpBKv8ODMXP5dq125LjnRinX8oxN7IEzWyM/g3hx8wfyU+bX4LKUNfh81xBg== Received: from [192.168.1.10] (80-42-66-93.dynamic.dsl.as9105.com [80.42.66.93]) (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 did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4R5GBp1jrrzjBN for ; Tue, 18 Jul 2023 23:59:14 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <8dbeb710-6e4b-f0aa-d54a-43bba1a9254f@freebsd.org> Date: Wed, 19 Jul 2023 00:59:12 +0100 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: kernel: sonewconn: pcb 0xfffff8002b255a00 (local:/var/run/devd.seqpacket.pipe): Listen queue overflow: 1 already in queue awaiting acceptance (60 occurrences), ? Content-Language: en-US From: Graham Perrin To: freebsd-current@freebsd.org References: <3567b4c0-8143-67c8-fde7-5ae3923f53f4@freebsd.org> <20230620094108.351849f5@ernst.home> <20230620120413.Horde.E7_jFO0w9ui-Nbkh9PONJjn@webmail.leidinger.net> <20230620164141.209ea8bc@ernst.home> Organization: FreeBSD In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------n2X0T4czbQ6O08AFuuzc27y2" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------n2X0T4czbQ6O08AFuuzc27y2 Content-Type: multipart/mixed; boundary="------------ehsKm4f0GNtOCTnj9mH6It4P"; protected-headers="v1" From: Graham Perrin To: freebsd-current@freebsd.org Message-ID: <8dbeb710-6e4b-f0aa-d54a-43bba1a9254f@freebsd.org> Subject: Re: kernel: sonewconn: pcb 0xfffff8002b255a00 (local:/var/run/devd.seqpacket.pipe): Listen queue overflow: 1 already in queue awaiting acceptance (60 occurrences), ? References: <3567b4c0-8143-67c8-fde7-5ae3923f53f4@freebsd.org> <20230620094108.351849f5@ernst.home> <20230620120413.Horde.E7_jFO0w9ui-Nbkh9PONJjn@webmail.leidinger.net> <20230620164141.209ea8bc@ernst.home> In-Reply-To: --------------ehsKm4f0GNtOCTnj9mH6It4P Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMjEvMDYvMjAyMyAwMToyOSwgR3JhaGFtIFBlcnJpbiB3cm90ZToNCj4NCj4g4oCmIFRo YW5rcywgcGVvcGxlLg0KPg0KPiBBIGZldyBob3VycyBhZ28gSSB0b29rIGEgaGludCBmcm9t IG9uZSBvZiB0aGUgcGFnZXMgbGlua2VkIGZyb20gDQo+IDxodHRwczovL2Rhbi5sYW5naWxs ZS5vcmcvMjAyMC8wMS8wMS9saXN0ZW4tcXVldWUtb3ZlcmZsb3cvPiwgYWRkZWQgYSANCj4g bGluZSB0byBteSBzeXNjdGwuY29uZig1KS4NCj4NCj4g4oCmDQo+ICUgZ3JlcCBpcGMgL2V0 Yy9zeXNjdGwuY29uZg0KPiBrZXJuLmlwYy5zb2FjY2VwdHF1ZXVlPTI1Ng0KPiAlDQo+DQpJ IGZvdW5kIG5vIGltcHJvdmVtZW50IGZyb20gdGhhdC4gSUlSQyBJIGFsc28gdHJpZWQgNTEy Lg0KDQo= --------------ehsKm4f0GNtOCTnj9mH6It4P-- --------------n2X0T4czbQ6O08AFuuzc27y2 Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmS3J1AFAwAAAAAACgkQt2dIb0oY1Ask CA/9Hj2Ks6G8E5GWBvh+37dCbuBwje5TeFWATPmqFztiGRSIiIQ09I7X3d09CZdjs4RY5PteCMhm BuW8ev/prAzre7khqO9Mt5/2egA9W+vEElaAG4Vy1aFLSOgx/N1auVSyWQqzl6hoSCRhCl5aQdKt o+pnEgaZQk37XhpwuwgfQMdoen4YtTuoNuvIGnoixRmhvw5vRjTHuV02lQPvtysc3HLfZ4AUB/9u aMar6n1NjWaALJSqw6C5zdq213KwNP6quMAAqFWVpdQmkNGnIWuEPwArkY+CtJzw0zpRfHGq5VIo mNZt7q/ukqWi7g2T+tcujnb/w7+pG9/ES/JiX76HKTAXRxsMPj12nkFYKtwZc2f54q6Tm/3YvhOb tzZ/zFcpypUpDtpzvImiA68PW8sobs1IbvqKqnryrgGojtHhKmcamoDg6EUvfJMMeKFVE3As/6Br 0HwjBqYidtvq/AME3F+Ws8utZWdqoJA0/AXRz80+6J/aRecDVoxQwmcBukboLyd6EVCN5vNQIDAg BPm+N+fEQTpXCOq+nZV8OvxWYMp1wkB6cAYtueS0pZSfN0ceoBP9LdBIGKAm2LRH7/h55qYSNfj8 8xXdzLEEyZxASBd68rybrJZ8u4dw7DC7rsNN3Dbm09X9Qtwi8eb+9h1btFbz8+cWYgGQB2uecHMq KeE= =lm10 -----END PGP SIGNATURE----- --------------n2X0T4czbQ6O08AFuuzc27y2-- From nobody Thu Jul 20 19:27:39 2023 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 4R6N4Z21gHz4nbP1 for ; Thu, 20 Jul 2023 19:27:42 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R6N4Y4Smcz4Djg for ; Thu, 20 Jul 2023 19:27:41 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=karels.net header.s=mail2 header.b=puExlE3w; spf=pass (mx1.freebsd.org: domain of mike@karels.net designates 3.19.118.201 as permitted sender) smtp.mailfrom=mike@karels.net; dmarc=none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTP id 36KJReiL048094 for ; Thu, 20 Jul 2023 14:27:40 -0500 (CDT) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1689881260; bh=kHJ4pYi/pSoyw4FjSO3dqBMb8C0cbrXkyHC3fAzpMaw=; h=From:To:Subject:Date; b=puExlE3w2aEQFLjAyXSlebMisuXezi0epQWUJq8OVXMW6Ikiejgk5qlInFhp4Rrc0 HgsTEKMIv0MPafQNnMkCJ5Kd6LIB0CYi7yeCTjC8lfYtLCZInIP5IHG93R0uk0jLHW 0z+hnaY5vjolEoE3g0k93k6t7I4wqCa46wY//rXys02WnjdZY4b/MiS1tNcMSZcPHL st7Tfmyw5MyKUSbK10fPfyxy9BNsPEKUr4+kuZkRDL2q5sYR+2wPNWh6prspVUE68J Csj/2vmmSn75YdTjJoUClvYAvkKmHonAmB0+fk9I3HW+lOEvlP+Klq1+nZAOSEq8l2 EKH6TgmbrsNEQ== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id HFC2JayKuWTcuwAAs/W3XQ (envelope-from ) for ; Thu, 20 Jul 2023 14:27:40 -0500 From: Mike Karels To: Current FreeBSD Subject: confusion about root partition causes panic during startup Date: Thu, 20 Jul 2023 14:27:39 -0500 X-Mailer: MailMate (1.14r5964) Message-ID: <120E9843-2732-4D2D-A23D-CB608F199E84@karels.net> 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 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; R_MISSING_CHARSET(0.50)[]; R_DKIM_ALLOW(-0.20)[karels.net:s=mail2]; R_SPF_ALLOW(-0.20)[+ip4:3.19.118.201]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[karels.net:+]; BLOCKLISTDE_FAIL(0.00)[3.19.118.201:server fail,73.62.165.147:server fail]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[mike]; ARC_NA(0.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[karels.net]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4R6N4Y4Smcz4Djg X-Spamd-Bar: -- I installed an additional NVME drive on a system, and then booted. It tu= rns out that the new drive became nda0, renumbering the other drives. The lo= ader found the correct partition to boot (the only choice), and loaded the ker= nel correctly. However, /etc/fstab still had the old name (nvd1p2), which is= now drive 2. I expected it to drop into single user, but instead the sys= tem panicked in vfs_mountroot_shuffle trying to switch root devices (see belo= w). It doesn't seem that having the wrong root device in /etc/fstab should ca= use a panic; it makes it harder to patch the system. I was unable to get the= system to boot using boot-to-single-user or setting currdev, but I manage= d to remember doing "boot -a" from a loader prompt to get the system to ask= the root device before mounting it. I can easily reproduce this to test.= Probably the NDFREE_PNBUF() shouldn't happen if namei() returned an error= =2E Mike Trying to mount root from ufs:/dev/nvd1p2 [rw]... WARNING: WITNESS option enabled, expect reduced performance. mountroot: unable to remount devfs under /dev (error 2) panic: Assertion _ndp->ni_cnd.cn_pnbuf !=3D NULL failed at ../../../kern/= vfs_mountroot.c:416 cpuid =3D 19 time =3D 11 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe006d3= bac40 vpanic() at vpanic+0x149/frame 0xfffffe006d3bac90 panic() at panic+0x43/frame 0xfffffe006d3bacf0 vfs_mountroot() at vfs_mountroot+0x1bf7/frame 0xfffffe006d3bae60 start_init() at start_init+0x23/frame 0xfffffe006d3baef0 fork_exit() at fork_exit+0x82/frame 0xfffffe006d3baf30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe006d3baf30 --- trap 0x5c035c02, rip =3D 0x680c680c680c680c, rsp =3D 0x1b6b1f6b1b6b1b= 6b, rbp =3D 0x4eb54eb54eb54eb5 --- KDB: enter: panic [ thread pid 1 tid 100002 ] Stopped at kdb_enter+0x32: movq $0,0xde7643(%rip) From nobody Thu Jul 20 19:31:01 2023 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 4R6N8h0mTcz4nd9R for ; Thu, 20 Jul 2023 19:31:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R6N8g5xSNz4GG5 for ; Thu, 20 Jul 2023 19:31:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-51cff235226so2593830a12.0 for ; Thu, 20 Jul 2023 12:31:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1689881472; x=1690486272; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=E+vPetezX70RF5FqZsa/x67igaYoTKxPS7Pw7yoGnSs=; b=fEI0ZiGRqK3BXcmd696+9czT7Fp2BHMVuAoiO0D3rncTzClZlKa2/P8+1MhroLA0hm UPrq8OIUSxc3kKxrCDPq7Wg2E0MUbn0Q330yTR2wLc1Dor/uW7Op+CYSU6fVBIWRpEiL mO1jAy/6UMl4jlrhCrtAAZwWHdl0PKp/ke6F3lIhfVo3RpQPvSRwxe+yu506p4/ibC+K gp3qe1TNfXwXO+77we3oQc4RcHBpO/1Qti2riDMKGHyBHKBpmhxve9Hd2y16nrvc2zrn HSGJ3MTmfzrrpCv1OK5rm63eeCZY19oIFezIBWHU3iJwIQnpUDpGjL3vPC2zULgDeE9x dxxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689881472; x=1690486272; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=E+vPetezX70RF5FqZsa/x67igaYoTKxPS7Pw7yoGnSs=; b=MBL6Fcrhcv7EGWWsLMAvwct1PUsOS7aMJhRz10WkG7zIGXhnmcj4TWoGiXaY1Kvnr3 X7ZTWPVjWq3RVbzsUzgXoiicLTQGBe1UXYGcxuYZHNyEbaYGdfGVeG9xNuS2Im2PZKx6 1Jz9I+MoxaJ8cAgWDWW2I+/bjpHvLvgQT5vwlJ57LPltY876RvpkAFsY5OjKfSzXplpP AooY54kUH2ut+NXSUDX1As1YKZImtBwk1ttd92GIW62EleHIc8DLiXwTwFZ46xPiXcSc WJfXoydqQeFYW3GP5lriMBRHMKiVYM87ErwqmacAywlyA3algxL1j9DlPlfOc0Z2GHQX ZZ7w== X-Gm-Message-State: ABy/qLagjjt8apKeWN86RlcvTACdVTu/GtB5tq6rwLmcGapiIWXyb/GO bNB3JOoMLV2qXu3sjSp91H9AQ66XFVNjsInQbPT9Kw== X-Google-Smtp-Source: APBJJlEGdDEy54i+P4xqfyCBjnq2wAnOb1QCOiGvAb53om+fiH5zTQABl4w6+nc0gSdBjs3GBQzX7u+ADWlLLhimu24= X-Received: by 2002:aa7:dac4:0:b0:51e:da3:1585 with SMTP id x4-20020aa7dac4000000b0051e0da31585mr7323210eds.9.1689881472334; Thu, 20 Jul 2023 12:31: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: <120E9843-2732-4D2D-A23D-CB608F199E84@karels.net> In-Reply-To: <120E9843-2732-4D2D-A23D-CB608F199E84@karels.net> From: Warner Losh Date: Thu, 20 Jul 2023 13:31:01 -0600 Message-ID: Subject: Re: confusion about root partition causes panic during startup To: Mike Karels Cc: Current FreeBSD Content-Type: multipart/alternative; boundary="000000000000df147a0600f03010" X-Rspamd-Queue-Id: 4R6N8g5xSNz4GG5 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated --000000000000df147a0600f03010 Content-Type: text/plain; charset="UTF-8" On Thu, Jul 20, 2023, 1:27 PM Mike Karels wrote: > I installed an additional NVME drive on a system, and then booted. It > turns > out that the new drive became nda0, renumbering the other drives. The > loader > found the correct partition to boot (the only choice), and loaded the > kernel > correctly. However, /etc/fstab still had the old name (nvd1p2), which is > now drive 2. I expected it to drop into single user, but instead the > system > panicked in vfs_mountroot_shuffle trying to switch root devices (see > below). > It doesn't seem that having the wrong root device in /etc/fstab should > cause > a panic; it makes it harder to patch the system. I was unable to get the > system to boot using boot-to-single-user or setting currdev, but I managed > to remember doing "boot -a" from a loader prompt to get the system to ask > the root device before mounting it. I can easily reproduce this to test. > Probably the NDFREE_PNBUF() shouldn't happen if namei() returned an error. > > Mike > > Trying to mount root from ufs:/dev/nvd1p2 [rw]... > WARNING: WITNESS option enabled, expect reduced performance. > mountroot: unable to remount devfs under /dev (error 2) > panic: Assertion _ndp->ni_cnd.cn_pnbuf != NULL failed at > ../../../kern/vfs_mountroot.c:416 > cpuid = 19 > time = 11 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe006d3bac40 > vpanic() at vpanic+0x149/frame 0xfffffe006d3bac90 > panic() at panic+0x43/frame 0xfffffe006d3bacf0 > vfs_mountroot() at vfs_mountroot+0x1bf7/frame 0xfffffe006d3bae60 > start_init() at start_init+0x23/frame 0xfffffe006d3baef0 > fork_exit() at fork_exit+0x82/frame 0xfffffe006d3baf30 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe006d3baf30 > --- trap 0x5c035c02, rip = 0x680c680c680c680c, rsp = 0x1b6b1f6b1b6b1b6b, > rbp = 0x4eb54eb54eb54eb5 --- > KDB: enter: panic > [ thread pid 1 tid 100002 ] > Stopped at kdb_enter+0x32: movq $0,0xde7643(%rip) > I'll have to see if I can recreate this. I've been running this way for a long time... Warner > --000000000000df147a0600f03010 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jul 20, 2023, 1:27 PM Mike Karels <mike@karels.net> wrote:
I installed an additional NVME drive on a system, a= nd then booted.=C2=A0 It turns
out that the new drive became nda0, renumbering the other drives.=C2=A0 The= loader
found the correct partition to boot (the only choice), and loaded the kerne= l
correctly.=C2=A0 However, /etc/fstab still had the old name (nvd1p2), which= is
now drive 2.=C2=A0 I expected it to drop into single user, but instead the = system
panicked in vfs_mountroot_shuffle trying to switch root devices (see below)= .
It doesn't seem that having the wrong root device in /etc/fstab should = cause
a panic; it makes it harder to patch the system.=C2=A0 I was unable to get = the
system to boot using boot-to-single-user or setting currdev, but I managed<= br> to remember doing "boot -a" from a loader prompt to get the syste= m to ask
the root device before mounting it.=C2=A0 I can easily reproduce this to te= st.
Probably the NDFREE_PNBUF() shouldn't happen if namei() returned an err= or.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mike

Trying to mount root from ufs:/dev/nvd1p2 [rw]...
WARNING: WITNESS option enabled, expect reduced performance.
mountroot: unable to remount devfs under /dev (error 2)
panic: Assertion _ndp->ni_cnd.cn_pnbuf !=3D NULL failed at ../../../kern= /vfs_mountroot.c:416
cpuid =3D 19
time =3D 11
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe006d3ba= c40
vpanic() at vpanic+0x149/frame 0xfffffe006d3bac90
panic() at panic+0x43/frame 0xfffffe006d3bacf0
vfs_mountroot() at vfs_mountroot+0x1bf7/frame 0xfffffe006d3bae60
start_init() at start_init+0x23/frame 0xfffffe006d3baef0
fork_exit() at fork_exit+0x82/frame 0xfffffe006d3baf30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe006d3baf30
--- trap 0x5c035c02, rip =3D 0x680c680c680c680c, rsp =3D 0x1b6b1f6b1b6b1b6b= , rbp =3D 0x4eb54eb54eb54eb5 ---
KDB: enter: panic
[ thread pid 1 tid 100002 ]
Stopped at=C2=A0 =C2=A0 =C2=A0 kdb_enter+0x32: movq=C2=A0 =C2=A0 $0,0xde764= 3(%rip)


I'll have to see if I can recreate t= his. I've been running this way for a long time...

Warner
--000000000000df147a0600f03010-- From nobody Thu Jul 20 21:13:31 2023 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 4R6QQm07q0z4nPSY for ; Thu, 20 Jul 2023 21:13:36 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oa1-x35.google.com (mail-oa1-x35.google.com [IPv6:2001:4860:4864:20::35]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R6QQl4x7Yz3nVC for ; Thu, 20 Jul 2023 21:13:35 +0000 (UTC) (envelope-from mjguzik@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-1b060bce5b0so960336fac.3 for ; Thu, 20 Jul 2023 14:13:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689887613; x=1690492413; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=eGLEJb4him2NXmWDv285L/PbhQsB9LSfZTUcvUXk1hw=; b=iTRsxiPUIEaVFeiawTy0gCOGHd6g+OO0gQ1S4qgTkdxo1gorPei8du5ZBUGL762xKT hWs4iChXEz/xYqWw4bLQVDvpQrKe7R5S8kTTr08qhCKoCOH4TPtNLVKl+kOSPKphda96 U1qnJ+AtgRdO80V5ReQwmFjU6758CE7k1MtxPE0cTOKX06w0Lf+9PcfhaOXnuCY89q7b ltl4T12O34x+EQu6L0+EYuiVXzN7unNchf2xP5T3sR5OGlXyzQhrm3QQLlrKxfEeHljz N/EK+PjAVSohnCgx0VIfPPz1qwudXTMRaOGaG8AFv7xKf0NtJe/SHtNOEYOc9csiOB2p 5foA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689887613; x=1690492413; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=eGLEJb4him2NXmWDv285L/PbhQsB9LSfZTUcvUXk1hw=; b=JNEZ7eDKiZUOGm03LcjR6EZYQ76g3w4U5nmWNNTClTV6WxY4vzBkzuWlwq8F9T8kI5 1trzBq7R6dJvUc/vuJCU1eu0G6Y8QaZHS49DMuaSz6NQ+1phGExZR6fMr0fhORE/SfBv KZLno9Xb37VRjrh0TvFFXZteFKAbcHNF+gmE5tBxwu9Y1/pnGEBl91ZSW4UHIjfD5NRg X1zbRis4qsk4ynRNq1m+JV8oE5ecUlH29M+Er7A6PQnsjLbeXgxgN03WrK8uotKuJHEW xCkdlD3L82nB+HpjHISX79Zv23+0xiL/jL9kDRK/DMiWMJevowElofjnhzUFKmCQyRGc KyFw== X-Gm-Message-State: ABy/qLY5uGfiOF89f9UXGjA8v+wR4QeMVzzE5GiURFu4aR3n/DuuEDGD Jdd7FVgaYbt2i9thWUhciayFDfd26rCBovwpLjUaGb1V X-Google-Smtp-Source: APBJJlFs4Z/qyfhg2hCADGod7zRPWdqJxH7y8IUAvzoxfL2r2mN1pJbJAT1iw6z15JnXYPCDZT8hJXWo526aoN9F5tU= X-Received: by 2002:a05:6870:910d:b0:1ba:989b:ca65 with SMTP id o13-20020a056870910d00b001ba989bca65mr582348oae.19.1689887612476; Thu, 20 Jul 2023 14:13:32 -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 Received: by 2002:a8a:1198:0:b0:4e1:6042:cdc9 with HTTP; Thu, 20 Jul 2023 14:13:31 -0700 (PDT) In-Reply-To: <120E9843-2732-4D2D-A23D-CB608F199E84@karels.net> References: <120E9843-2732-4D2D-A23D-CB608F199E84@karels.net> From: Mateusz Guzik Date: Thu, 20 Jul 2023 23:13:31 +0200 Message-ID: Subject: Re: confusion about root partition causes panic during startup To: Mike Karels Cc: Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4R6QQl4x7Yz3nVC X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On 7/20/23, Mike Karels wrote: > I installed an additional NVME drive on a system, and then booted. It > turns > out that the new drive became nda0, renumbering the other drives. The > loader > found the correct partition to boot (the only choice), and loaded the > kernel > correctly. However, /etc/fstab still had the old name (nvd1p2), which is > now drive 2. I expected it to drop into single user, but instead the > system > panicked in vfs_mountroot_shuffle trying to switch root devices (see > below). > It doesn't seem that having the wrong root device in /etc/fstab should > cause > a panic; it makes it harder to patch the system. I was unable to get the > system to boot using boot-to-single-user or setting currdev, but I managed > to remember doing "boot -a" from a loader prompt to get the system to ask > the root device before mounting it. I can easily reproduce this to test. > Probably the NDFREE_PNBUF() shouldn't happen if namei() returned an error. > ye, this should do it (untested): diff --git a/sys/kern/vfs_mountroot.c b/sys/kern/vfs_mountroot.c index 956d29e3f084..85398ff781e4 100644 --- a/sys/kern/vfs_mountroot.c +++ b/sys/kern/vfs_mountroot.c @@ -352,13 +352,13 @@ vfs_mountroot_shuffle(struct thread *td, struct mount *mpdevfs) NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, fspath); error = namei(&nd); if (error) { - NDFREE_PNBUF(&nd); fspath = "/mnt"; NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, fspath); error = namei(&nd); } if (!error) { + NDFREE_PNBUF(&nd); vp = nd.ni_vp; error = (vp->v_type == VDIR) ? 0 : ENOTDIR; if (!error) @@ -376,7 +376,6 @@ vfs_mountroot_shuffle(struct thread *td, struct mount *mpdevfs) } else vput(vp); } - NDFREE_PNBUF(&nd); if (error) printf("mountroot: unable to remount previous root " @@ -387,6 +386,7 @@ vfs_mountroot_shuffle(struct thread *td, struct mount *mpdevfs) NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, "/dev"); error = namei(&nd); if (!error) { + NDFREE_PNBUF(&nd); vp = nd.ni_vp; error = (vp->v_type == VDIR) ? 0 : ENOTDIR; if (!error) > Mike > > Trying to mount root from ufs:/dev/nvd1p2 [rw]... > WARNING: WITNESS option enabled, expect reduced performance. > mountroot: unable to remount devfs under /dev (error 2) > panic: Assertion _ndp->ni_cnd.cn_pnbuf != NULL failed at > ../../../kern/vfs_mountroot.c:416 > cpuid = 19 > time = 11 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe006d3bac40 > vpanic() at vpanic+0x149/frame 0xfffffe006d3bac90 > panic() at panic+0x43/frame 0xfffffe006d3bacf0 > vfs_mountroot() at vfs_mountroot+0x1bf7/frame 0xfffffe006d3bae60 > start_init() at start_init+0x23/frame 0xfffffe006d3baef0 > fork_exit() at fork_exit+0x82/frame 0xfffffe006d3baf30 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe006d3baf30 > --- trap 0x5c035c02, rip = 0x680c680c680c680c, rsp = 0x1b6b1f6b1b6b1b6b, rbp > = 0x4eb54eb54eb54eb5 --- > KDB: enter: panic > [ thread pid 1 tid 100002 ] > Stopped at kdb_enter+0x32: movq $0,0xde7643(%rip) > > -- Mateusz Guzik From nobody Fri Jul 21 02:37:45 2023 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 4R6Ycr107lz4nPmX for ; Fri, 21 Jul 2023 02:37:48 +0000 (UTC) (envelope-from mike@mail2.karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R6Ycp4tzMz4RWC for ; Fri, 21 Jul 2023 02:37:46 +0000 (UTC) (envelope-from mike@mail2.karels.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=karels.net header.s=mail2 header.b=lGsQ3ESl; spf=none (mx1.freebsd.org: domain of mike@mail2.karels.net has no SPF policy when checking 3.19.118.201) smtp.mailfrom=mike@mail2.karels.net; dmarc=none Received: from mail2.karels.net (localhost [127.0.0.1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTPS id 36L2bjjM049892 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 20 Jul 2023 21:37:45 -0500 (CDT) (envelope-from mike@mail2.karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1689907065; bh=Q5Hznyb7fMiIkroRdiyiLaNdDB5nvgQ3W/d4Ia9nXGw=; h=To:cc:From:Reply-to:Subject:In-reply-to:Date; b=lGsQ3ESlR6GtTlKRO5CXmHxDK0ut0OGoMCs5N9Ag76Sodw42RkriNK0A0CPkAkXKm 4sJDoKorco4NGK3x0B4ip2vs1AWEMx3En8ucvL/QqBTMbIQt3+w5p6oxiLpZ5eNdfZ iK3GPZaYyrmnPXdNM4l10tS4DmE1TvEfYwYdxmzSqTwXcJb27ovvcha1dg78xfflgj tK+OILsztpd5BlDcHoLRgTSOSoFBqzT3AiZnz0RRW/owj+aljHIrERJqcGG+CJ/1Wt mBoTi+WBdYDLhNP8gwbxFZG342M/uZRauNV5L6SNVXwdWV4u91iDOKu7o+UNqlFLzo r9OPYciSTRLzg== Received: (from mike@localhost) by mail2.karels.net (8.17.1/8.17.1/Submit) id 36L2bjqk049891; Thu, 20 Jul 2023 21:37:45 -0500 (CDT) (envelope-from mike) Message-Id: <202307210237.36L2bjqk049891@mail2.karels.net> To: Mateusz Guzik cc: Current FreeBSD From: Mike Karels Reply-to: mike@karels.net Subject: Re: confusion about root partition causes panic during startup In-reply-to: Your message of Thu, 20 Jul 2023 23:13:31 +0200. 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-ID: <49889.1689907065.1@mail2.karels.net> Content-Transfer-Encoding: quoted-printable Date: Thu, 20 Jul 2023 21:37:45 -0500 X-Spamd-Result: default: False [-2.95 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.95)[-0.947]; FORGED_SENDER(0.30)[mike@karels.net,mike@mail2.karels.net]; R_DKIM_ALLOW(-0.20)[karels.net:s=mail2]; MIME_GOOD(-0.10)[text/plain]; FREEFALL_USER(0.00)[mike]; HAS_REPLYTO(0.00)[mike@karels.net]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[karels.net]; ARC_NA(0.00)[]; BLOCKLISTDE_FAIL(0.00)[3.19.118.201:server fail]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[mike@karels.net,mike@mail2.karels.net]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; REPLYTO_ADDR_EQ_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[karels.net:+]; MIME_TRACE(0.00)[0:+]; FREEMAIL_TO(0.00)[gmail.com]; R_SPF_NA(0.00)[no SPF record] X-Rspamd-Queue-Id: 4R6Ycp4tzMz4RWC X-Spamd-Bar: -- Mateusz Guzik wrote: > On 7/20/23, Mike Karels wrote: > > I installed an additional NVME drive on a system, and then booted. It > > turns > > out that the new drive became nda0, renumbering the other drives. The > > loader > > found the correct partition to boot (the only choice), and loaded the > > kernel > > correctly. However, /etc/fstab still had the old name (nvd1p2), which= is > > now drive 2. I expected it to drop into single user, but instead the > > system > > panicked in vfs_mountroot_shuffle trying to switch root devices (see > > below). > > It doesn't seem that having the wrong root device in /etc/fstab should > > cause > > a panic; it makes it harder to patch the system. I was unable to get = the > > system to boot using boot-to-single-user or setting currdev, but I man= aged > > to remember doing "boot -a" from a loader prompt to get the system to = ask > > the root device before mounting it. I can easily reproduce this to te= st. > > Probably the NDFREE_PNBUF() shouldn't happen if namei() returned an er= ror. > > > ye, this should do it (untested): > diff --git a/sys/kern/vfs_mountroot.c b/sys/kern/vfs_mountroot.c > index 956d29e3f084..85398ff781e4 100644 > --- a/sys/kern/vfs_mountroot.c > +++ b/sys/kern/vfs_mountroot.c > @@ -352,13 +352,13 @@ vfs_mountroot_shuffle(struct thread *td, struct > mount *mpdevfs) > NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, fsp= ath); > error =3D namei(&nd); > if (error) { > - NDFREE_PNBUF(&nd); > fspath =3D "/mnt"; > NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSP= ACE, > fspath); > error =3D namei(&nd); > } > if (!error) { > + NDFREE_PNBUF(&nd); > vp =3D nd.ni_vp; > error =3D (vp->v_type =3D=3D VDIR) ? 0 : ENOTDIR= ; > if (!error) > @@ -376,7 +376,6 @@ vfs_mountroot_shuffle(struct thread *td, struct > mount *mpdevfs) > } else > vput(vp); > } > - NDFREE_PNBUF(&nd); > if (error) > printf("mountroot: unable to remount previous ro= ot " > @@ -387,6 +386,7 @@ vfs_mountroot_shuffle(struct thread *td, struct > mount *mpdevfs) > NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, "/dev"); > error =3D namei(&nd); > if (!error) { > + NDFREE_PNBUF(&nd); > vp =3D nd.ni_vp; > error =3D (vp->v_type =3D=3D VDIR) ? 0 : ENOTDIR; > if (!error) That was missing the last change, and tabs were expanded. I put it in by hand, and the patch works, at least to avoid this panic. It still insisted on remounting root on nda1p2, which is not a root file system. Remounting /dev still failed without panicking, then it panicked because there was no /sbin/init. Apparently it is necessary to use "boot -a" in this situation. Too bad the loader option menu doesn't include that. Just to be clear what I tested, my patch follows. Mike diff --git a/sys/kern/vfs_mountroot.c b/sys/kern/vfs_mountroot.c index 956d29e3f084..b08b2a3200f8 100644 --- a/sys/kern/vfs_mountroot.c +++ b/sys/kern/vfs_mountroot.c @@ -352,13 +352,13 @@ vfs_mountroot_shuffle(struct thread *td, struct moun= t *mpdevfs) NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, fspath); error =3D namei(&nd); if (error) { - NDFREE_PNBUF(&nd); fspath =3D "/mnt"; NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, fspath); error =3D namei(&nd); } if (!error) { + NDFREE_PNBUF(&nd); vp =3D nd.ni_vp; error =3D (vp->v_type =3D=3D VDIR) ? 0 : ENOTDIR; if (!error) @@ -376,7 +376,6 @@ vfs_mountroot_shuffle(struct thread *td, struct mount = *mpdevfs) } else vput(vp); } - NDFREE_PNBUF(&nd); = if (error) printf("mountroot: unable to remount previous root " @@ -387,6 +386,7 @@ vfs_mountroot_shuffle(struct thread *td, struct mount = *mpdevfs) NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, "/dev"); error =3D namei(&nd); if (!error) { + NDFREE_PNBUF(&nd); vp =3D nd.ni_vp; error =3D (vp->v_type =3D=3D VDIR) ? 0 : ENOTDIR; if (!error) @@ -413,7 +413,6 @@ vfs_mountroot_shuffle(struct thread *td, struct mount = *mpdevfs) if (error) printf("mountroot: unable to remount devfs under /dev " "(error %d)\n", error); - NDFREE_PNBUF(&nd); = if (mporoot =3D=3D mpdevfs) { vfs_unbusy(mpdevfs); From nobody Fri Jul 21 17:50:23 2023 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 4R6xtg3Khbz4pDtQ for ; Fri, 21 Jul 2023 17:51:07 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R6xtg2qKQz3ngL; Fri, 21 Jul 2023 17:51:07 +0000 (UTC) (envelope-from yasu@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689961867; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=1dkjnsQ4U+HNHalpYQgtBh8XWJi9wkYG080j2oUdv3s=; b=nAy2uDsFG+Pd903t9k9SQ/a13gI13f9a63oaqCyH0gH1hfIcBi0werubiUm5D67jTDEMmU sfnECxOfZ3dTztxp0IEtz6DO1YNXs9SS+bkTM/a1464jKD8BvekC3CH3f5qB72U+5t2Pyf ycVwV3mdOuItSvZBbCjjaQsnxmMk+upIVbvb5LysyI+eNz3Y2tTb2NeX0doXH5Wrv2pM4o BUJRI6ZRlDKAHXX0McXOs8iFMh81lD8O+QPmQx4gBS7aSNvnLCM0Oo3VTmt0slVSdu+HF9 i8nUgTEyUDGQIsb/sp62Y3U9D9oSWwRySh/UGlxF29s7v3wJY0JiDQqeQnGAvQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689961867; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=1dkjnsQ4U+HNHalpYQgtBh8XWJi9wkYG080j2oUdv3s=; b=m+DOO0FGzvBI71djsqk5iYrsZg1oatBWyP3wJf1vrSNScLmUlGZEjOXRNrgPc6MYaH8kDU J45h/pAyIvZErahUFQqtJJVEYyhPPl2MKKYso9CE95LGSRnp2ORhlz5QJ35qfDZfE7ITcL y/uacYL++5ZwuhsmYDxFpjEE4cyyoFbimPjBkYzp8EJUubs8e7w4J7D6EYWSW3XQYzR0A4 ukHZdRezVVOBXeWvG0xhFlde67aTHx/Y8CSVxI0ZuDZ5lsOlwGRpsAma2kocyHQ9n/tgQ+ XNUsgulsrUhLupSg3jJm5tVcRLKPuhLtHcSRME1PPdS/Eed0nrMkCQPIwBYafw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1689961867; a=rsa-sha256; cv=none; b=cPl9YjfXPp/VlF03T05K97bCVFzQuaSpytZPwhkScxnyJjSPitSIroTyvyuFFlTSGzHu0y fSVV4l/gV1ZVgW2n8u+r7Gi3AyMsFc9LNhlqAPRTYYRriDe4qSuKVDf15YK69egTlBSpzW Gt29BzH4jYOCfBeogix/2WAfwE+4q3iHzpWA/9S5EZ2rypvWu3e5M2ROBx0k7WkTVCXmz0 eLkCAntDxjPnCDTjbRDyGsinfv64WyDuDPIbJNZYvcHSZG06ciSzM3I/wk3vjfVivNszNx kCL0HIWFEOqh7zmXVYtoHnnXQPI5Da6UFSI1n8m6TXoLVXOto9w0d273MupdVg== Received: from localhost (unknown [IPv6:240b:11:220:fe00::174:11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: yasu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4R6xtf4xs0z14Ll; Fri, 21 Jul 2023 17:51:06 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Date: Sat, 22 Jul 2023 02:50:23 +0900 (JST) Message-Id: <20230722.025023.585050244019517783.yasu@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 From: Yasuhiro Kimura X-Mailer: Mew version 6.9 on Emacs 30.0.50 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 After updating my 14.0-CURRENT amd64 system from main-n264162-f58378393fb to main-n264268-ff4633d9f89, kernel crashes with panic as following. https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64-main-n264268-ff4633d9f89.20230721.panic.png --- Yasuhiro Kimura From nobody Fri Jul 21 19:45:07 2023 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 4R70Qz67svz4pFp3 for ; Fri, 21 Jul 2023 19:45:47 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R70Qz3Wr9z3Dc4; Fri, 21 Jul 2023 19:45:47 +0000 (UTC) (envelope-from yasu@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689968747; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FJLPII/tiIxKmoielGcRuwUS/ZW5lJivgl+WqG7gdkY=; b=C7z9eg74CqpHuh4+aIJN+Ih/CJ7COWR0EhQuV2RFrhJCAjkjmVKWs2JbblofS+AudaDV75 ngNdGzA1eCfqNZrROvES8rhLlj7QXfU/z7OxbFSHWEQxBSqZ+fl9/QH6hXNaTGBRpY2VqT XhQ2vMlbk6SJp7EI2CiIHJ6Dxzu5uKHKkim+jjJxWMzlPhzD8RSiMbiLEQaOaGQljOwcrN DNTj9OLFXR1Ae7e51pNXaeKYQZkusVL/bNIjae3J/Y7h6fZaMwQPIGroDoQy/gNHdk4G4U TsVnXSlSggmLAQPPoxZX1wptx9aiE4Mo1jeQ4gwMUTdUmZXyH6ojfIa7C1+W5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1689968747; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FJLPII/tiIxKmoielGcRuwUS/ZW5lJivgl+WqG7gdkY=; b=B0BJ6NtHjmaLFgsvf8IsmrZLZy6+o52XO98f0cyktV9aBJpYR1h37YW6kJZlHoUHR6wdg2 j8UUo0X0PKMkb6NR/HAVoJtaFcL/6BM2KCG2CEvU6KLWSCqOp2gQBYWWYJWUpGL96KPzYQ mpJ+q3kp8jCoVCE95dFKmLiWO5t4c0qc3WjCVcayNDwhgc9Sq6AcYKRz/ksuh/K2gq+qtv nb6ngyXDX2PViG2Kf2ha5j3HOBr27zfoHvQAGr1S71xOGB+KGZvTglqby4Y7EqdZrZp5Is lvV3UuPb28e0lBinsC08DPXkU0t0Jq/NAFNUAgugjWUAgZ1JsXvIlDk2HCrJfw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1689968747; a=rsa-sha256; cv=none; b=FjY+1w/bcL318DNHCr7h5vz/d9/8lA5VySHJBkKPgFKdZJM+zf3MsCwEMrPn5W6fkYIqrq NuFtkiYDUZYtnySmW2UVkIcy6vQPm0jO9ayqwtJkbJ/0QsKyJ4iFxxL1A9kmuZ67WaPP3m +pEnQpl+iQKcOdEbYUlODB1hyFi+D640GgAVd67KVyIddcpSdC23SECctDyiBT0nm4FRmH IcTjRTkrPIXEO54L1jZEI+DtW9zbBJ0V4MiUewlq+zmnSTHotZSWGhTNWRLaEEgfYwcsCk XqXjgVDciGtf0P2IlxFjGF0kzE4G8pQMB57xYrV3HG8ybYwu/6k/dLgUXgCY3Q== Received: from localhost (unknown [IPv6:240b:11:220:fe00::174:11]) (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) (Authenticated sender: yasu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4R70Qy4Lrnz162k; Fri, 21 Jul 2023 19:45:46 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Date: Sat, 22 Jul 2023 04:45:07 +0900 (JST) Message-Id: <20230722.044507.1700500821004554930.yasu@FreeBSD.org> To: freebsd-current@freebsd.org Cc: kbowling@FreeBSD.org Subject: Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 From: Yasuhiro Kimura In-Reply-To: <20230722.025023.585050244019517783.yasu@FreeBSD.org> References: <20230722.025023.585050244019517783.yasu@FreeBSD.org> X-Mailer: Mew version 6.9 on Emacs 30.0.50 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 From: Yasuhiro Kimura Subject: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 Date: Sat, 22 Jul 2023 02:50:23 +0900 (JST) > After updating my 14.0-CURRENT amd64 system from > main-n264162-f58378393fb to main-n264268-ff4633d9f89, kernel crashes > with panic as following. > > https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64-main-n264268-ff4633d9f89.20230721.panic.png According to the result of bisect, kernel panic starts with following commit. ---------------------------------------------------------------------- commit 95f7b36e8fac45092b9a4eea5e32732e979989f0 Author: Kevin Bowling Date: Thu Jul 20 20:30:00 2023 -0700 e1000: lem(4)/em(4) ifcaps, TSO and hwcsum fixes * em(4) obey administrative ifcaps for using hwcsum offload * em(4) obey administrative ifcaps for hw vlan receive tagging * em(4) add additional TSO6 ifcap, but disabled by default as is TSO4 * lem(4) obey administrative ifcaps for using hwcsum offload * lem(4) add support for hw vlan receive tagging * lem(4) Add ifcaps for TSO offload experimentation, but disabled by default due to errata and possibly missing txrx code. * lem(4) disable HWCSUM ifcaps by default on 82547 due to errata around full duplex links. It may still be administratively enabled. Reviewed by: markj (previous version) MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D30072 ---------------------------------------------------------------------- Cc-ing to its committer. --- Yasuhiro Kimura From nobody Sat Jul 22 04:44:13 2023 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 4R7DNW450hz4nZ0Y for ; Sat, 22 Jul 2023 04:44:27 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R7DNW1MZCz3tQs for ; Sat, 22 Jul 2023 04:44:27 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oi1-x235.google.com with SMTP id 5614622812f47-3a412653335so1748158b6e.1 for ; Fri, 21 Jul 2023 21:44:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; t=1690001064; x=1690605864; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=aycRqLHzKTsGfvmkjYugIEcwOjpq/N0e94wuFxXxJRE=; b=hAhGOIO2AgZsrfz3CVswe3Yoyfg9+Ci0QREkQUqeVx6lWIsqBbMKvl7pihdhikKqZv eCmgtGg8rqnON4iHvI1g9IUKoBz6Qh1cFHwZkLJLQMWSnV/gZYQSqoW+QGmnVY01slxI SZXwTQMm8j6Eb37otZmlhuiq9dMt2yFWvDMww= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690001064; x=1690605864; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=aycRqLHzKTsGfvmkjYugIEcwOjpq/N0e94wuFxXxJRE=; b=PrGxLeqRA/93ODycNjGiuPCB0IR6BfsQl6gJ7Y2RwOliWGfk+qmXGWR5JS+vD4WmSz kaFE+dyWY59SbFYH7iikTtBs7+8zgop2JzplOY++SlG3/E3sm6Rog3R0l/uSMeEPh6R0 VLujKtjKUhkkHUK0sdfhGgPo+IKMc2BByKynwxs9LeEF5MQjDQPvXKgEy0wZK8+UOOFQ 4OzYB49PRNiTwZawwYjCT4qCdr6MKk25DRKCkywbAZfxAKodpJW8DLqPL1bP2pY/hacX mEshmPW7eZPCtXryiExc2/Fdq8fyzEKbOoVs27wwuMFJB/wgoq66l9dqHRol2vcYW0ZT 0iUg== X-Gm-Message-State: ABy/qLZ4EliIj++gJOPcqmxnxLOFqW4mD8d8rEwCbtUH7rcBJ6YeJphH a7UI5GGTgBn8uIcNNNBexy2Py7scH2U1m+O1FGriQLJPzcgW6z/c X-Google-Smtp-Source: APBJJlGoZRxAXp879z/ROO7ESZNJx2mwOLBc4MABEiR7g9K+d6Y0lnVod5L5phXNVJcgGHoZOtvlOXoIRyZwsWWKARY= X-Received: by 2002:a05:6808:23d0:b0:39c:93ba:cb92 with SMTP id bq16-20020a05680823d000b0039c93bacb92mr5811179oib.8.1690001064430; Fri, 21 Jul 2023 21:44: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 References: <20230722.025023.585050244019517783.yasu@FreeBSD.org> <20230722.044507.1700500821004554930.yasu@FreeBSD.org> In-Reply-To: <20230722.044507.1700500821004554930.yasu@FreeBSD.org> From: Kevin Bowling Date: Fri, 21 Jul 2023 21:44:13 -0700 Message-ID: Subject: Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 To: Yasuhiro Kimura Cc: freebsd-current@freebsd.org, kbowling@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4R7DNW1MZCz3tQs X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated Thanks, I have reverted for now. Can you tell me which NIC is implemented there? On Fri, Jul 21, 2023 at 12:45=E2=80=AFPM Yasuhiro Kimura = wrote: > > From: Yasuhiro Kimura > Subject: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4= 633d9f89 > Date: Sat, 22 Jul 2023 02:50:23 +0900 (JST) > > > After updating my 14.0-CURRENT amd64 system from > > main-n264162-f58378393fb to main-n264268-ff4633d9f89, kernel crashes > > with panic as following. > > > > https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64-main-n264268-= ff4633d9f89.20230721.panic.png > > According to the result of bisect, kernel panic starts with following > commit. > > ---------------------------------------------------------------------- > commit 95f7b36e8fac45092b9a4eea5e32732e979989f0 > Author: Kevin Bowling > Date: Thu Jul 20 20:30:00 2023 -0700 > > e1000: lem(4)/em(4) ifcaps, TSO and hwcsum fixes > > * em(4) obey administrative ifcaps for using hwcsum offload > * em(4) obey administrative ifcaps for hw vlan receive tagging > * em(4) add additional TSO6 ifcap, but disabled by default as is TSO4 > * lem(4) obey administrative ifcaps for using hwcsum offload > * lem(4) add support for hw vlan receive tagging > * lem(4) Add ifcaps for TSO offload experimentation, but disabled by > default due to errata and possibly missing txrx code. > * lem(4) disable HWCSUM ifcaps by default on 82547 due to errata arou= nd > full duplex links. It may still be administratively enabled. > > Reviewed by: markj (previous version) > MFC after: 2 weeks > Differential Revision: https://reviews.freebsd.org/D30072 > ---------------------------------------------------------------------- > > Cc-ing to its committer. > > --- > Yasuhiro Kimura From nobody Sat Jul 22 08:20:19 2023 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 4R7KBd4vKqz4dNDj for ; Sat, 22 Jul 2023 08:21:13 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R7KBd1J87z3wSH; Sat, 22 Jul 2023 08:21:13 +0000 (UTC) (envelope-from yasu@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690014073; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Kh0qUtAtnsaqAjv/K0+PNKIwsEUACQc7MKkn7F1cUYs=; b=B3hFSt7bRiFr2l8LMqVknxPUh7ycWRiyUeuxKzYMoSywSZVUMJpmlwHbYkWplbd7yrgQjJ 4BN0oSMpipEn03dxRI+hVhv2bIWmAR1AxGEY+b7UY0czf05B2rugrjkBrIt4ieB0APWWvp 2Ph3sliXS83jOtA+SdgJ8LKRd8EE92j9yNRIrREDF6yytJP0itfKCevzfvvYm4Vvz0cMTK uJLldoOqzOEIFZDgosN0EA5ip63zQhrrwzi8LuAauDIwUlTEwZD1HIe1aKlPSu/d+PpL38 rrNdqWchQ2G29rkbprV/Ahm+K45/e3DOXLuTXgruWXZ+joJfotcQ+xBnXXKz1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690014073; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Kh0qUtAtnsaqAjv/K0+PNKIwsEUACQc7MKkn7F1cUYs=; b=DyD/uG2g8yzh3m2UWLKQBpBaBm5ldQUzoTXwFYSnCKWnG7OWCufbbqYZhwkMFTXgy7Ssmq bJifUHyuVZ3KW5ilqEDEewT75NDYMCaZM7Ikt8CN5YS21yZFPRs1aaVW+wdrd6NQOLg7Gm 0TvlleLUOzaoZ9B3F2VSw5cosITTlrgwOjcyaKTbRTUZ6A51fDSYzQ6o5UNJmiU4pZzWQ8 pHK/NPssVg+ZWJF9NsLZOMTFr9bto8PDuXfVudNNxAwTFzqOmcSb/X2qDk0IQkd0rieCIB F3eKoxBnNqcUQYELFHZOmtguK67G6EoDxlVCJLHDEX5g8ZgfnFaSjcoP792COw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1690014073; a=rsa-sha256; cv=none; b=t6cgmmlolY+WVfkKjgYzmycP7Ndu4z2x7P2pyZbhmU4iIJVy40Z/55RQI+5+CPtlFhMOnq PHMvB6/52aK+UPSiv4GbGPYN9HBR0KEyQ9UzubhbCTqB5yaBIRWVWjO1mL6RAcl+kHFsjj rf2wumh73t1hXPDriLzMX2wmZASU1GUm080b0YEwNgtUeTmzKXLLHS3Fs9RspnbKn+WatR 7ixsYpStQwQmoL7CM1pJApcQue6Dx2h26kxFhc3Nf/a7Lzv0O6kqjAE8TWnp04tc4XK4Xx ZIgBLXNiePhFHKmqU6GrTmkknX4UQu9yVm7If0qXt5FZqQL9qT2PLySROduIyQ== Received: from localhost (unknown [IPv6:240b:11:220:fe00::174:11]) (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) (Authenticated sender: yasu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4R7KBc1CkqzMrF; Sat, 22 Jul 2023 08:21:11 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Date: Sat, 22 Jul 2023 17:20:19 +0900 (JST) Message-Id: <20230722.172019.1355359952134070430.yasu@FreeBSD.org> To: kevin.bowling@kev009.com Cc: freebsd-current@freebsd.org, kbowling@freebsd.org Subject: Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 From: Yasuhiro Kimura In-Reply-To: References: <20230722.025023.585050244019517783.yasu@FreeBSD.org> <20230722.044507.1700500821004554930.yasu@FreeBSD.org> X-Mailer: Mew version 6.9 on Emacs 30.0.50 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 From: Kevin Bowling Subject: Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 Date: Fri, 21 Jul 2023 21:44:13 -0700 > Thanks, I have reverted for now. Can you tell me which NIC is > implemented there? Output of `pciconf -lv` says as following. em0@pci0:0:3:0: class=0x020000 rev=0x02 hdr=0x00 vendor=0x8086 device=0x100e subvendor=0x8086 subdevice=0x001e vendor = 'Intel Corporation' device = '82540EM Gigabit Ethernet Controller' class = network subclass = ethernet Regards. --- Yasuhiro Kimura From nobody Sat Jul 22 19:23:22 2023 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 4R7btw2XmTz4nWkN for ; Sat, 22 Jul 2023 19:23:36 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R7btv6DJ9z40rK for ; Sat, 22 Jul 2023 19:23:35 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x635.google.com with SMTP id d9443c01a7336-1b8b2886364so16755545ad.0 for ; Sat, 22 Jul 2023 12:23:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; t=1690053813; x=1690658613; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=SF2bWD6ovgtrydxwU1bFvlMDtdMcwXalJ5RjKp7pfsk=; b=brPgRbx1dYScsPyuNK7Il1JhiGp165iWKOR+klS/QoDl9k3oROFHitQMWN5N++CkmH uVsyAaS2S+FMavYMvyB95yEnwpyAotaJ3xlIgp5sNxwCenAwVAa4nWKpcbxCBVY736w2 Gz6NVtyTDhuP9rMhlgMq+UrGQore8qaSIwMBM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690053813; x=1690658613; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=SF2bWD6ovgtrydxwU1bFvlMDtdMcwXalJ5RjKp7pfsk=; b=i8aSWyiqBHyJZKfHJidHViQUGXvAmFGM2OrLKz+8UTgH0LjNy82RHz2DPcjY3TR/bh 6Zht6z1QiIsLw7VS2//7QkuR6dlAYmlPKJoojEAH1HT7a9Zc+FTAUl+J988fBgc+bxvN Ul5IPf/NIT6/jppvcc8+xIiOUuMXt2zj5rAIjs+PZefOIS7ek+fkIGnmz0lYCUu6kbBC yaF6FT3qQO2FdwWZdu2hV7dCvWc8vQ5VfNY53ssvqDwfsh595efNYvUWoua6wZCq5ho+ /wGN78YpPxXlfTDxVxmWQ819tRe/rF/5Mlz6N9Nxw1r8SMIWNWPMdsUrpFBX2qJ037r3 1pXw== X-Gm-Message-State: ABy/qLbfbIcRDJJk2p0IoWrld8rIQni8m8pGYB1501g/NjA6w/wHZ3Hv G2rga7TQa0PckRtmHmU/VAlvQUmIYWRCmd45h2NMmQ== X-Google-Smtp-Source: APBJJlEvmM0wVuJq6C8Jko0rsTF72pdeJHgtu8yiDFpkm1693GbrfBNmR8Rz+brpOcsySd0FmCRvzJra7bLW+VAoK10= X-Received: by 2002:a17:90a:8a0d:b0:263:43c6:69ac with SMTP id w13-20020a17090a8a0d00b0026343c669acmr3610732pjn.44.1690053813553; Sat, 22 Jul 2023 12:23:33 -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: <20230722.025023.585050244019517783.yasu@FreeBSD.org> <20230722.044507.1700500821004554930.yasu@FreeBSD.org> <20230722.172019.1355359952134070430.yasu@FreeBSD.org> In-Reply-To: <20230722.172019.1355359952134070430.yasu@FreeBSD.org> From: Kevin Bowling Date: Sat, 22 Jul 2023 12:23:22 -0700 Message-ID: Subject: Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 To: Yasuhiro Kimura Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4R7btv6DJ9z40rK X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On Sat, Jul 22, 2023 at 1:21=E2=80=AFAM Yasuhiro Kimura = wrote: > > From: Kevin Bowling > Subject: Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268= -ff4633d9f89 > Date: Fri, 21 Jul 2023 21:44:13 -0700 > > > Thanks, I have reverted for now. Can you tell me which NIC is > > implemented there? > > Output of `pciconf -lv` says as following. > > em0@pci0:0:3:0: class=3D0x020000 rev=3D0x02 hdr=3D0x00 vendor=3D0x8086 de= vice=3D0x100e subvendor=3D0x8086 subdevice=3D0x001e > vendor =3D 'Intel Corporation' > device =3D '82540EM Gigabit Ethernet Controller' > class =3D network > subclass =3D ethernet > > Regards. Thanks for the report, I've identified the errors and recommitted. > --- > Yasuhiro Kimura