Control: tags -1 + moreinfo Hi On Sat, Mar 28, 2026 at 01:18:50PM +0100, [email protected] wrote: > Package: linux-image-amd64 > Version: 6.19.6-2~bpo13+1 > Severity: important > > Dear Maintainer, > * What led up to the situation? > The system was running normally on Debian with kernel 6.19.6-2~bpo13+1. > The issue occurred after the system resumed from a suspend (deep > sleep). > > * What exactly did you do (or not do) that was effective (or > ineffective)? > I put the system into suspend and later woke it up. > After resuming, the system appeared to function normally for a short > time. > However, shortly after the resume, the kernel encountered a NULL > pointer > dereference. > > The system then became completely unresponsive (hard freeze). > No reboot or kernel panic occurred, likely because panic_on_oops was > disabled. > > * What was the outcome of this action? > The system froze completely and stopped responding. > There was no visible kernel panic and no automatic reboot. > The only indication of the failure was a kernel message: > mar 28 11:15:09 debian kernel: BUG: kernel NULL pointer dereference, > address: > 000000000000007d > mar 28 11:15:09 debian kernel: #PF: supervisor read access in kernel > mode > mar 28 11:15:09 debian kernel: #PF: error_code(0x0000) - not-present > page > > After this point, the system stopped logging any further messages.
We have a couple of questions here: There are proprietary modules loaded apparently, are you able to reliably trigger the problem without loading the nvidia modules? If so, can you reproduce the issue with the most current version in Debian unstable, resketicvely hopefully soon to be accepted and built 6.19.10 based kernel? Can you please provide us full kernel logs from the boot beginning up to first triggering the issue and then include the full log here in the bugreport? Regards, Salvatore
