Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #89702 > unrolled thread

Bug#1118508: linux-image-6.12.38+deb13-amd64: Frequent kernel panic during/just after boot on Lenovo P15v Gen1 with external USB hub in Samsung display

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.

Contents

  Bug#1118508: linux-image-6.12.38+deb13-amd64: Frequent kernel panic during/just after boot on Lenovo P15v Gen1 with external USB hub in Samsung display Salvatore Bonaccorso <carnil@debian.org> - 2025-10-21 20:50 +0200
    Bug#1118508: linux-image-6.12.38+deb13-amd64: Frequent kernel panic during/just after boot on Lenovo P15v Gen1 with external USB hub in Samsung display Rimas Kudelis <rimas@kudelis.lt> - 2025-10-21 21:40 +0200
      Bug#1118508: linux-image-6.12.38+deb13-amd64: Frequent kernel panic during/just after boot on Lenovo P15v Gen1 with external USB hub in Samsung display Salvatore Bonaccorso <carnil@debian.org> - 2025-10-21 22:00 +0200

#89702 — Bug#1118508: linux-image-6.12.38+deb13-amd64: Frequent kernel panic during/just after boot on Lenovo P15v Gen1 with external USB hub in Samsung display

Control: tags -1 + moreinfo

Hi,

On Tue, Oct 21, 2025 at 03:37:25PM +0300, Rimas Kudelis wrote:
> Source: src:linux
> Severity: important
> 
> Dear Maintainer,
> 
> quite often, when booting my PC, I get a kernel panic (the computer hangs
> and the caps lock led blinks) at boot time, or just after it ends. I suspect
> this might be related with me typing my password, or moving a mouse at an
> unfortunate time (too early, something still initializing?), but I'm not
> certain that this is it.
> 
> Once the system boots successfully and I log in, the kernel panic doesn't
> happen.
> 
> For example, today, the kernel panic happened when I submitted my password
> to the GDM login screen. I think I also had it happen while entering my LUKS
> password at least once. Also, the PC actually crashed the first time I
> booted it after installing Trixie, causing me to delay trying Trixie out for
> a couple weeks.
> 
> My setup is a Lenovo P15v laptop, which is connected via USB-C to a Samsung
> LS27A600UUU (27" ViewFinity S60UA QHD, USB-C Monitor), to which my keyboard
> and mouse combo are connected via USB-A port, as well as a second 27"
> Samsung display via the DP-OUT port. I suspect that maybe this complexity
> could have something to do with the freezes and be the reason why they
> haven't been noticed and caught until now.
> 
> I don't think it's a faulty hardware issue however, because I have used
> Pop!_OS 22.04 for several years now (it still resides on my second SSD
> disk), which *never* exhibited such behavior.

6.12.38-1 is not the most current kernel available in trixie, pliease
do update to 6.12.48-1 and let us please know if the problem persist.

If yes, then we would need (ideally a full) boot log, but if nothing
get recorded in logs, then the netconsole[1] approach might help

[1] https://docs.kernel.org/networking/netconsole.html

On UEFI system pstore alterantively might help us as well.

But first upgrade your kernel to the most current one in trixie, to
determine if the problem persists.

Regards,
Salvatore

[toc] | [next] | [standalone]

#89703

Hi,

disregard the original subject line, I actually upgraded to 6.12.48 this 
morning and reported the bug with that kernel already in use, as 
indicated in the System Information block.

I'll see about the logs. I don't tend to reboot often, and when I 
checked with `journalctl -b-1` (and other numbers) today, I didn't see 
anything weird at the end of these logs: they all indicated successful 
logouts. I suspect they aren't being saved for some reason. I'll look at 
them again the next time Trixie crashes on boot.

Regards,
Rimas


2025-10-21 21:45, Salvatore Bonaccorso rašė:
> If yes, then we would need (ideally a full) boot log, but if nothing
> get recorded in logs, then the netconsole[1] approach might help
> 
> [1] https://docs.kernel.org/networking/netconsole.html
> 
> On UEFI system pstore alterantively might help us as well.
> 
> But first upgrade your kernel to the most current one in trixie, to
> determine if the problem persists.

[toc] | [prev] | [next] | [standalone]

#89705

Hi Rimas,

On Tue, Oct 21, 2025 at 09:54:39PM +0300, Rimas Kudelis wrote:
> Hi,
> 
> disregard the original subject line, I actually upgraded to 6.12.48 this
> morning and reported the bug with that kernel already in use, as indicated
> in the System Information block.

Thanks, I have updated the metadata.

> I'll see about the logs. I don't tend to reboot often, and when I checked
> with `journalctl -b-1` (and other numbers) today, I didn't see anything
> weird at the end of these logs: they all indicated successful logouts. I
> suspect they aren't being saved for some reason. I'll look at them again the
> next time Trixie crashes on boot.

Okay let's see if we can get further information on the crashes.

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web