Re: Finding git commit corresponding to 13.2-RELEASE-p3

On Sun, 24 Sep 2023 13:41:30 -0400
"Colin S. Gordon" <csgordon@fastmail.com> wrote:

> Hi,
> 
> I'm trying to debug sleep on my laptop, but have run into trouble reproducing
the problem with a locally-built kernel, which I suspect is an issue of
me not getting the right version of the source for what's currently
running. 
> 
> Can anyone point me in the right direction for what commit 13.2-RELEASE-p3 was built
from? I neglected to install the source component during my initial
install, so cloned manually. I've tried a few different commits,
including initially HEAD on 13-STABLE, and more recently a build of
866e5c6b3ce7 from stable/13 (based on
https://www.freebsd.org/security/advisories/FreeBSD-EN-23:09.freebsd-update.asc).
However the builds I've managed to produce introduce an additional
failure that masks the original problem. On 13.2-RELEASE-p3, my machine
goes to sleep, and partly wakes up before hitting
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211705#c3 on a laptop
whose only storage is eMMC, in particular with the screen coming back
up enough for me to see the failure from sdhci. On all the kernels I've
built locally, the screen never comes back up, so I wouldn't be able to
see if changes I made had any effect. (There's no actual serial port on
this machine to debug with another machine.)
> 
> So I now want to find the commit corresponding to exactly the kernel shipped with (amd64) 13.2-RELEASE-p3, so I can
>  • Verify that I can actually reproduce the exact problem on a locally-built (so, modifiable kernel). Otherwise there's something wrong with my build process, I guess. (The kernels I'm building boot and run, but have different behavior when I try to resume from sleep compared to 13.2-RELEASE-p3.)
>  • Debug bug 211705, and
>  • Binary search changes to see what commits might have altered the resume behavior on my machine (which 
> I'm happy to dig into the problems themselves, but I really need to find which git commit to build from, and I'm having trouble finding this information.  I'm sorry if it's posted in some place I haven't managed to find, but I'd appreciate any pointers (both to this specific piece of information, and how to find it in the future for other scenarios).
> 
> Thanks in advance,
> Colin

IIUC, each -p* build is done at the point when update for "BRANCH="
line in /usr/src/sys/conf/newvers.sh is done. So you should track the
commits to /usr/src/sys/conf/newvers.sh on cgit [1].
For 13.2-p*, track releng/13.2 branch [2].

You can find commits
  525ecfdad597980ea4cd59238e24c8530dbcd31d for vanilla 13.2-RELEASE
  08b87f63a046bd966bd0ed548211ae98ff50e638 for -p1
  4341433a673fde3e1c1554b9daa15d4db71f6edb for -p2
and
  a1c915cc75c1b3c66e16bb52579e2abdf122eccb for -p3
individually.
Next, to be sure enough, go to [3], select releng/13.2 with the drop
down menu at the top-right of the page and push "switch" button at the
right of it, switch "log msg" to "range" and enter the wanted commit
hash and press "search" button. You can find all commits to the branch
until the commit is done.

[1] https://cgit.freebsd.org/

[2] https://cgit.freebsd.org/src/log/sys/conf/newvers.sh?h=releng/13.2

[3] https://cgit.freebsd.org/src/

-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>