From: Adam Stylinski <kungfujesus06@gmail.com>
To: linux-pci@vger.kernel.org
Cc: bhelgaas@google.com
Subject: Kernel regression in 6.13
Date: Mon, 15 Dec 2025 19:54:46 -0500 [thread overview]
Message-ID: <aUCt1tHhm_-XIVvi@eggsbenedict> (raw)
Hello,
I seem to be encountering a regression that prevents my system from booting. The regression occurred between 6.12 and 6.13. I've bisected it to this commit:
665745f274870c921020f610e2c99a3b1613519b
Some info about this system: it's ancient. It's a Q9650 that I used as a mythbackend/frontend for over a decade. This booting failure on newer kernels finally forced my hand to buy new a "new" PCI Express based tuner and upgrade the system into the modern age. It boots via MBR on a P45 based chipset (A P5Q Plus board, to be precise). Given the age, I chalked the issue up to possibly some failing hardware or memory corruption that happened at compile time. I recently pulled the system back out again to do some performance testing in zlib-ng only to find out it hangs on the latest Ubuntu server ISO. I figured at this point it wasn't something specific to my kernel config / compilation and it's likely a regression. It's also old enough that I may be in the position of the only one having this problem, so I took it upon myself to bisect what was going on. Let me know if there's anything you'd like me to test or try.
next reply other threads:[~2025-12-16 0:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 0:54 Adam Stylinski [this message]
2025-12-16 9:49 ` Kernel regression in 6.13 Ilpo Järvinen
2025-12-16 13:57 ` Adam Stylinski
2025-12-16 14:14 ` Ilpo Järvinen
2025-12-16 14:23 ` Adam Stylinski
2025-12-18 13:54 ` Ilpo Järvinen
[not found] ` <aURK74sGvdTGBMdb@eggsbenedict>
[not found] ` <3fd99997-a639-d971-e43e-bcc973aa6d04@linux.intel.com>
[not found] ` <aUWG4H3GH-k2ebpa@eggsbenedict>
[not found] ` <aVyBBOXXDEN8dses@thinkpad>
[not found] ` <2c078897-3a1e-a016-1d93-237cfb71fb94@linux.intel.com>
[not found] ` <aWgnZLSenkOiXiuM@thinkpad>
2026-01-14 23:40 ` Adam Stylinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aUCt1tHhm_-XIVvi@eggsbenedict \
--to=kungfujesus06@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox