Date: Tue, 1 Oct 2024 03:21:09 +0100 From: Graham Perrin <grahamperrin@gmail.com> To: freebsd-current@freebsd.org Subject: Wake (resume) regression? Message-ID: <7985e4d2-2387-4a86-8dbe-0a081fda0466@gmail.com>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------sUmIpI2GKGMUZmwIrBcGRL7p Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Has anything changed in the past two months that might cause wake to become unreliable? nvidia-driver-470, if that's relevant. Built from source. HP ZBook 17 G2. IIRC the unreliability became noticeable not long after the bump to 1500023. That was around the end of August (with pkgbase). Previously, I'd say that wake was 99% reliable. Now, wake more often fails than succeeds. The greatest frustration: it's not consistently reproducible. I have not yet identified the ingredients that precede a failure, and critically: - when failure occurs, there's nothing (no flicker of the display, no HDD activity). In other words, no sense of what might be wrong at the time. <https://gist.github.com/grahamperrin/86359cb7c6d1316d75f340fb305484ed>; lists all recent boot environments. <https://pastebin.com/raw/xBwqeBxr>; is the subset that remains after routine weeding of environments. This includes: 1500021-006-base - - 2.81G 2024-07-25 02:31 1500022-001-base-ports - - 17.0M 2024-07-29 17:22 1500022-002-base-ports - - 3.09G 2024-07-30 06:50 1500022-004-base - - 2.81G 2024-07-30 14:45 1500023-001-base - - 2.89G 2024-07-31 03:14 1500023-002-base - - 2.80G 2024-08-01 05:26 ---- I'm aware of this report (not involving NVIDIA): <https://github.com/freebsd/drm-kmod/issues/312>; <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280923>; Blind carbon copy: the reporter. --------------sUmIpI2GKGMUZmwIrBcGRL7p Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <!DOCTYPE html> <html data-lt-installed="true"> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body style="padding-bottom: 1px;"> <p><font face="monospace">Has anything changed in the past two months that might cause wake to become unreliable? <br> </font></p> <p><font face="monospace">nvidia-driver-470, if that's relevant. Built from source. </font></p> <p><font face="monospace">HP ZBook 17 G2. <br> </font></p> <p><font face="monospace">IIRC the unreliability became noticeable not long after the bump to 1500023. That was around the end of August (with pkgbase). <br> </font></p> <p><font face="monospace">Previously, I'd say that wake was 99% reliable. Now, wake more often fails than succeeds. The greatest frustration: it's not consistently reproducible. I have not yet identified the ingredients that precede a failure, and critically: <br> </font></p> <p><font face="monospace">- when failure occurs, there's nothing (no flicker of the display, no HDD activity).</font></p> <p><font face="monospace">In other words, no sense of what might be wrong at the time.<br> </font></p> <p><font face="monospace"><a class="moz-txt-link-rfc2396E" href="https://gist.github.com/grahamperrin/86359cb7c6d1316d75f340fb305484ed"><https://gist.github.com/grahamperrin/86359cb7c6d1316d75f340fb305484ed></a>; lists all recent boot environments. </font></p> <p><font face="monospace"><a class="moz-txt-link-rfc2396E" href="https://pastebin.com/raw/xBwqeBxr"><https://pastebin.com/raw/xBwqeBxr></a>; is the subset that remains after routine weeding of environments. This includes:<br> </font></p> <pre>1500021-006-base - - 2.81G 2024-07-25 02:31 1500022-001-base-ports - - 17.0M 2024-07-29 17:22 1500022-002-base-ports - - 3.09G 2024-07-30 06:50 1500022-004-base - - 2.81G 2024-07-30 14:45 1500023-001-base - - 2.89G 2024-07-31 03:14 1500023-002-base - - 2.80G 2024-08-01 05:26 </pre> <p></p> <p><font face="monospace">----</font></p> <p><font face="monospace">I'm aware of this report (not involving NVIDIA): <br> </font></p> <p><font face="monospace"><a class="moz-txt-link-rfc2396E" href="https://github.com/freebsd/drm-kmod/issues/312"><https://github.com/freebsd/drm-kmod/issues/312></a><br>; <a class="moz-txt-link-rfc2396E" href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280923"><https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280923></a></font></p>; <p><font face="monospace">Blind carbon copy: the reporter. <br> </font></p> </body> <lt-container></lt-container> </html> --------------sUmIpI2GKGMUZmwIrBcGRL7p--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7985e4d2-2387-4a86-8dbe-0a081fda0466>