From nobody Tue Feb 04 15:41:08 2025 X-Original-To: freebsd-stable@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 4YnSJg25vXz5n0k5 for ; Tue, 04 Feb 2025 15:41:23 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YnSJf15V1z4PlT for ; Tue, 04 Feb 2025 15:41:22 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.208.49 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-ed1-f49.google.com with SMTP id 4fb4d7f45d1cf-5d3ecae02beso7929634a12.0 for ; Tue, 04 Feb 2025 07:41:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738683680; x=1739288480; 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=xUyAIFW+wKGAD9yySA+BSDUqwGPODNHhUqkXscQRJJw=; b=Qbh3v4GBH33lnjVfGeKLBwQIJakjZ+dSf/G/hJZEPFANhk4Gs1xOt39+fLDoEqDJBw ay0AYXhwXpNn83GogrNQLlAoaKHjUJMJUJmacD9W5Km9IffIG6VKOCJWPKipkxPq/3T2 duosD9uOnMjhuFvIkqn1fMWKRQwpQUa86lnBCnjBxUMns+TpzVLmDNHs7qATXpbqLSFn oPG5QbynELIWjWTgQBYw5ETKTXd+oOBkH0ajPS73eYv2gLwqKPweeCotMdVZ8k9VaHbE xIiZxUKY3v+ahgC2RPDXMIXEUF5BjFdBy4KAT5UlP9uspTcxIOSreuo7jJfDCf9YmwjD n+Ug== X-Gm-Message-State: AOJu0Yw4D2JxqxT8JL3SSCet/F6wBbaIhMdwO2bvoa1EgxcmZznfmxfx NsqBv4tPT9//uwlXBBBb1Af/ld9MRq+VLnerOavX8QWfhUP2RFM+5sMbbWwvVOu++X9OZZez4dq HPaqP9wfVDx5M4qP7H9CyBzrnAW4= X-Gm-Gg: ASbGncuXr5RR62ZZN40TzCrbDVKt0QxapLCiwNIwklxCjntmM/JojKGFKXTfWq/PJsv MxJOJ2w8a0wP7OgvK2qFuv6yDcvPhKIKfMIAzYLShdd2wbrVv6gIASmsm9Dpe28TmvOCHbimw X-Google-Smtp-Source: AGHT+IH50MM9f//o7U4+e318ZGZmqte4avROytAoVXiRr3gJ641xlTfAnbNRMr1wttsx52p5z6Zt2M3h8EwzCSnUNLs= X-Received: by 2002:a05:6402:40cd:b0:5dc:8851:fc36 with SMTP id 4fb4d7f45d1cf-5dc8851fcdfmr20843484a12.11.1738683680046; Tue, 04 Feb 2025 07:41:20 -0800 (PST) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 References: <54A00F42-AF4D-440D-99E9-AFF3642C97CE.ref@yahoo.com> <54A00F42-AF4D-440D-99E9-AFF3642C97CE@yahoo.com> In-Reply-To: <54A00F42-AF4D-440D-99E9-AFF3642C97CE@yahoo.com> From: Alan Somers Date: Tue, 4 Feb 2025 08:41:08 -0700 X-Gm-Features: AWEUYZmMUitf-_2x2QYuDF_Mh9wHm9H2hi88VQKoi_JIVwuaMKK0ez_bqwoPHtg Message-ID: Subject: Re: 13.4-RELEASE : freebsd-update fetch-then-install updated kernel but not /usr/lib/debug/boot/kernel/kernel.debug To: Mark Millard Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [0.27 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_LONG(0.95)[0.951]; NEURAL_HAM_SHORT(-0.58)[-0.579]; RBL_SENDERSCORE_REPUT_7(0.50)[209.85.208.49:from]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; BAD_REP_POLICIES(0.10)[]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; R_SPF_ALLOW(0.00)[+ip4:209.85.128.0/17]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.49:from]; FREEFALL_USER(0.00)[asomers]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.49:from] X-Spamd-Bar: / X-Rspamd-Queue-Id: 4YnSJf15V1z4PlT On Sat, Dec 14, 2024 at 10:42=E2=80=AFPM Mark Millard w= rote: > > I was looking have a context to be able to use kgdb for looking at > a 13.4-RELEASE-p2 (so: a 13.4-RELEASE-p1 kernel). > > To get a set of files for 13.4-RELEASE-p2 I had to start from a > 13.4-RELEASE and use freebsd-update : there is no direct download > of a kernel*.txz set or other such for the patched kernel, so far > as I can tell. > > But the freebsd-update update-then-install sequence: > > ) Updated boot/kernel/kernel (and more) > yet: > ) Did not update usr/lib/debug/boot/kernel/kernel.debug > > After the update, kgdb reports for the updated context: > > warning: the debug information found in "/usr/lib/debug//boot/kernel/kern= el.debug" does not match "/boot/kernel/kernel" (CRC mismatch). > > And I diff'd before-vs-after copies of > usr/lib/debug/boot/kernel/kernel.debug and it did not > have a change of content, nor did its modification > date change. > > How is one supposed to investigate via, say, panic backtrace > addresses and such of a patched vintage of the likes of > 13.4-RELEASE and its patched kernel? Does it require > setting up an environment for rebuilding from source that > will happen to accurately reproduce what the official > build produced? > > I'd rather avoid the question of if a configuration for > (re-)building is the cause of a difference vs. other > potential causes of differences: I wish there were > known-good download files to use for reference. > > I'll note that technically, for what I was attempting to > do, I should only need expanded kernel.txz , kernel-dbg.txz , > and src.txz files if they were for the right patch level. > It is the need to use freebsd-update that leads to involving > far more. > > > Somewhat related Side note . . . > > As noted in: > > https://lists.freebsd.org/archives/freebsd-pkgbase/2024-December/000483.h= tml > > the likes of a PkgBase 14.2-RELEASE vs. a set of the *.txz for > the "same" 14.2-RELEASE are not a full match, apparently with: > > ) pad byte differences > > ) Differences in memory layout for .rodata through .eh_frame . > (File paths are recorded that have differing lengths, for > example.) > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com I've noticed this, too. I don't know why it happens, and it's frustrating. It looks like sometimes freebsd-update will update a kernel module's symbol file, ala /usr/lib/debug/boot/kernel/ctl.ko.debug , but not update the symbols for the kernel itself. Other times, however, it updates both.