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


Groups > linux.debian.kernel > #84813

Bug#1089521: linux-image-6.12.3-amd64 fails to boot due to Oops: invalid opcode: 0000 error

From Jan Binder <jb-debbugs@nlogn.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1089521: linux-image-6.12.3-amd64 fails to boot due to Oops: invalid opcode: 0000 error
Date 2024-12-13 15:30 +0100
Message-ID <JTeQ1-gE7m-3@gated-at.bofh.it> (permalink)
References <JRo77-eHQl-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Thanks for looking into this, disabling the camera works as a stopgap measure 
by putting something like 

blacklist intel_ipu6
blacklist intel_ipu6_isys
blacklist ipu_bridge

into - for example - /etc/modprobe.d/ipu6.conf

6.11 has some other source of instability leading to daily lockups that I 
could not narrow down yet, now I can see if 6.12 is better.

Best,
Jan

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1089521: linux-image-6.12.3-amd64 fails to boot due to Oops: invalid opcode: 0000 error Antoine Cellerier <antoine@cellerier.net> - 2024-12-08 13:00 +0100
  Bug#1089521: linux-image-6.12.3-amd64: ThinkPad X1 Carbon Gen11 6.12.3 failed to boot after upgrade from 6.11 Nico Orru <nigu.orru@gmail.com> - 2024-12-10 21:30 +0100
  Bug#1089521: linux-image-6.12.3-amd64 fails to boot due to Oops: invalid opcode: 0000 error Jan Binder <jb-debbugs@nlogn.org> - 2024-12-13 15:30 +0100
  Processed: "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-12-19 14:10 +0100
  Bug#1089521: linux-image-6.12.3-amd64 fails to boot due to Oops: invalid opcode: 0000 error Salvatore Bonaccorso <carnil@debian.org> - 2024-12-23 11:40 +0100

csiph-web