On Wed, 26 Nov 2025 09:14:17 +0100 Salvatore Bonaccorso <[email protected]> wrote: > Hi Nick, > > On Tue, Nov 25, 2025 at 10:05:16AM -0800, Nick Owens wrote: > > On Sat, 15 Nov 2025 16:16:04 -0800 Nick Owens <[email protected]> wrote: > > > hi, > > > > > > > > > > Is this regressing from an earlier kernel? If yes can you isolate the > > > > range more closely? > > > > > > > > > > based on "journalctl -t kernel | grep 'Linux version'" the prior version > > > with no hang seems to be 6.9.12-amd64. i will try it after the newer 6.12. > > > > do you have any advice on how to run the older debian kernel on debian > > trixie? > > You can fetch other released images (please only use them then only > for testing, as they obviously contain issues fixed later) from the > snapshot.debian.org service: > > https://snapshot.debian.org/ > > here you can fetch e.g. the 6.9.12 one and re-test it with and them > move stepwise towards the range where things changes. This might help > isolate the problem, but the next step would likely be as well then to > biseect the changes in this closer range. As I understand the > reproduction is as well not immediately. > > > > > > > > > > > > > > > Additionally 6.12.43-1 is not the current trixie kernel, do the hangs > > > > are reproducible with 6.12.48-1 (and the today to be released via the > > > > 13.2 point release) 6.12.57-1? > > > > > > > > > > i've booted to linux-image-6.12.57+deb13-amd64 and i will see what > > happens. > > > > this kernel has also eventually hung after about 10 days. > > Ok bad. I have updated the metadata. > > What you additionally as wel can try is to test the kernels currently > in unstable and see if the problem is triggered there as well, > currently it would be 6.17.8-1 in unstable.
since my last message, i removed an rtl8125 NIC from the machine that had had no cables plugged into it. something on the system, not sure what, was causing the kernel to print these link down messages every few minutes: Nov 25 17:06:22 sokoban kernel: r8169 0000:09:00.0 enp9s0: Link is Down Nov 25 17:14:34 sokoban kernel: r8169 0000:08:00.0 enp8s0: Link is Down Nov 25 17:14:34 sokoban kernel: r8169 0000:09:00.0 enp9s0: Link is Down Nov 25 17:15:43 sokoban kernel: r8169 0000:08:00.0 enp8s0: Link is Down Nov 25 17:15:43 sokoban kernel: r8169 0000:09:00.0 enp9s0: Link is Down Nov 25 17:17:13 sokoban kernel: r8169 0000:08:00.0 enp8s0: Link is Down Nov 25 17:17:13 sokoban kernel: r8169 0000:09:00.0 enp9s0: Link is Down Nov 25 17:25:43 sokoban kernel: r8169 0000:08:00.0 enp8s0: Link is Down Nov 25 17:25:43 sokoban kernel: r8169 0000:09:00.0 enp9s0: Link is Down Nov 25 17:26:01 sokoban kernel: r8169 0000:08:00.0 enp8s0: Link is Down Nov 25 17:26:01 sokoban kernel: r8169 0000:09:00.0 enp9s0: Link is Down Nov 25 17:33:01 sokoban kernel: r8169 0000:08:00.0 enp8s0: Link is Down Nov 25 17:33:01 sokoban kernel: r8169 0000:09:00.0 enp9s0: Link is Down Nov 25 17:35:43 sokoban kernel: r8169 0000:08:00.0 enp8s0: Link is Down Nov 25 17:35:43 sokoban kernel: r8169 0000:09:00.0 enp9s0: Link is Down Nov 25 17:42:28 sokoban kernel: r8169 0000:08:00.0 enp8s0: Link is Down the nic is RTL8125-2.5G-2T-X1 from 10gtek. since i removed the NIC, the machine has been up for 16 days with no reproduction of a hang. shall we close this? i don't really intend to do further debug here. > > Regards, > Salvatore > >
