Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20

Bug #2017444 reported by Jan Saarinen
32
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Lunar
Fix Released
High
Unassigned
linux-firmware (Ubuntu)
Invalid
Undecided
Unassigned
Lunar
Invalid
Undecided
Unassigned

Bug Description

== SRU Justification ==
[Impact]
Some Atom based system cannot boot on kernel 6.2 because of atomisp
driver.

[Fix]
Disable the driver via config, suggested by the driver dev.

[Test]
Users confirmed disabling the config works.

[Where problems could occur]
The ISP camera dever worked on Linux. So disabling it shouldn't
introduce any surprise.

== Original Bug Report ==
Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR any other Kernel in 6.2 series or Kernel 6.3.0.

This bug affects all Intel Atom CPU computers in all Linux distributions making impossible to install or boot to OS with kernel 6.2 or higher.

The bug is caused by Intel atomisp camera driver module which has firmware missing: shisp_2401a_v21.bin. Missing firmware causes a watchdog bug notice and Soft Lockup of boot sequence.

NEW SOLUTION AND NOTICE TO UBUNTU KERNEL MAINTAINERS, April 29th:
The following persons are in charge of atomisp kernel development:

Hans de Goede <email address hidden> (maintainer:STAGING - ATOMISP DRIVER)
Mauro Carvalho Chehab <email address hidden> (maintainer:STAGING - ATOMISP DRIVER)
Sakari Ailus <email address hidden> (reviewer:STAGING - ATOMISP DRIVER)
Greg Kroah-Hartman <email address hidden> (supporter:STAGING SUBSYSTEM)
<email address hidden> (open list:STAGING - ATOMISP DRIVER)
<email address hidden> (open list:STAGING SUBSYSTEM)
<email address hidden> (open list)

