Hi Salvatore, Thanks for looking into this. Here is the requested information. Note the sequence of boot: before (6.17.13) -> crash (6.17.13) -> revert to older kernel (6.17.12) -> after (6.17.13). Every subsequent boots after this has been on 6.17.13. - Package Updates: The crash occurred around 11:07. Below is the transaction history for the minutes preceding the boot, taken from /var/log/apt/history.log. systemd, udev, and kmod were *not* updated in this session. The last full-upgrade is actually done on 6.17.12, since I have not booted into 6.17.13 after the error yet. --- Start-Date: 2026-01-01 11:02:55 Commandline: apt upgrade -y Requested-By: ntpt (1000) Install: libmpeg2encpp-2.2-0:amd64 (1:2.2.1-3, automatic), libmplex2-2.2-0:amd64 (1:2.2.1-3, automatic), libmjpegutils-2.2-0:amd64 (1:2.2.1-3, automatic) Upgrade: libatk-bridge2.0-dev:amd64 (2.58.2-1, 2.58.2-2), gstreamer1.0-plugins-ugly:amd64 (1.26.9-1, 1.26.10-1), clang-format:amd64 (1:21.1.6-69, 1:21.1.6-70), mosquitto-clients:amd64 (2.0.22-3, 2.0.22-4), fonts-lyx:amd64 (2.4.4-2, 2.5.0~RC2-1), gir1.2-gstreamer-1.0:amd64 (1.26.9-1, 1.26.10-1), gstreamer1.0-gl:amd64 (1.26.9-1, 1.26.10-1), npm:amd64 (9.2.0~ds2-1, 9.2.0~ds2-2), clangd:amd64 (1:21.1.6-69, 1:21.1.6-70), libgdm1:amd64 (49.2-2, 49.2-3), at-spi2-core:amd64 (2.58.2-1, 2.58.2-2), libatspi2.0-dev:amd64 (2.58.2-1, 2.58.2-2), libgstreamer-gl1.0-0:amd64 (1.26.9-1, 1.26.10-1), libges-1.0-0:amd64 (1.26.9-1, 1.26.10-1), node-mkdirp:amd64 (2.1.6+~cs5.2.1-4, 2.1.6+~cs5.2.1-5), gir1.2-gst-plugins-base-1.0:amd64 (1.26.9-1, 1.26.10-1), libvdpau1:amd64 (1.5-3+b1, 1.5-4), libatspi2.0-0t64:amd64 (2.58.2-1, 2.58.2-2), libegl1-mesa-dev:amd64 (25.2.8-2+b3, 25.3.2-2), gdm3:amd64 (49.2-2, 49.2-3), gstreamer1.0-x:amd64 (1.26.9-1, 1.26.10-1), libatk-adaptor:amd64 (2.58.2-1, 2.58.2-2), libgstreamer-plugins-bad1.0-0:amd64 (1.26.9-1, 1.26.10-1), gstreamer1.0-gtk3:amd64 (1.26.9-1, 1.26.10-1), libatk1.0-dev:amd64 (2.58.2-1, 2.58.2-2), gstreamer1.0-plugins-good:amd64 (1.26.9-1, 1.26.10-1), gstreamer1.0-plugins-base:amd64 (1.26.9-1, 1.26.10-1), node-tap:amd64 (16.3.7+ds3+~cs49.5.20-5, 16.3.7+ds3+~cs49.5.20-6), node-tar:amd64 (6.2.1+ds1+~cs6.1.13-4, 6.2.1+ds1+~cs6.1.13-5), mesa-vulkan-drivers:amd64 (25.2.8-2+b3, 25.3.2-2), node-which:amd64 (2.0.2+~cs1.3.2-3, 2.0.2+~cs1.3.2-4), libnautilus-extension4:amd64 (49.2-1, 49.2-2), libatk1.0-0t64:amd64 (2.58.2-1, 2.58.2-2), gir1.2-gdm-1.0:amd64 (49.2-2, 49.2-3), libgstreamer1.0-0:amd64 (1.26.9-1, 1.26.10-1), gir1.2-atk-1.0:amd64 (2.58.2-1, 2.58.2-2), gir1.2-gst-plugins-bad-1.0:amd64 (1.26.9-1, 1.26.10-1), clang:amd64 (1:21.1.6-69, 1:21.1.6-70), nautilus:amd64 (49.2-1, 49.2-2), nautilus-data:amd64 (49.2-1, 49.2-2), gstreamer1.0-plugins-bad:amd64 (1.26.9-1, 1.26.10-1), libgstreamer-plugins-base1.0-0:amd64 (1.26.9-1, 1.26.10-1), libmosquitto1:amd64 (2.0.22-3, 2.0.22-4), gstreamer1.0-libav:amd64 (1.26.9-1+b1, 1.26.10-1), clang-tidy:amd64 (1:21.1.6-69, 1:21.1.6-70), libatk-bridge2.0-0t64:amd64 (2.58.2-1, 2.58.2-2), at-spi2-common:amd64 (2.58.2-1, 2.58.2-2), gir1.2-atspi-2.0:amd64 (2.58.2-1, 2.58.2-2) End-Date: 2026-01-01 11:03:13 Start-Date: 2026-01-01 11:04:20 Commandline: apt autoremove Requested-By: ntpt (1000) Remove: libmjpegutils-2.1-0t64:amd64 (1:2.1.0+debian-8.1+b1), vdpau-driver-all:amd64 (1.5-3+b1), libvdpau-va-gl1:amd64 (0.4.2-2), libmplex2-2.1-0t64:amd64 (1:2.1.0+debian-8.1+b1), libmpeg2encpp-2.1-0t64:amd64 (1:2.1.0+debian-8.1+b1), mesa-vdpau-drivers:amd64 (25.2.8-2+b3) End-Date: 2026-01-01 11:04:21 Start-Date: 2026-01-01 11:28:59 Commandline: apt full-upgrade Requested-By: ntpt (1000) Upgrade: libglx-mesa0:amd64 (25.2.8-2+b3, 25.3.2-2), libgbm1:amd64 (25.2.8-2+b3, 25.3.2-2), mesa-libgallium:amd64 (25.2.8-2+b3, 25.3.2-2), libgl1-mesa-dri:amd64 (25.2.8-2+b3, 25.3.2-2), libegl-mesa0:amd64 (25.2.8-2+b3, 25.3.2-2) Remove: mesa-va-drivers:amd64 (25.2.8-2+b3) End-Date: 2026-01-01 11:29:01 --- - Systemd Version Current version: 259-1 (dpkg -l systemd) - Logs: I have attached the requested journals (exported via journalctl -b -<boot_num>). boot_before.log: The successful boot prior, on 6.17.13. boot_crash.log: The boot where the NULL pointer dereference occurred. boot_revert.log: The boot where I revert back to 6.17.12. boot_after.log: The subsequent successful boot on 6.17.13. I have not found the time yet to test 6.18. I am providing the logs for 6.17 first. I hope the provided information are helpful. Regards, Nguyễn Trần Phước Thành On Fri, Jan 2, 2026 at 12:59 AM Salvatore Bonaccorso <carnil@debian.org> wrote: > > Control: tags -1 + moreinfo unreachable upstream > > Hi, > > On Thu, Jan 01, 2026 at 09:33:35PM +0700, Nguyen Tran Phuoc Thanh wrote: > > Package: src:linux > > Version: 6.17.13-1 > > Severity: important > > X-Debbugs-Cc: tranphuocthanh01@gmail.com > > > > Dear Maintainer, > > > > * What led up to the situation? > > > > I noticed that my system is taking longer than usual to boot, so I > > investigated and found that the systemd-modules service hanging for > > quite long (>2 mins). > > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > > > I hard-resetted the laptop and changed to an older kernel. After some > > searching around, I tried to recreate the problem unsuccessfully. > > Subsequent boots of this suspected kernel did not exhibit the error. > > > > I noticed Bug #1124075 regarding lp crashes in 6.17.12, which is the > > closest to what I'm having. I tried the reporter approach of manually > > unloading and loading lp/parport using 'sudo modprobe -v lp' and 'sudo > > modprobe -v parport'. Found no error with 'dmesg -w'. parport can not be > > unloaded due to being in use. > > > > Here's the excerpt from the journalctl command for the boot with error: > > Okay, bad, this means that likely #1124075 is not really resolved but > just does not "easily" reproduce on each invocation, as it was a one > shoot as well in the original reporters case. > > Which other packages were updated before the reboot with the suspected > kernel? > > Can you please provide the *full* journal from the boot with the > problem and the same for the subsequent boot without issue. And > ideally as well the one before booting into the problematic one. > > It would as well be intersting to know which systemd version was > running at each of the occurences. > > As there won't be any furhter updates to the 6.17.y series, if you > install and boot 6.18.2-1~exp1 from experimental I assume you still > gen no reproduction of the problem? > > Regards, > Salvatore
Attachment:
boot_revert.log.gz
Description: application/gzip
Attachment:
boot_bad.log.gz
Description: application/gzip
Attachment:
boot_after.log.gz
Description: application/gzip
Attachment:
boot_prev.log.gz
Description: application/gzip