From: owner@bugs.debian.org
This is a multi-part message in MIME format...
Your message dated Sat, 01 Nov 2025 20:49:51 +0100 (CET)
with message-id <20251101194951.4EC70BE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1111722,
regarding linux-image-6.12.38+deb13-amd64: Intermittent system-wide freezes,
both random and triggered by high-resource apps
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.)
--
1111722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111722
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
Received: (at submit) by bugs.debian.org; 21 Aug 2025 12:48:36 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
(2024-03-25) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-9.7 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FOURLA,
FREEMAIL_FROM,FVGT_m_MULTI_ODD,HAS_PACKAGE,NML_ADSP_CUSTOM_MED,
RCVD_IN_PBL,RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,
RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,RDNS_NONE,
SPF_SOFTFAIL,SPOOFED_FREEMAIL,SPOOFED_FREEMAIL_NO_RDNS,SPOOF_GMAIL_MID,
WORD_WITHOUT_VOWELS,XMAILER_REPORTBUG autolearn=ham autolearn_force=no
version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 486; hammy, 150; neutral, 1732; spammy,
0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
0.000-+--X-Debbugs-Cc, 0.000-+--python3, 0.000-+--sk:taint_o,
0.000-+--sk:TAINT_O
Return-path:
Received: from [41.227.237.181] (port=37392 helo=[127.0.1.1])
by buxtehude.debian.org with esmtp (Exim 4.96)
(envelope-from )
id 1up4iZ-00D6eM-0x
for submit@bugs.debian.org;
Thu, 21 Aug 2025 12:48:36 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Ousama Halmous
To: Debian Bug Tracking System
Subject: linux-image-6.12.38+deb13-amd64: Intermittent system-wide freezes,
both random and triggered by high-resource apps
Message-ID: <175578051030.131544.571373155081723870.reportbug@halmas>
X-Mailer: reportbug 13.2.0
Date: Thu, 21 Aug 2025 13:48:30 +0100
Delivered-To: submit@bugs.debian.org
Package: src:linux
Version: 6.12.38-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-amd64@lists.debian.org, halmousousama@gmail.com
User: debian-amd64@lists.debian.org
Usertags: amd64
Description of the Bug:
The system experiences intermittent, complete freezes that manifest in two
distinct scenarios:
Scenario A: Application-induced Freeze
---------------------------------------
When a specific application (e.g., a web browser with many tabs) starts
consuming a very high amount of memory or CPU, it can cause the entire system
to freeze.
I want to clarify that this is distinct from a recoverable Out-of-Memory (OOM)
event. For instance, the attached dmesg log shows a case where the OOM killer
successfully terminated the 'lm-studio' process, and the system recovered
correctly. The freezes
I am reporting are different: the system becomes completely unresponsive and
does not recover, requiring a hard reset.
Scenario B: Sudden, Unexplained Freeze
--------------------------------------
The system also freezes randomly without any obvious trigger. The effect is
identical to Scenario A: the entire screen stops updating (like a paused
video), and the system becomes completely unresponsive.
In both scenarios, the only way to recover is a forced shutdown by holding
down the power button. No kernel panic is displayed, and Ctrl+Alt F* keys to
switch to a console do not work.
Diagnostic Steps Taken:
I do not currently have logs from the last time either of these freezes
occurred.
However, I have now enabled the Magic SysRq key (`kernel.sysrq = 1`). On the
next freeze, regardless of the scenario, I will attempt a safe reboot using
the `REISUB` sequence. I will then update this bug report with the logs from
the previous boot by
running `journalctl -b -1`.
Please let me know if there are other diagnostic steps I should take or
specific information I can provide the next time this occurs.
-- Package-specific info:
** Version:
Linux version 6.12.38+deb13-amd64 (debian-kernel@lists.debian.org)
(x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for
Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Debian 6.12.38-1 (2025-07-16)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.12.38+deb13-amd64 root=UUID=e1eccd3c-
7a0-477b-82a7-c37e3a7fc100 ro quiet
** Tainted: OE (12288)
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
[22118.590649] [ 2689] 1000 2689 682824 4371 756
3615 0 253952 544 200 gjs
[continued in next message]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