April 29th Hans de Goede adviced me personally( https://github.com/linux-surface/linux-surface/issues/1095 ), that atomisp driver is still in development and should be disabled. By disabling driver he meant disabling atomisp modules in kernel.

OLD SOLUTION FOR THIS BUG:

Copying (installing) firmware shisp_2401a0_v21.bin from:

https://github.com/intel-aero/meta-intel-aero-base/blob/master/recipes-kernel/linux/linux-yocto/shisp_2401a0_v21.bin

to /lib/firmware will solve the bug (partially - it still gives error messages - but at least the computer boots).**

(dmesg.log with shisp-file with kernel 6.2.0-06 and 6.3.0-06 as attachments 9. and 10.)

(Another solution - which Manjaro kernel maintainer did - was to disable atomisp and related modules).

Afterwards Intel Atom CPU computer will be able to boot with kernel 6.2.

DMESG.LOG OF KUBUNTU 23.04 LIVE USB AND MORE INFORMATION IN: https://askubuntu.com/questions/1464926/not-able-to-boot-kubuntu-23-04-with-kernel-6-2-and-intel-atom-cpu

The last stable Ubuntu Kernel Intel Atom CPU computer will boot with is 6.1.25.

This bug was already in 5.19, as you can see from dmesg.logs. It appears that atomisp failes to launch in both 5.19.0-40 and 6.1.25 but still the computer boots.

This bug is also reported in Manjaro ( " https://github.com/linux-surface/linux-surface/issues/1095 ")and Arch Linux (" https://bbs.archlinux.org/viewtopic.php?id=283920 ") so it is not limited to Ubuntu Kernels.

This bug has already been reported for Ubuntu 23.04 Beta in Ubuntu bugtracking system (" https://<email address hidden>/msg501664.html ") with Bug number #2015794.

Attachments:
1. Picture of stuck boot sequence of HP x2 210 G2 with Intel Atom CPU trying to boot in to Kubuntu 23.04 with Kernel 6.2.0-20.

2. dmesg.log of the computer with Ubuntu Kernel 6.1.25.
3. xsession-errors of the computer with Ubuntu Kernel 6.1.25.
4. dmesg.log of the computer with Ubuntu Kernel 5.19.0-40.
5. Video of boot sequence with Kernel 6.2.0-20.
6. uname-a.log of Kernel 6.1.25.
7. lspci-vvnn.log of Kernel 6.1.25.
8. version.log of Kernel 5.19.0-40.
9. dmesg.log with shisp-file with ubuntu kernel 6.2.0-06.**
10. dmesg.log with shisp-file with ubuntu kernel 6.3.0-06**

P.S. The apport-collect data is from Kernel 5.19.0-40.
P.S.P.S I had difficulty determining Tags so they are to be changed by you.

Revision history for this message
Jan Saarinen (h2onvety) wrote :
Jan Saarinen (h2onvety)
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2017444

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Jan Saarinen (h2onvety)
summary: Kernel 6.2.0-20 Bug / Regression caused by atomisp module - Computer
- with Intel Atom CPU will not boot with Kernel 6.2.0-20 in to Kubuntu
- 23.04
+ with Intel Atom CPU will not boot with Kernel 6.2.0-20 in to Ubuntu or
+ Kubuntu 23.04
tags: added: kernel
tags: added: kernel-bug
removed: kernel
Jan Saarinen (h2onvety)
description: updated
Jan Saarinen (h2onvety)
description: updated
Revision history for this message
Jan Saarinen (h2onvety) wrote :
Jan Saarinen (h2onvety)
description: updated
description: updated
Revision history for this message
Jan Saarinen (h2onvety) wrote :
Revision history for this message
Jan Saarinen (h2onvety) wrote :
Revision history for this message
Jan Saarinen (h2onvety) wrote :
tags: added: apport-collected lunar staging
description: updated
Revision history for this message
Jan Saarinen (h2onvety) wrote : AlsaInfo.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : IwConfig.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : Lspci.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : Lspci-vt.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : Lsusb.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : Lsusb-t.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : Lsusb-v.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : ProcEnviron.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : ProcModules.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : RfKill.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : UdevDb.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : WifiSyslog.txt

apport information

Revision history for this message
Jan Saarinen (h2onvety) wrote : acpidump.txt

apport information

description: updated
description: updated
Revision history for this message
Jan Saarinen (h2onvety) wrote : Re: Kernel 6.2.0-20 Bug / Regression caused by atomisp module - Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20 in to Ubuntu or Kubuntu 23.04

Naturally I was not able to execute apport-collect 2017444 in Kernel 6.2.0-20 but I did it with Kernel 5.19.0-40.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Jan Saarinen (h2onvety)
description: updated
description: updated
Jan Saarinen (h2onvety)
description: updated
Jan Saarinen (h2onvety)
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Jan Saarinen (h2onvety) wrote :
Revision history for this message
Jan Saarinen (h2onvety) wrote :
Revision history for this message
Jan Saarinen (h2onvety) wrote :
description: updated
Jan Saarinen (h2onvety)
description: updated
description: updated
description: updated
tags: added: kernel
removed: kernel-bug
Jan Saarinen (h2onvety)
tags: added: kernel-uncat
removed: kernel
tags: added: kernel-core
tags: added: kernel-input
tags: added: bitesize
Jan Saarinen (h2onvety)
tags: added: kernel-bug-exists-upstream
Jan Saarinen (h2onvety)
description: updated
Jan Saarinen (h2onvety)
description: updated
description: updated
Jan Saarinen (h2onvety)
description: updated
Revision history for this message
Jan Saarinen (h2onvety) wrote :
description: updated
Revision history for this message
Jan Saarinen (h2onvety) wrote :
description: updated
Revision history for this message
Jan Saarinen (h2onvety) wrote :

SOLUTION FOR THIS BUG IS FOUND:

Installing file shisp_2401a0_v21.bin from:

https://github.com/intel-aero/meta-intel-aero-base/blob/master/recipes-kernel/linux/linux-yocto/shisp_2401a0_v21.bin

to /lib/firmware will solve the bug.

Revision history for this message
Jan Saarinen (h2onvety) wrote :

Will You please add file shisp_2401a0_v21.bin to kernel in directory /lib/firmware

Jan Saarinen (h2onvety)
summary: - Kernel 6.2.0-20 Bug / Regression caused by atomisp module - Computer
- with Intel Atom CPU will not boot with Kernel 6.2.0-20 in to Ubuntu or
- Kubuntu 23.04
+ Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
description: updated
Jan Saarinen (h2onvety)
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-firmware (Ubuntu):
status: New → Confirmed
Jan Saarinen (h2onvety)
description: updated
description: updated
description: updated
Jan Saarinen (h2onvety)
description: updated
Jan Saarinen (h2onvety)
description: updated
Jan Saarinen (h2onvety)
description: updated
Jan Saarinen (h2onvety)
description: updated
description: updated
description: updated
Jan Saarinen (h2onvety)
description: updated
Jan Saarinen (h2onvety)
description: updated
Juerg Haefliger (juergh)
tags: added: kern-6606
Jan Saarinen (h2onvety)
description: updated
Jan Saarinen (h2onvety)
description: updated
Changed in linux (Ubuntu):
assignee: nobody → Kai-Heng Feng (kaihengfeng)
Jan Saarinen (h2onvety)
description: updated
description: updated
Changed in linux (Ubuntu Lunar):
status: New → Confirmed
Revision history for this message
Juerg Haefliger (juergh) wrote :

atomisp module should be disabled per the upstream driver maintainer. See: https://github.com/linux-surface/linux-surface/issues/1095

Changed in linux-firmware (Ubuntu Lunar):
status: New → Invalid
Changed in linux-firmware (Ubuntu):
status: Confirmed → Invalid
Stefan Bader (smb)
Changed in linux (Ubuntu Lunar):
importance: Undecided → High
Stefan Bader (smb)
Changed in linux (Ubuntu Lunar):
status: Confirmed → Fix Committed
Changed in linux (Ubuntu):
assignee: Kai-Heng Feng (kaihengfeng) → nobody
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-6.2/6.2.0-1003.3~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-nvidia-6.2
Jan Saarinen (h2onvety)
tags: added: verification-done-jammy
removed: verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (72.7 KiB)

This bug was fixed in the package linux - 6.2.0-23.23

---------------
linux (6.2.0-23.23) lunar; urgency=medium

  * lunar/linux: 6.2.0-23.23 -proposed tracker (LP: #2019845)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - debian/dkms-versions -- update from kernel-versions (main/2023.05.15)

  * Fix flicker display problem on some panels which support PSR2 (LP: #2002968)
    - drm/i915/psr: Add continuous full frame bit together with single

  * Kernel 6.1 bumped the disk consumption on default images by 15%
    (LP: #2015867)
    - [Packaging] introduce a separate linux-lib-rust package

  * Update I915 PSR calculation on Linux 6.2 (LP: #2018655)
    - drm/i915: Fix fast wake AUX sync len
    - drm/i915: Explain the magic numbers for AUX SYNC/precharge length

  * Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
    (LP: #2017444)
    - [Config]: Disable CONFIG_INTEL_ATOMISP

  * udev fails to make prctl() syscall with apparmor=0 (as used by maas by
    default) (LP: #2016908)
    - SAUCE: (no-up) Stacking v38: Fix prctl() syscall with apparmor=0

  * CVE-2023-32233
    - netfilter: nf_tables: deactivate anonymous set from preparation phase

  * CVE-2023-2612
    - SAUCE: shiftfs: prevent lock unbalance in shiftfs_create_object()

  * CVE-2023-31436
    - net: sched: sch_qfq: prevent slab-out-of-bounds in qfq_activate_agg

  * CVE-2023-1380
    - wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies()

  * 5.19 not reporting cgroups v1 blkio.throttle.io_serviced (LP: #2016186)
    - SAUCE: blk-throttle: Fix io statistics for cgroup v1

  * LSM stacking and AppArmor for 6.2: additional fixes (LP: #2017903)
    - SAUCE: (no-up) apparmor: fix policy_compat perms remap for file dfa
    - SAUCE: (no-up) apparmor: fix profile verification and enable it
    - SAUCE: (no-up) apparmor: fix: add missing failure check in
      compute_xmatch_perms
    - SAUCE: (no-up) apparmor: fix: kzalloc perms tables for shared dfas

  * Lunar update: v6.2.12 upstream stable release (LP: #2017219)
    - Revert "pinctrl: amd: Disable and mask interrupts on resume"
    - drm/amd/display: Pass the right info to drm_dp_remove_payload
    - drm/i915: Workaround ICL CSC_MODE sticky arming
    - ALSA: emu10k1: fix capture interrupt handler unlinking
    - ALSA: hda/sigmatel: add pin overrides for Intel DP45SG motherboard
    - ALSA: i2c/cs8427: fix iec958 mixer control deactivation
    - ALSA: hda: patch_realtek: add quirk for Asus N7601ZM
    - ALSA: hda/realtek: Add quirks for Lenovo Z13/Z16 Gen2
    - ALSA: firewire-tascam: add missing unwind goto in
      snd_tscm_stream_start_duplex()
    - ALSA: emu10k1: don't create old pass-through playback device on Audigy
    - ALSA: hda/sigmatel: fix S/PDIF out on Intel D*45* motherboards
    - ALSA: hda/hdmi: disable KAE for Intel DG2
    - Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp}
    - Bluetooth: Fix race condition in hidp_session_thread
    - bluetooth: btbcm: Fix logic error in forming the board name.
    - Bluetooth: Free potentially unfreed SCO connection
    - Bluetooth: hci_conn: Fix possible UAF
    - btrfs: restore the thread_pool=...

Changed in linux (Ubuntu Lunar):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/6.2.0-1009.9 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-lunar-linux-azure verification-needed-lunar
Jan Saarinen (h2onvety)
tags: added: verification-done-lunar
removed: verification-needed-lunar
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.5.0-5.5

---------------
linux (6.5.0-5.5) mantic; urgency=medium

  * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23)

 -- Andrea Righi <email address hidden> Wed, 06 Sep 2023 15:51:04 +0200

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-6.5/6.5.0-1007.7~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-done-jammy-linux-azure-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-failed-jammy-linux-azure-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-azure-6.5-v2 verification-needed-jammy-linux-azure-6.5
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-6.5/6.5.0-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws-6.5-v2 verification-needed-jammy-linux-aws-6.5
Revision history for this message
Jan Saarinen (h2onvety) wrote :

inxi of an Intel Atom CPU computer running with Kernel 6.5.0-10-generic

tags: added: verification-done-jammy-linux-aws-6.5 verification-done-jammy-linux-azure-6.5
removed: verification-needed-jammy-linux-aws-6.5 verification-needed-jammy-linux-azure-6.5
Revision history for this message
Jan Saarinen (h2onvety) wrote :

So this fix solves the problem.

The Web-camera also works now.

Thank You everyone.

Revision history for this message
Imre Péntek (pentek-imre) wrote :

hello, I have this in my dmesg:

[ 24.197415] atomisp_gmin_platform: module is from the staging directory, the quality is unknown, you have been warned.
[ 24.197536] atomisp_gmin_platform: module verification failed: signature and/or required key missing - tainting kernel
[ 24.484974] proc_thermal 0000:00:0b.0: enabling device (0000 -> 0002)
[ 24.562387] atomisp: module is from the staging directory, the quality is unknown, you have been warned.

[ 24.572467] **********************************************************
[ 24.572470] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
[ 24.572472] ** **
[ 24.572474] ** trace_printk() being used. Allocating extra memory. **
[ 24.572476] ** **
[ 24.572478] ** This means that this is a DEBUG kernel and it is **
[ 24.572479] ** unsafe for production use. **
[ 24.572481] ** **
[ 24.572483] ** If you see this message and you are not debugging **
[ 24.572485] ** the kernel, report this immediately to your vendor! **
[ 24.572487] ** **
[ 24.572488] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
[ 24.572490] **********************************************************
[ 24.580827] atomisp-isp2 0000:00:03.0: Support for Cherrytrail (ISP2401) was disabled at compile time

is this related?
Ubuntu 22.04.3 LTS
headless installation (only ssh (and physical) access)
there are no pending updates

Revision history for this message
Jan Saarinen (h2onvety) wrote : Re: [Bug 2017444] Re: Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20

Good New Year's Eve (it's 6 minutes to midnight in Finland) - and Happy
New Year 2024,

the reason I wrote the Bug Report was that it was impossible to install
Ubuntu 23 at all. At that time Ubuntu 22.04 was still using Kernel 5.xx
and problems - if any - were not as severe as in Ubuntu 23.04 and 23.10.

To my understanding atomisp-modules were disabled then.

A quick search with Cherrytrail (ISP2401) gave this news article (
https://www.phoronix.com/news/Linux-6.7-Media ) - have You read it already?

It seems that improvements to atomisp have been made during the autumn
of 2023 and atomisp-modules have been enabled again in kernel.

I do not have more knowledge, but one of the Red Hat engineers referred
in the Proronix article is Hans de Goede. He is both developing
atomisp-modules and also the one in charge of atomisp-modules in
Kernel.org. So by searching what he has published about the subject this
autumn may give you more info. And if you feel it is important enough -
you may ask him personally.

Yours,

Sami Saarinen

P.S. I have a week old fresh install of Kubuntu 22.04 LTS in a
HP-x2-210-G2 with Intel Atom CPU and dmegs's gives no warnings about
atomisp.

On 30.12.2023 16.03, Imre Péntek wrote:
> hello, I have this in my dmesg:
>
> [ 24.197415] atomisp_gmin_platform: module is from the staging directory, the quality is unknown, you have been warned.
> [ 24.197536] atomisp_gmin_platform: module verification failed: signature and/or required key missing - tainting kernel
> [ 24.484974] proc_thermal 0000:00:0b.0: enabling device (0000 -> 0002)
> [ 24.562387] atomisp: module is from the staging directory, the quality is unknown, you have been warned.
>
> [ 24.572467] **********************************************************
> [ 24.572470] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
> [ 24.572472] ** **
> [ 24.572474] ** trace_printk() being used. Allocating extra memory. **
> [ 24.572476] ** **
> [ 24.572478] ** This means that this is a DEBUG kernel and it is **
> [ 24.572479] ** unsafe for production use. **
> [ 24.572481] ** **
> [ 24.572483] ** If you see this message and you are not debugging **
> [ 24.572485] ** the kernel, report this immediately to your vendor! **
> [ 24.572487] ** **
> [ 24.572488] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
> [ 24.572490] **********************************************************
> [ 24.580827] atomisp-isp2 0000:00:03.0: Support for Cherrytrail (ISP2401) was disabled at compile time
>
> is this related?
> Ubuntu 22.04.3 LTS
> headless installation (only ssh (and physical) access)
> there are no pending updates
>

Revision history for this message
Juerg Haefliger (juergh) wrote :

You shouldn't be commenting on closed bugs, your comments might go unnoticed. Please open a new bug to report issues and/or requests.

To post a comment you must log in.