Date: Sun, 24 Sep 2023 13:41:30 -0400 From: "Colin S. Gordon" <csgordon@fastmail.com> To: freebsd-hackers@FreeBSD.org Subject: Finding git commit corresponding to 13.2-RELEASE-p3 Message-ID: <1ee70bdf-828c-462d-bf1c-28d10cd7e903@app.fastmail.com>
next in thread | raw e-mail | index | archive | help
--bac917373e9c40f4972f9708e55be000 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, I'm trying to debug sleep on my laptop, but have run into trouble reprod= ucing the problem with a locally-built kernel, which I suspect is an iss= ue of me not getting the right version of the source for what's currentl= y running.=20 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 86= 6e5c6b3ce7 from stable/13 (based on https://www.freebsd.org/security/adv= isories/FreeBSD-EN-23:09.freebsd-update.asc). However the builds I've ma= naged 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=3D2= 11705#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 al= l the kernels I've built locally, the screen never comes back up, so I w= ouldn't be able to see if changes I made had any effect. (There's no act= ual serial port on this machine to debug with another machine.) So I now want to find the commit corresponding to exactly the kernel shi= pped with (amd64) 13.2-RELEASE-p3, so I can =E2=80=A2 Verify that I can actually reproduce the exact problem on a l= ocally-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.) =E2=80=A2 Debug bug 211705, and =E2=80=A2 Binary search changes to see what commits might have altered = the resume behavior on my machine (which=20 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 inf= ormation. I'm sorry if it's posted in some place I haven't managed to f= ind, but I'd appreciate any pointers (both to this specific piece of inf= ormation, and how to find it in the future for other scenarios). Thanks in advance, Colin --bac917373e9c40f4972f9708e55be000 Content-Type: text/html Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso= Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>Hi,<br></div><d= iv><br></div><div>I'm trying to debug sleep on my laptop, but have run i= nto 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 f= or what's currently running. <br></div><div><br></div><div>Can anyone po= int 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 inst= all, so cloned manually. I've tried a few different commits, including i= nitially HEAD on 13-STABLE, and more recently a build of 866e5c6b3ce7 fr= om stable/13 (based on <a href=3D"https://www.freebsd.org/security/advis= ories/FreeBSD-EN-23:09.freebsd-update.asc">https://www.freebsd.org/secur= ity/advisories/FreeBSD-EN-23:09.freebsd-update.asc</a>). However the bui= lds I've managed to produce introduce an additional failure that masks t= he original problem. On 13.2-RELEASE-p3, my machine goes to sleep, and p= artly wakes up before hitting <a href=3D"https://bugs.freebsd.org/bugzil= la/show_bug.cgi?id=3D211705#c3">https://bugs.freebsd.org/bugzilla/show_b= ug.cgi?id=3D211705#c3</a> on a laptop whose only storage is eMMC, in par= ticular 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 come= s 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 m= achine.)<br></div><div><br></div><div>So I now want to find the commit c= orresponding to exactly the kernel shipped with (amd64) 13.2-RELEASE-p3,= so I can<br></div><ul><li>Verify that I can actually reproduce the exac= t problem on a locally-built (so, modifiable kernel). Otherwise there's = something wrong with my build process, I guess. (The kernels I'm buildin= g boot and run, but have different behavior when I try to resume from sl= eep compared to 13.2-RELEASE-p3.)<br></li><li>Debug bug 211705, and<br><= /li><li>Binary search changes to see what commits might have altered the= resume behavior on my machine (which <br></li></ul><div>I'm happy to di= g into the problems themselves, but I really need to find which git comm= it 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).<br></div><div><br= ></div><div>Thanks in advance,<br></div><div>Colin<br></div></body></htm= l> --bac917373e9c40f4972f9708e55be000--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1ee70bdf-828c-462d-bf1c-28d10cd7e903>