Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #90916 > unrolled thread
| Started by | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| First post | 2026-01-22 08:40 +0100 |
| Last post | 2026-01-22 09:00 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1126128: linux-image-6.17.13+deb14-amd64: Oops at boot time about parport_register_dev_model Salvatore Bonaccorso <carnil@debian.org> - 2026-01-22 08:40 +0100
Processed: Re: Bug#1126128: linux-image-6.17.13+deb14-amd64: Oops at boot time about parport_register_dev_model "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-01-22 08:40 +0100
Bug#1126128: linux-image-6.17.13+deb14-amd64: Oops at boot time about parport_register_dev_model Giuseppe Sacco <eppesuig@debian.org> - 2026-01-22 09:00 +0100
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2026-01-22 08:40 +0100 |
| Subject | Bug#1126128: linux-image-6.17.13+deb14-amd64: Oops at boot time about parport_register_dev_model |
| Message-ID | <MfXsm-cnNz-3@gated-at.bofh.it> |
Control: forcemerge 1124463 -1 Hi, On Thu, Jan 22, 2026 at 07:47:50AM +0100, Giuseppe Sacco wrote: > Package: src:linux > Version: 6.17.13-1 > Severity: normal > > Dear Maintainer, > > * What led up to the situation? > > This is a debian testing machine that I update every day. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > I just booted the machine. The kernel panic appeared on the boot > screen. I waited a minute, then long depressed the power button in > order to switch off the computer. Then I powered it up again and the > boot when fine. I did not take a photo of the screen, but a kernel Oops > is the journal. I am attaching it here. > > * What was the outcome of this action? > > The computer was not usable. The screen showing a kernel Oops and, on > the first line of the console, new messages where apearing. At a > glance, they were still stack trace from kernel Oops. > > * What outcome did you expect instead? > > A normal boot. > > Here is the journal I was referring about: > > gen 22 07:22:44 collutorio kernel: EXT4-fs (nvme0n1p6): re-mounted 7db9ea79-87e7-4e31-bf38-4cee76438742 r/w. > gen 22 07:22:44 collutorio systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems. > gen 22 07:22:44 collutorio systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (C> > gen 22 07:22:44 collutorio kernel: ppdev: user-space parallel port driver > gen 22 07:22:44 collutorio systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition ch> > gen 22 07:22:44 collutorio systemd[1]: Starting systemd-random-seed.service - Load/Save OS Random Seed... > gen 22 07:22:44 collutorio systemd[1]: systemd-tpm2-setup.service - TPM SRK Setup was skipped because of an unmet condition check (ConditionSecur> > gen 22 07:22:44 collutorio systemd[1]: systemd-pcrnvdone.service - TPM PCR NvPCR Initialization Separator was skipped because of an unmet conditi> > gen 22 07:22:44 collutorio kernel: ppdev lp.0: really_probe: driver_sysfs_add failed > gen 22 07:22:44 collutorio kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0) > gen 22 07:22:44 collutorio kernel: BUG: unable to handle page fault for address: ffff8987d5cc5e88 > gen 22 07:22:44 collutorio kernel: #PF: supervisor instruction fetch in kernel mode > gen 22 07:22:44 collutorio kernel: #PF: error_code(0x0011) - permissions violation > gen 22 07:22:44 collutorio kernel: PGD 3fe401067 P4D 3fe401067 PUD 10161f063 PMD 107bc5063 PTE 8000000115cc5163 > gen 22 07:22:44 collutorio kernel: Oops: Oops: 0011 [#1] SMP NOPTI > gen 22 07:22:44 collutorio kernel: CPU: 8 UID: 0 PID: 432 Comm: systemd-modules Not tainted 6.17.13+deb14-amd64 #1 PREEMPT(lazy) Debian 6.17.13-1 > gen 22 07:22:44 collutorio kernel: Hardware name: Dell Inc. Latitude 5440/03J519, BIOS 1.16.0 07/08/2024 > gen 22 07:22:44 collutorio kernel: RIP: 0010:0xffff8987d5cc5e88 > gen 22 07:22:44 collutorio kernel: Code: ff ff 80 01 20 c1 87 89 ff ff 20 4c 53 99 ff ff ff ff 70 47 c9 d6 87 89 ff ff 01 00 00 00 07 00 00 00 00 00 00 00 00 00 00 00 <88> 5e cc d5 87 89 ff ff 88 5e cc d5 87 89 ff ff 00 00 00 00 00 00 > gen 22 07:22:44 collutorio kernel: RSP: 0018:ffffd1818095fb60 EFLAGS: 00010286 > gen 22 07:22:44 collutorio kernel: RAX: ffff8987d5cc5e88 RBX: ffff8987e8882000 RCX: 0000000000000007 > gen 22 07:22:44 collutorio kernel: RDX: ffffffffc1678ac0 RSI: ffff8987c2d89390 RDI: ffff8987e5486400 > gen 22 07:22:44 collutorio kernel: RBP: ffffd1818095fbb8 R08: 00000000fffffff3 R09: ffffd1818095f758 > gen 22 07:22:44 collutorio kernel: R10: 0000000000000000 R11: 00000000ffffefff R12: ffff8987e8882040 > gen 22 07:22:44 collutorio kernel: R13: ffff8987e5486450 R14: ffff8987e5486400 R15: ffff8987c10bc4a0 > gen 22 07:22:44 collutorio kernel: FS: 00007f19909ff6c0(0000) GS:ffff898ba4a08000(0000) knlGS:0000000000000000 > gen 22 07:22:44 collutorio kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > gen 22 07:22:44 collutorio kernel: CR2: ffff8987d5cc5e88 CR3: 0000000117351006 CR4: 0000000000f70ef0 > gen 22 07:22:44 collutorio kernel: PKRU: 55555554 > gen 22 07:22:44 collutorio kernel: Call Trace: > gen 22 07:22:44 collutorio kernel: <TASK> > gen 22 07:22:44 collutorio kernel: ? parport_register_dev_model+0x26c/0x340 [parport] > gen 22 07:22:44 collutorio kernel: ? lp_register+0x86/0x1b0 [lp] > gen 22 07:22:44 collutorio kernel: ? __pfx_lp_preempt+0x10/0x10 [lp] > gen 22 07:22:44 collutorio kernel: ? __pfx_port_check+0x10/0x10 [parport] > gen 22 07:22:44 collutorio kernel: ? lp_attach+0x89/0x110 [lp] > gen 22 07:22:44 collutorio kernel: ? port_check+0x24/0x30 [parport] > gen 22 07:22:44 collutorio kernel: ? bus_for_each_dev+0x82/0xd0 > gen 22 07:22:44 collutorio kernel: ? __parport_register_driver+0x82/0xb0 [parport] > gen 22 07:22:44 collutorio kernel: ? lp_init_module+0x39f/0xff0 [lp] > gen 22 07:22:44 collutorio kernel: ? __pfx_lp_init_module+0x10/0x10 [lp] > gen 22 07:22:44 collutorio kernel: ? do_one_initcall+0x58/0x300 > gen 22 07:22:44 collutorio kernel: ? do_init_module+0x62/0x250 > gen 22 07:22:44 collutorio kernel: ? init_module_from_file+0x8a/0xe0 > gen 22 07:22:44 collutorio kernel: ? init_module_from_file+0x8a/0xe0 > gen 22 07:22:44 collutorio kernel: ? idempotent_init_module+0x114/0x310 > gen 22 07:22:44 collutorio kernel: ? __x64_sys_finit_module+0x6d/0xd0 > gen 22 07:22:44 collutorio kernel: ? do_syscall_64+0x82/0x320 > gen 22 07:22:44 collutorio kernel: ? do_user_addr_fault+0x21a/0x690 > gen 22 07:22:44 collutorio kernel: ? exc_page_fault+0x74/0x180 > gen 22 07:22:44 collutorio kernel: ? entry_SYSCALL_64_after_hwframe+0x76/0x7e > gen 22 07:22:44 collutorio kernel: </TASK> > gen 22 07:22:44 collutorio kernel: Modules linked in: parport_pc dm_mod(+) lp(+) ppdev parport msr(+) i2c_dev efi_pstore nfnetlink efivarfs autofs4 ext4 crc16 mbcache jbd2 crc32c_cryptoapi xe drm_gpuvm configfs drm_gpusvm_helper gpu_sched drm_ttm_helper drm_exec drm_suballoc_helper hid_sensor_custom hid_sensor_hub intel_ishtp_hid i915 nvme nvme_core nvme_keyring nvme_auth ahci libahci drm_buddy ucsi_acpi typec_ucsi ttm libata typec roles i2c_algo_bit drm_display_helper scsi_mod hid_multitouch hid_generic cec scsi_common rc_core i2c_hid_acpi drm_client_lib i2c_hid drm_kms_helper hid iTCO_wdt intel_pmc_bxt iTCO_vendor_support drm xhci_pci watchdog psmouse xhci_hcd intel_lpss_pci serio_raw usbcore thunderbolt e1000e intel_ish_ipc i2c_i801 button intel_lpss video battery intel_ishtp intel_vsec i2c_smbus vmd usb_common wmi idma64 > gen 22 07:22:44 collutorio kernel: CR2: ffff8987d5cc5e88 > gen 22 07:22:44 collutorio kernel: ---[ end trace 0000000000000000 ]--- > gen 22 07:22:44 collutorio kernel: RIP: 0010:0xffff8987d5cc5e88 > gen 22 07:22:44 collutorio kernel: Code: ff ff 80 01 20 c1 87 89 ff ff 20 4c 53 99 ff ff ff ff 70 47 c9 d6 87 89 ff ff 01 00 00 00 07 00 00 00 00 00 00 00 00 00 00 00 <88> 5e cc d5 87 89 ff ff 88 5e cc d5 87 89 ff ff 00 00 00 00 00 00 > gen 22 07:22:44 collutorio kernel: RSP: 0018:ffffd1818095fb60 EFLAGS: 00010286 > gen 22 07:22:44 collutorio kernel: RAX: ffff8987d5cc5e88 RBX: ffff8987e8882000 RCX: 0000000000000007 > gen 22 07:22:44 collutorio kernel: RDX: ffffffffc1678ac0 RSI: ffff8987c2d89390 RDI: ffff8987e5486400 > gen 22 07:22:44 collutorio kernel: RBP: ffffd1818095fbb8 R08: 00000000fffffff3 R09: ffffd1818095f758 > gen 22 07:22:44 collutorio kernel: R10: 0000000000000000 R11: 00000000ffffefff R12: ffff8987e8882040 > gen 22 07:22:44 collutorio kernel: R13: ffff8987e5486450 R14: ffff8987e5486400 R15: ffff8987c10bc4a0 > gen 22 07:22:44 collutorio kernel: FS: 00007f19909ff6c0(0000) GS:ffff898ba4a08000(0000) knlGS:0000000000000000 > gen 22 07:22:44 collutorio kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > gen 22 07:22:44 collutorio kernel: CR2: ffff8987d5cc5e88 CR3: 0000000117351006 CR4: 0000000000f70ef0 > gen 22 07:22:44 collutorio kernel: PKRU: 55555554 > gen 22 07:22:44 collutorio kernel: note: systemd-modules[432] exited with irqs disabled This looks the same as #1124463. If you can reliably reproduce the issue (it is not for other known reporters), it might be helpful if you can test https://lore.kernel.org/all/aVj-mz8vaw53TWtX@debian/ . Regards, Salvatore
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2026-01-22 08:40 +0100 |
| Subject | Processed: Re: Bug#1126128: linux-image-6.17.13+deb14-amd64: Oops at boot time about parport_register_dev_model |
| Message-ID | <MfXsm-cnNz-9@gated-at.bofh.it> |
| In reply to | #90916 |
Processing control commands: > forcemerge 1124463 -1 Bug #1124463 [src:linux] linux-image-6.17.13+deb14-amd64: One time kernel NULL pointer dereference, trace shows lp and parport Bug #1124075 [src:linux] linux-image-6.17.12+deb14-amd64: Kernel Oops (GPF) in idempotent_init_module when loading lp module Bug #1126128 [src:linux] linux-image-6.17.13+deb14-amd64: Oops at boot time about parport_register_dev_model Set Bug forwarded-to-address to 'https://lore.kernel.org/all/6ba903ad-9897-42bb-8c2d-337385cc3746@molgen.mpg.de/'. Severity set to 'important' from 'normal' Marked as found in versions linux/6.17.12-1. Added tag(s) upstream. Bug #1124075 [src:linux] linux-image-6.17.12+deb14-amd64: Kernel Oops (GPF) in idempotent_init_module when loading lp module Merged 1124075 1124463 1126128 -- 1124075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124075 1124463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124463 1126128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126128 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Giuseppe Sacco <eppesuig@debian.org> |
|---|---|
| Date | 2026-01-22 09:00 +0100 |
| Message-ID | <MfXLH-cnVP-3@gated-at.bofh.it> |
| In reply to | #90916 |
Hi Salvatore, Il giorno gio, 22/01/2026 alle 08.29 +0100, Salvatore Bonaccorso ha scritto: [...] > This looks the same as #1124463. If you can reliably reproduce the > issue (it is not for other known reporters), it might be helpful if > you can test https://lore.kernel.org/all/aVj-mz8vaw53TWtX@debian/ . Upon five boots today, only the first one gave the error. Anyway, I'll add your patch and let you know during next days. Bye, Giuseppe
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web