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: [email protected] > > 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
