This kernel in my Trixie installation locks up the computer soon after
boot. It has happened in Firefox, Thunderbird and even in a text editor
as I was writing up a bug report.

I have had to revert to the previous kernel 6.11.10-amd64 .

There is never anything in the logs as the machine locks up tight and
no logs are written.

alt-sysreq REISUB is of no use the machine doesn't respond.

Computer info:

frank@franklin:~$ inxi -F System:
  Host: franklin Kernel: 6.11.10-amd64 arch: x86_64 bits: 64
Desktop: IceWM v: 3.2.3.2
Distro: Debian GNU/Linux trixie/sid
Machine:   Type: Desktop System: LENOVO product: 5536E2F v: ThinkCentre
M90p     serial: <superuser required>   Mobo: LENOVO model: N/A serial:
<superuser required> BIOS: LENOVO     v: 5JKT47AUS date: 07/13/2010 CPU:
   Info: dual core model: Intel Core i5 660 bits: 64 type: MT MCP cache:
     L2: 512 KiB   Speed (MHz): avg: 1197 min/max: 1197/3326 cores: 1:
1197 2: 1197 3: 1197     4: 1197 Graphics:   Device-1: Intel Core
Processor Integrated Graphics driver: i915 v: kernel
Display: x11 server: X.Org v: 21.1.15 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: crocus,swrast
platforms: gbm,x11,surfaceless,device   API: OpenGL v: 4.5 compat-v: 2.1
vendor: intel mesa v: 24.2.8-1     renderer: Mesa Intel HD Graphics
(ILK) Audio:   Device-1: Intel 5 Series/3400 Series High Definition
Audio     driver: snd_hda_intel   API: ALSA v: k6.11.10-amd64 status:
kernel-api   Server-1: PipeWire v: 1.2.7 status: active Network:
Device-1: Intel 82578DM Gigabit Network driver: e1000e   IF: eno1 state:
up speed: 1000 Mbps duplex: full mac: 44:87:fc:d8:3b:53
Drives:   Local Storage: total: 912.89 GiB used: 62.47 GiB (6.8%)
ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB
ID-2: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB
type: USB Partition:   ID-1: / size: 228.61 GiB used: 8.89 GiB (3.9%)
fs: ext4 dev: /dev/sda1 Swap:   Alert: No swap data was found. Sensors:
System Temperatures: cpu: 61.0 C mobo: N/A   Fan Speeds (rpm): N/A Info:
   Memory: total: 8 GiB note: est. available: 7.44 GiB used: 1.78 GiB
(23.9%)   Processes: 189 Uptime: 2h 39m
Shell: Bash
inxi: 3.3.36 frank@franklin:~$

Hi,

Does the problem still happens with the current version available
6.12.15-1 in unstable?

Regards,
Salvatore

Hi,

Does the problem still happens with the current version available
6.12.15-1 in unstable?

Regards,
Salvatore

Hi Frank,

[adding back the bug email so we get the response archived]

Thanks for confirming that.

We need to get some information on the crash. You say the machin does
not react at all, is stil something written in the system log? If not
might you be able to configure a netconsole[1] to get backtrace
remotely maybe before the system is stuck?

The system is neither accessible via SSH remotely?

Regards,
Salvatore

 [1] https://www.kernel.org/doc/html/latest/networking/netconsole.html#netconsole

Sorry for the late reply..I've been busy with non-computer stuff.

   Absolutely nothing written in any log.

   I had a look at netconsole, but this is far above my pay grade ! I
have no idea where to start with this.

   I have never tried accessing this computer from elsewhere as there is
no other computer I have access to.
I find it very strange that the "new" 6.12 series runs perfectly fine on
my OpenSuse Tumbleweed but crashes with a tight lockup on Debian Trixie?

The only difference is that grub is installed on the Tumbleweed
partition not on Trixie. I was forced to do this when I discovered
the Debian mkconfig utility would not install Tumbleweed kernel in
grub.cfg properly. Perhaps because I am running BTRFS on Tumbleweed ?

Frank