From: owner@bugs.debian.org
This is a multi-part message in MIME format...
Your message dated Sat, 6 Dec 2025 12:53:22 +0100
with message-id <7zalewncoxelmwhfuzxqjkect7mvfuiiadww4s2v2huooi5
hs@p7gxwaigi26x>
and subject line Re: Bug#1114884: Console hangs on 6.1.0-39 while 6.1.0-37
works fine
has caused the Debian Bug report #1114884,
regarding Console hangs on 6.1.0-39 while 6.1.0-37 works fine
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.)
--
1114884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114884
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
Received: (at submit) by bugs.debian.org; 11 Sep 2025 09:18:34 +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=-16.4 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,FOURLA,HAS_PACKAGE,RDNS_NONE,SPF_HELO_NONE,
SPF_SOFTFAIL,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, 51; hammy, 150; neutral, 697; spammy,
0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
0.000-+--X-Debbugs-Cc, 0.000-+--H*x:12.0.0, 0.000-+--H*UA:12.0.0,
0.000-+--H*M:reportbug
Return-path:
Received: from [46.234.254.83] (port=55370 helo=mercury.x3ee.net)
by buxtehude.debian.org with esmtp (Exim 4.96)
(envelope-from )
id 1uwdRo-007jWK-2v
for submit@bugs.debian.org;
Thu, 11 Sep 2025 09:18:34 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Chris Mair
To: Debian Bug Tracking System
Subject: linux-image-6.1.0-39-amd64: AMD Ryzen 9 7950X, linux-im
ge-6.1.0-39-amd64 hangs on boot while 6.1.0-37-amd64 works fine
Message-ID: <175758231026.12377.1084849690899957775.reportbug@mercury.x3ee.net>
X-Mailer: reportbug 12.0.0
Date: Thu, 11 Sep 2025 11:18:30 +0200
Delivered-To: submit@bugs.debian.org
Package: src:linux
Version: 6.1.148-1
Severity: important
X-Debbugs-Cc: chris@1006.org
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I was running Debian 12 on this system fine for over a year. On 2025-09-10 I
did an `apt upgrade` that installed among other things
linux-image-6.1.0-39-amd64 and rebooted afterwards.
until I did an apt upgrade that installed linux-image-6.1.0-39-amd64. Using
this kernel the system hangs after GRUB. It displays the message: hub
[something] config failed, hub doesn't have any ports! (err -19). Apologies I
dont remember the [something] part. The lines is followed by a (normal) line
about root filesystem check. After these to lines the boot process hangs
indefinitely (tried three times). I could bring the system back to live by
going into the Grub menu an booting 6.1.0-37-amd64, which is running fine while
I type this. It looks like there was a regression between 6.1.0-37-amd64 and
6.1.0-39-amd64.
* What exactly did you do (or not do) that was effective (or
ineffective)?
After booting the freshly updated system with 6.1.0-39-amd64, the system hang
at boot. The only effective workaround I found was booting up the previous
kernel 6.1.0-37-amd64 which works fine and which I'm writing this report on.
* What was the outcome of this action?
The `apt upgrade` installed 6.1.0-39-amd64 which made the system hang at boot.
After Grub, it displays the message: "hub [something] config failed, hub
doesn't
have any ports! (err -19)". Apologies I dont remember the [something] part. The
lines is followed by a (normal) line about root filesystem check. After these
to
lines the boot process hangs indefinitely (tried three times).
The workaround was going into the Grub menu and boot 6.1.0-37-amd64 which
works fine.
* What outcome did you expect instead?
I expected the `apt upgrade`, which resulted in installing 6.1.0-39-amd64, to
just work.
*** End of the template - remove these template lines ***
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor: AsrockRack
product_name: RS-8528C SHORTY
product_version: --
chassis_vendor: --
chassis_version: --
bios_vendor: American Megatrends International, LLC.
bios_version: 10.15
board_vendor: ASRockRack
board_name: B650D4U
board_version: 4.00
** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite
Ridge Root Complex [1022:14d8]
Subsystem: ASRock Incorporation Raphael/Granite Ridge Root Complex [1849:14d8]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
|
