From nobody Sun Sep 24 17:41:30 2023 X-Original-To: freebsd-hackers@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 4Rtv9h5tn9z4vGQw for ; Sun, 24 Sep 2023 18:07:36 +0000 (UTC) (envelope-from csgordon@fastmail.com) Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Rtv9h0fmmz3c4n for ; Sun, 24 Sep 2023 18:07:36 +0000 (UTC) (envelope-from csgordon@fastmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=fastmail.com header.s=fm2 header.b=b5Dp8Pqm; dkim=pass header.d=messagingengine.com header.s=i60c149f6.fm2 header.b=RBm+LdF1; spf=pass (mx1.freebsd.org: domain of csgordon@fastmail.com designates 66.111.4.224 as permitted sender) smtp.mailfrom=csgordon@fastmail.com; dmarc=pass (policy=none) header.from=fastmail.com Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id 961AD58196C for ; Sun, 24 Sep 2023 14:07:35 -0400 (EDT) Received: from imap53 ([10.202.2.103]) by compute5.internal (MEProxy); Sun, 24 Sep 2023 14:07:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= cc:content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm2; t=1695578855; x=1695579455; bh=Y23BzQuLBU1JsuwNZhrGwv2h2 04zoL0QNsdGmw0QhKw=; b=b5Dp8PqmFnuPba5t0DBeoTvLieU3rav73NC8aRoLf mo23+QBnb9Esckhf8tRq8FkELRnIbCgs06k2XBqsXZEXTQn14usEEoB7K8r817e1 6OlQgTPd2tJzc81Jm+9oHhSEhkPxqmq9LKUQq1f+pO7FMXNEyNXW8TH0FyZIhTxa a1k1BBEKldQnpD7PqHLezlBB8vTWMtXrusojCSiVFV6YAMm3lkz9mqUhljC6m5BK /xx76ipSfei77P89FcAfod/lVKHC6C01cNn1jlwbctFDhXZFR4jrnV/hpUXozS7g HibnO/kGffShcnf/lg5Vn2uVuU3bSIoMtv6yOgPjCEDUw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=i60c149f6.fm2; t=1695578855; x=1695579455; bh=Y23BzQuLBU1JsuwNZhrGwv2h204zoL0Q NsdGmw0QhKw=; b=RBm+LdF14J+k20P82wEFeiEmA8xe2WIu+EiqYvUeixVbEZg/ iNLuSpB6FDlCYi+oEiWRwzsYcgp8uBc66iqXVP8SzaEVhFXDu+PGDj+yCBFf4nS2 E4WpIqGO0KSuuRE6/TPnnz2VN7+jEqb5Fh+TEL2n39y33MWp5FHFYHuLHn13HIL6 IOPTLQJFdf/DhqSiQn6RaR6omHL65jbv48NkONgF9zR6HdrfKTcCixlKDDTdwV1Q 6K4o5Sd3ESwMnsUv8DgyV5FErcwHDmBLKXLdJOJX+dVhPKBS/ibOiKaQ768a5OYF iC4ULMC8zVlaQbB5ueLgxcU4Kipomd85YsINaQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudelvddguddvudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesrgdtre erreertdenucfhrhhomhepfdevohhlihhnucfurdcuifhorhguohhnfdcuoegtshhgohhr ughonhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrghtthgvrhhnpeevkeevleefgf ekueeuveekkeffgefgieffteekhfeutdelheefudeluedugfegteenucffohhmrghinhep fhhrvggvsghsugdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegtshhgohhrughonhesfhgrshhtmhgrihhlrdgtohhm X-ME-Proxy: Feedback-ID: i60c149f6:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 338E2364005C; Sun, 24 Sep 2023 14:07:35 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-761-gece9e40c48-fm-20230913.001-gece9e40c List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Message-Id: <1ee70bdf-828c-462d-bf1c-28d10cd7e903@app.fastmail.com> Date: Sun, 24 Sep 2023 13:41:30 -0400 From: "Colin S. Gordon" To: freebsd-hackers@FreeBSD.org Subject: Finding git commit corresponding to 13.2-RELEASE-p3 Content-Type: multipart/alternative; boundary=bac917373e9c40f4972f9708e55be000 X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.09 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[fastmail.com,none]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.224:c]; R_DKIM_ALLOW(-0.20)[fastmail.com:s=fm2,messagingengine.com:s=i60c149f6.fm2]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.224:from]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[fastmail.com]; MLMMJ_DEST(0.00)[freebsd-hackers@FreeBSD.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[fastmail.com:+,messagingengine.com:+]; FREEMAIL_ENVFROM(0.00)[fastmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.111.4.224:from] X-Rspamd-Queue-Id: 4Rtv9h0fmmz3c4n --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
Hi,

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.

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 https://www.freebsd.org/secur= ity/advisories/FreeBSD-EN-23:09.freebsd-update.asc). 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 https://bugs.freebsd.org/bugzilla/show_b= ug.cgi?id=3D211705#c3 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.)

So I now want to find the commit c= orresponding to exactly the kernel shipped with (amd64) 13.2-RELEASE-p3,= so I can
  • 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.)
  • Debug bug 211705, and
    <= /li>
  • Binary search changes to see what commits might have altered the= resume behavior on my machine (which
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).
Thanks in advance,
Colin
--bac917373e9c40f4972f9708e55be000--