Bug#1092103: marked as done (Linux 6.12 freeze on small machine)
Your message dated Sat, 3 May 2025 13:39:34 +0200
with message-id <[🔎] aBYAdr-4DnMC1C78@eldamar.lan>
and subject line Re: Bug#1092103: issue seems gone.
has caused the Debian Bug report #1092103,
regarding Linux 6.12 freeze on small machine
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1092103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092103
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-6.12.6-amd64
Version: 6.12.6-1
Found a case where cpu freeze(100% usage) will occur.
(Tested)Environment:
CPU: 1 or 2 cores.
Memory: <= 1GB
Only tested in Virtual Machine(KVM).
Procedure:
1. Start iperf3 as server on the test machine.
2. On any client machine, start a reversed(download) test to the test machine.
To trigger the case, use 4 threads and 256k block size. Higer value slightly increase the chance.
3.Wait for iperf3 to run.
(4). After a few iteration or at test end, the server will stop responding and completly locked.(no kernel panic log, console just freeze)
>From monitoring platform , the process contained the already freezed vm uses 100% cpu(50% on 2 cores). Charts show the vm linearly increase memory usage to watermark point and never freed them(Because cpu is freezed ?).
Tested on vanilla debian 6.12 and xanmod(no debian patches) 6.12, both freezed.
Tested on xanmod 6.6, no such problem.
Tested on vanilla debian 6.1, no such problem.
--- End Message ---
--- Begin Message ---
Control: tags -1 - moreinfo
Control: fixed -1 6.12.25-1
Hi,
On Sat, May 03, 2025 at 01:57:48PM +0800, GMX wrote:
> Hi. I'm currently using 6.12.25 from xanmod.
>
> The issue seems no longer there. Either tested locally or on cloud vps, no
> such issue now. So I think we can assume that this is fixed now.
Thanks for reporting back, accordingly I will close the bug.
One note about the problem: I did as well test kernel back to the
6.12.6-1 as mentioned initially in the report, and was not able to
trigger there either. So right now I'm not conviced a change between
6.12.6 and 6.12.25 is "fixing" the problem, but I will still close it
now with 6.12.25-1.
Regards,
Salvatore
--- End Message ---
Reply to: