Ubuntu
linux package

Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

Bug #2038582 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-aws (Ubuntu)
Fix Released
Undecided
Unassigned
linux-azure (Ubuntu)
Fix Released
Undecided
Unassigned
linux-gcp (Ubuntu)
Fix Released
Undecided
Unassigned
linux-ibm (Ubuntu)
Fix Released
Undecided
Unassigned
linux-oracle (Ubuntu)
Fix Released
Undecided
Unassigned
linux-raspi (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

This will prevent existing armhf binaries to operate correctly, if they are still using 32bit time.

24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used.

I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision.

This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support.

config COMPAT_32BIT_TIME
 bool "Provide system calls for 32-bit time_t"
 default !64BIT || COMPAT
 help
   This enables 32 bit time_t support in addition to 64 bit time_t support.
   This is relevant on all 32-bit architectures, and 64-bit architectures
   as part of compat syscall handling.

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 2038582

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
Manuel Diewald (diewald)
tags: added: kern-8207
Dimitri John Ledkov (xnox)
summary: - Turning COMPAT_32BIT_TIME off on arm64
+ Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

https://lists.ubuntu.com/archives/kernel-team/2023-November/147186.html

Changed in linux (Ubuntu):
status: Incomplete → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (49.1 KiB)

This bug was fixed in the package linux-ibm - 6.8.0-1001.1

---------------
linux-ibm (6.8.0-1001.1) noble; urgency=medium

  * noble/linux-ibm: 6.8.0-1001.1 -proposed tracker (LP: #2052778)

  * Packaging resync (LP: #1786013)
    - debian.ibm/dkms-versions -- update from kernel-versions (main/d2024.02.07)

  * Miscellaneous Ubuntu changes
    - [packaging] update rust, clang and bindgen build-deps
    - [Config] updateconfigs following 6.8.0-7.7 rebase

  [ Ubuntu: 6.8.0-7.7 ]

  * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691)
  * update apparmor and LSM stacking patch set (LP: #2028253)
    - SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
      ima_filter_rule from security_audit_rule
    - SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
      management of the sock security
    - SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
      structure.
    - SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label collisions
      with stacked LSMs
    - SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in
      security_audit_rule_match
    - SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx
      hook
    - SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob
      in audit_context
    - SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in
      security_ipc_getsecid
    - SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM
      data
    - SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in
      security_current_getsecid
    - SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in
      security_inode_getsecid
    - SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in
      audit_names
    - SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new
      security_cred_getlsmblob LSM hook
    - SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data
      from secid to lsmblob
    - SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for
      audit data
    - SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct LSM
      context releaser
    - SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_secid_to_secctx
    - SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_lsmblob_to_secctx
    - SAUCE: apparmor4.0.0 [19/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_inode_getsecctx
    - SAUCE: apparmor4.0.0 [20/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_dentry_init_security
    - SAUCE: apparmor4.0.0 [21/87]: LSM stacking v39: LSM:
      security_lsmblob_to_secctx module selection
    - SAUCE: apparmor4.0.0 [22/87]: LSM stacking v39: Audit: Create audit_stamp
      structure
    - SAUCE: apparmor4.0.0 [23/87]: LSM stacking v39: Audit: Allow multiple
      records in an audit_buffer
    - SAUCE: apparmor4.0.0 [24/87]: LSM stacking v39: Audit: Add record for
      multiple task security contexts
    - SAUCE: apparmor4.0.0 [25/87]: LSM stacking v39: audit: mu...

Changed in linux-ibm (Ubuntu):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (49.2 KiB)

This bug was fixed in the package linux-oracle - 6.8.0-1001.1

---------------
linux-oracle (6.8.0-1001.1) noble; urgency=medium

  * noble/linux-oracle: 6.8.0-1001.1 -proposed tracker (LP: #2052776)

  * Packaging resync (LP: #1786013)
    - debian.oracle/dkms-versions -- update from kernel-versions
      (main/d2024.02.07)

  * [arm64] Increase max CPU count to 512 (LP: #2046184)
    - [Config]: oracle: Increase max CPU count to 512

  * Miscellaneous Ubuntu changes
    - [Config] updateconfigs following 6.8.0-7.7 rebase

  [ Ubuntu: 6.8.0-7.7 ]

  * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691)
  * update apparmor and LSM stacking patch set (LP: #2028253)
    - SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
      ima_filter_rule from security_audit_rule
    - SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
      management of the sock security
    - SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
      structure.
    - SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label collisions
      with stacked LSMs
    - SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in
      security_audit_rule_match
    - SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx
      hook
    - SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob
      in audit_context
    - SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in
      security_ipc_getsecid
    - SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM
      data
    - SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in
      security_current_getsecid
    - SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in
      security_inode_getsecid
    - SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in
      audit_names
    - SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new
      security_cred_getlsmblob LSM hook
    - SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data
      from secid to lsmblob
    - SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for
      audit data
    - SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct LSM
      context releaser
    - SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_secid_to_secctx
    - SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_lsmblob_to_secctx
    - SAUCE: apparmor4.0.0 [19/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_inode_getsecctx
    - SAUCE: apparmor4.0.0 [20/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_dentry_init_security
    - SAUCE: apparmor4.0.0 [21/87]: LSM stacking v39: LSM:
      security_lsmblob_to_secctx module selection
    - SAUCE: apparmor4.0.0 [22/87]: LSM stacking v39: Audit: Create audit_stamp
      structure
    - SAUCE: apparmor4.0.0 [23/87]: LSM stacking v39: Audit: Allow multiple
      records in an audit_buffer
    - SAUCE: apparmor4.0.0 [24/87]: LSM stacking v39: Audit: Add record for
      multiple task security co...

Changed in linux-oracle (Ubuntu):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.8.0-11.11

---------------
linux (6.8.0-11.11) noble; urgency=medium

  * noble/linux: 6.8.0-11.11 -proposed tracker (LP: #2053094)

  * Miscellaneous Ubuntu changes
    - [Packaging] riscv64: disable building unnecessary binary debs

 -- Paolo Pisati <email address hidden> Wed, 14 Feb 2024 00:04:31 +0100

Changed in linux (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-gcp - 6.8.0-1002.2

---------------
linux-gcp (6.8.0-1002.2) noble; urgency=medium

  * noble/linux-gcp: 6.8.0-1002.2 -proposed tracker (LP: #2053032)

  * Miscellaneous Ubuntu changes
    - [packaging] update rust, clang and bindgen build-deps
    - [Packaging] add Rust build deps for riscv64

 -- Paolo Pisati <email address hidden> Tue, 13 Feb 2024 16:15:29 +0100

Changed in linux-gcp (Ubuntu):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (49.3 KiB)

This bug was fixed in the package linux-aws - 6.8.0-1001.1

---------------
linux-aws (6.8.0-1001.1) noble; urgency=medium

  * noble/linux-aws: 6.8.0-1001.1 -proposed tracker (LP: #2052774)

  * Packaging resync (LP: #1786013)
    - debian.aws/dkms-versions -- update from kernel-versions (main/d2024.02.07)

  * AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64 (LP: #2045428)
    - Revert "UBUNTU: SAUCE: net: ena: fix too long default tx interrupt
      moderation interval"

  * Miscellaneous Ubuntu changes
    - [Packaging] remove custom ABI/retpoline check files
    - [Config] update annotations after rebase to v6.8

  [ Ubuntu: 6.8.0-7.7 ]

  * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691)
  * update apparmor and LSM stacking patch set (LP: #2028253)
    - SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
      ima_filter_rule from security_audit_rule
    - SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
      management of the sock security
    - SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
      structure.
    - SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label collisions
      with stacked LSMs
    - SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in
      security_audit_rule_match
    - SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx
      hook
    - SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob
      in audit_context
    - SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in
      security_ipc_getsecid
    - SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM
      data
    - SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in
      security_current_getsecid
    - SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in
      security_inode_getsecid
    - SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in
      audit_names
    - SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new
      security_cred_getlsmblob LSM hook
    - SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data
      from secid to lsmblob
    - SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for
      audit data
    - SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct LSM
      context releaser
    - SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_secid_to_secctx
    - SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_lsmblob_to_secctx
    - SAUCE: apparmor4.0.0 [19/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_inode_getsecctx
    - SAUCE: apparmor4.0.0 [20/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_dentry_init_security
    - SAUCE: apparmor4.0.0 [21/87]: LSM stacking v39: LSM:
      security_lsmblob_to_secctx module selection
    - SAUCE: apparmor4.0.0 [22/87]: LSM stacking v39: Audit: Create audit_stamp
      structure
    - SAUCE: apparmor4.0.0 [23/87]: LSM stacking v39: Audit: Allow multiple
      records in an audit_buffer
    - SAUC...

Changed in linux-aws (Ubuntu):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (49.8 KiB)

This bug was fixed in the package linux-azure - 6.8.0-1001.1

---------------
linux-azure (6.8.0-1001.1) noble; urgency=medium

  * noble/linux-azure: 6.8.0-1001.1 -proposed tracker (LP: #2052777)

  * Packaging resync (LP: #1786013)
    - debian.azure/dkms-versions -- update from kernel-versions (main/d2024.02.07)

  * Azure: cifs modules missing from the linux-modules package (LP: #2052980)
    - [Config] Move cifs.ko to linux-modules package

  * Azure: Enable CONFIG_TEST_LOCKUP (LP: #2052723)
    - [Config] CONFIG_TEST_LOCKUP=m

  * Miscellaneous Ubuntu changes
    - [Packaging] azure: update Rust toolchain
    - [Packaging] azure: move to kernel v6.8
    - [Config] azure: update annotations after moving to v6.8

  [ Ubuntu: 6.8.0-9.9 ]

  * noble/linux: 6.8.0-9.9 -proposed tracker (LP: #2052945)
  * Miscellaneous upstream changes
    - Revert "UBUNTU: [Packaging] temporarily disable Rust dependencies on
      riscv64"

  [ Ubuntu: 6.8.0-8.8 ]

  * noble/linux: 6.8.0-8.8 -proposed tracker (LP: #2052918)
  * Miscellaneous Ubuntu changes
    - [Packaging] riscv64: enable linux-libc-dev build
    - v6.8-rc4 rebase
  * Rebase on v6.8-rc4

  [ Ubuntu: 6.8.0-7.7 ]

  * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691)
  * update apparmor and LSM stacking patch set (LP: #2028253)
    - SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
      ima_filter_rule from security_audit_rule
    - SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
      management of the sock security
    - SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
      structure.
    - SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label collisions
      with stacked LSMs
    - SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in
      security_audit_rule_match
    - SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx
      hook
    - SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob
      in audit_context
    - SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in
      security_ipc_getsecid
    - SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM
      data
    - SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in
      security_current_getsecid
    - SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in
      security_inode_getsecid
    - SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in
      audit_names
    - SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new
      security_cred_getlsmblob LSM hook
    - SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data
      from secid to lsmblob
    - SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for
      audit data
    - SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct LSM
      context releaser
    - SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_secid_to_secctx
    - SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_lsmblob_to_secctx
    - SAUCE: ap...

Changed in linux-azure (Ubuntu):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (17.1 KiB)

This bug was fixed in the package linux-raspi - 6.8.0-1002.2

---------------
linux-raspi (6.8.0-1002.2) noble; urgency=medium

  * noble/linux-raspi: 6.8.0-1002.2 -proposed tracker (LP: #2057941)

  * Wifi wlan0 device not present on Raspberry Pi 3A+ (LP: #2056635)
    - [Config] raspi: Set MMC_BCM2835_SDHOST=y

  * Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives) (LP: #2038582)
    - [Config] raspi: Set COMPAT_32BIT_TIME=n

  * Miscellaneous Ubuntu changes
    - [Config] raspi: updateconfigs after update to raspberrypi rpi-6.8.y
      (2024-03-14)

  * Miscellaneous upstream changes
    - dtoverlays: Correct width/height on Waveshare 2.8" panel
    - dtoverlays: rotate override needs to update "rotation" for drm mode
    - configs: Disable process/register dumps via SysRq
    - ASOc: Add HiFiBerry DAC8X to the simple card driver
    - Overlays: Add definitions for HiFiBerry 8 channel DAC8X
    - drm: Add DRM_MODE_TV_MODE_MONOCHROME
    - drm/vc4: Add monochrome mode to the VEC.
    - media: i2c: imx296: Updated register setting to fix Fast Trigger
    - dt-bindings: add additional RP1 PLL output channels
    - drivers: clk: rp1: add GPCLK source muxes and additional PLL dividers
    - DT: rp1: add general-purpose clock source definitions
    - drivers: clk: rp1: constrain clock divider outputs to design maximums
    - vc4: Add jack detection to HDMI audio driver
    - fixup! ASoC: dwc: Defer bclk_ratio handling to hw_params
    - ASoC: bcm: Use the correct sample width value
    - clk: rp1: Reserve pll_audio* for clk_i2s
    - clk: rp1: Allow clk_i2s to change the audio PLLs
    - regulator: Add a regulator for the new LCD panels
    - dt-bindings: ili9881c: add compatible string for new panels
    - drm/panel: ilitek-ili9881c: Allow configuration of the number of lanes
    - drm/panel: ili9881: Add configuration for the new panels
    - defconfigs: Add panel regulator to all the Pi defconfigs
    - dtoverlays: Add overlays for 5" and 7" ILI9881 panels
    - ARM: dts: bcm2712-rpi: Add i2c<n>_pins labels
    - ASoC: dwc: Correct channel count reporting
    - Driver:add waveshare 4inch dsi lcd (C) driver
    - Dtoverlay:add waveshare 4inch dsi lcd (C) dtoverlay
    - Dtoverlay:fix waveshare 11.9inch touch orientation error
    - Dtoverlay:Add waveshare 4inch dsi lcd (C) parameters to the README

  [ Ubuntu: 6.8.0-20.20 ]

  * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
  * Noble update: v6.8.1 upstream stable release (LP: #2058224)
    - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set
    - Documentation/hw-vuln: Add documentation for RFDS
    - x86/rfds: Mitigate Register File Data Sampling (RFDS)
    - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests
    - Linux 6.8.1
  * Autopkgtest failures on amd64 (LP: #2048768)
    - [Packaging] update to clang-18
  * Miscellaneous Ubuntu changes
    - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with
      CONFIG_SECURITY=n
    - [Config] amd64: MITIGATION_RFDS=y

  [ Ubuntu: 6.8.0-19.19 ]

  * noble/linux: 6.8.0-19.19 -proposed tracker (LP: #2057910)
  * Miscellaneous Ubuntu changes
    - [Packaging] re-introduce linux-doc as an empty package
...

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

This bug is awaiting verification that the linux-nvidia-6.8/6.8.0-1006.6~22.04.2 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-nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'.

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.8-v2 verification-needed-jammy-linux-nvidia-6.8
Revision history for this message
Simon Déziel (sdeziel) wrote :

Disabling support for 32bit time caught some by surprise: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2062176

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.