RC5 seemed to have resolved the issue I was having, I was unable to test with RC4 due to uninstalling it after the panic and not being able to test till today. Booting rc5 with and without the blacklist for parport_pc does not result in a panic.
On Sun, May 24, 2026 at 10:52 AM Jennifer Riley <[email protected]> wrote: > It would crash every boot after upgrading from rc3 to rc4, although the > log I reported was the only time it showed a QR kernel panic. I was able to > boot to desktop once but the system immediately clicked off once desktop > was reached. > > I will test "blacklist=parport_pc" in the next day or so when I have the > time. > > On Sun, May 24, 2026 at 9:34 AM Ben Hutchings <[email protected]> wrote: > >> Control: tag -1 moreinfo >> >> On Wed, 2026-05-20 at 23:23 +0200, Salvatore Bonaccorso wrote: >> > Hi, >> > >> > On Wed, May 20, 2026 at 02:06:58PM -0700, Jennifer Riley wrote: >> > > Package: linux-image-7.1-amd64 >> > > Version: linux-image-7.1-amd64 >> > > Severity: critical >> > > Justification: breaks the whole system >> > > X-Debbugs-Cc: [email protected] >> > > >> > > Dear Maintainer, >> > > >> > > after upgrade to kernel 7.1 rc4 >> [...] >> > This might be another instance of #1124075, but I'm not merging them >> > yet. Ben? >> >> It does look similar, although there isn't anything in the log >> definitely connecting the crash to the parport subsystem. >> >> Jennifer - did this only happen once, or does it happen every time (or >> very often) when you try to boot this version? >> >> If it happens often, does adding "blacklist=parport_pc" to the kernel >> command line fix the problem? >> >> Ben. >> >> -- >> Ben Hutchings - Debian developer, member of kernel, installer and LTS >> teams >> >
