summaryrefslogtreecommitdiffstats
path: root/ChangeLog.txt
diff options
context:
space:
mode:
Diffstat (limited to 'ChangeLog.txt')
-rw-r--r--ChangeLog.txt24
1 files changed, 24 insertions, 0 deletions
diff --git a/ChangeLog.txt b/ChangeLog.txt
index 115418e14..47ab1ac4d 100644
--- a/ChangeLog.txt
+++ b/ChangeLog.txt
@@ -1,3 +1,27 @@
+Tue Jul 18 19:58:10 UTC 2023
+a/tar-1.35-x86_64-1.txz: Upgraded.
+x/mesa-23.2.0_rc1-x86_64-1.txz: Upgraded.
+ OK, usually I won't use rc versions even in -current, but in this case I'm
+ going to. Some time ago my desktop machine with RS880 / Radeon HD 4290
+ graphics on the motherboard began acting up with the screen going black
+ for a few seconds before returning. This after an hour or so of uptime,
+ usually, then becoming more frequent with more uptime. Eventually I'd lose
+ mouse and/or keyboard too, and have to reboot. Here's a couple of errors
+ from dmesg:
+ [ 9942.677675] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait
+ timed out.
+ [ 9942.677741] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed
+ testing IB on GFX ring (-110).
+ I also noticed that the backtrace started with ttm_bo_release, and seeing
+ this in recent kernel patches had been chalking this up to a kernel bug.
+ I *still* think it could be, and there are a bunch of kernel patches coming
+ soon to -stable from Alex Deucher that could address the underlying causes
+ (not for 6.1.39 though, unfortunately). Anyway, I'd recently figured out
+ that reverting Mesa sufficiently made the issue go away. And now it seems
+ this 23.2.0 release candidate also fixes the issue.
+ Yes, I could go search for the commits to cherry-pick, but we'll be moving
+ to mesa-23.2.0 when it's released, so we might as well start testing now.
++--------------------------+
Mon Jul 17 19:17:19 UTC 2023
ap/sudo-1.9.14p2-x86_64-1.txz: Upgraded.
This is a bugfix release.