[РЕШЕНО] Ошибка № ...

пятница

[Bug 2092703] Re: Ubuntu 22.04 fails to start after kernel update to 6.8.0-50

The same bug affects me. I use a Lenovo ThinkPad T14 Gen 2 AMD laptop,
with Ryzen 5 PRO 5650U processor.

Ubuntu 22.04 fails to boot after the update (by the Software Updater application) on Friday 2024-12-20 to kernel Linux 6.8.0-50-generic on my laptop.
A black screen with blinking cursor appears after booting. Ctrl-Alt-Delete changes this to a Lenovo and Ubuntu logo, and triggers a restart. The same happens during each new boot to the now default kernel.
Selecting the old Linux 6.8.0-49-generic kernel during boot results in a successful boot and fully functional system, but any attempt with 6.8.0-50-generic fails.

When booting with with 6.8.0-50-generic, the following error message
appears in the log files: " org.gnome.Shell.desktop[1547]: Failed to
setup: No GPUs found ".

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2092703

Title:
Ubuntu 22.04 fails to start after kernel update to 6.8.0-50

Status in linux package in Ubuntu:
Confirmed

Bug description:
Hello, I've recently (2024-12-24) updated the kernel in my Ubuntu
22.04 from 6.8.0-49 to 6.8.0-50, but it doesn't work. I can still
successfully boot 6.8.0-49 kernel. I'm using Lenovo Thinkpad L15 Gen 2
with AMD Ryzen 5850U.

As far as I noticed in boot logs from previous boot (journalctl -b
-1), there is some problem with X.org:

gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) FBDEV: driver for framebuffer: fbdev
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) VESA: driver for VESA chipsets: vesa
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or directory
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for modesetting
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or directory
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org Foundation"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module version = 0.0.2
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, version 25.2
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Unable to find a valid framebuffer device
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for fbdev
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org Foundation"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module version = 0.0.2
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, version 25.2
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/fb0: No such file or directory
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: vesa: Ignoring device with a bound kernel driver
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "modesetting"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "fbdev"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "vesa"
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Device(s) detected, but none match those in the config file.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE)
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: Fatal server error:
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) no screens found(EE)
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE)
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: Please consult the The X.Org Foundation support
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: at http://wiki.x.org
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: for help.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE)
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Server terminated with error (1). Closing log file.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1664]: Unable to run X server
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm-launch-environment][1657]: pam_unix(gdm-launch-environment:session): session closed for user gdm
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: GdmDisplay: Session never registered, failing
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm-launch-environment][1657]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a kernel: logitech-hidpp-device 0003:046D:4082.0004: HID++ 4.5 device connected.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a systemd[1]: session-c6.scope: Deactivated successfully.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: Child process -1664 was already dead.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: GdmDisplay: Session never registered, failing
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a systemd-logind[1049]: Session c6 logged out. Waiting for processes to exit.
gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a systemd-logind[1049]: Removed session c6.

When booting 6.8.0-49 (the one that works fine), I see it uses /dev/dri/card1 instead (extract from logs attached as kernel-6.8.0-49-journalctl-boot-logs-ok.txt).

I'm also attaching:

- cat /proc/version_signature > version.log (from the working kernel 6.8.0-49)
- sudo lspci -vnvn > lspci-vnvn.log (from the working kernel 6.8.0-49)
- apt-updated-packages.txt - a list of updated packages
- kernel-6.8.0-50-journalctl-boot-logs-issue.txt - extract from logs from journalctl -b -1 (boot attempt using problematic kernel 6.8.0-50)
- kernel-6.8.0-49-journalctl-boot-logs-ok.txt - extract from logs from journalctl -b -0 (booting working kernel 6.8.0-49)

How can I make kernel 6.8.0-50 work?

BR,
Adrian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092703/+subscriptions

[Bug 2091990] Re: ovs/linuxbridge jobs running on ubuntu jammy broken with latest kernel 5.15.0-127.137

[Bug 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part

[Bug 2064176] Re: LXD fan bridge causes blocked tasks

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 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-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.

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-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2064176

Title:
LXD fan bridge causes blocked tasks

Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released

Bug description:
SRU Justification:

[Impact]

User can trigger a host crash on Jammy/Noble by launching
a container which uses Ubuntu FAN network in LXD.

[Fix]

A first proposed patch fixes RCU locking by releasing rcu_read_lock
on the skb discard codepath.

Second patch just use a proper way (dev_core_stats_tx_dropped_inc() function)
to increase netdev's tx_dropped statistic value.

[Test Plan]

As provided by Max Asnaashari:

# Install LXD from channel latest/stable
snap install lxd --channel latest/stable

# Configure LXD
lxd init --auto

# Create a FAN network
lxc network create lxdfan0 bridge.mode=fan ipv4.nat=true

# Launch a container using the FAN network
lxc launch ubuntu-minimal:22.04 c1 --network lxdfan0

# Try to interact with LXD
lxc ls

[Where problems could occur]

Change is local and only related to Ubuntu FAN code. I would not expect
any problems with this patchset.

Hi, cross posting this from
https://github.com/canonical/lxd/issues/12161

I've got a lxd cluster running across 3 VMs using the fan bridge. I'm
using a dev revision of LXD based on 6413a948. Creating a container
causes the trace in the attached syslog snippet; this causes the
container creation process to hang indefinitely. ssh logins, `lxc
shell cluster1`, and `ps -aux` also hang.

Apr 29 17:15:01 cluster1 kernel: [ 161.250951] ------------[ cut here ]------------
Apr 29 17:15:01 cluster1 kernel: [ 161.250957] Voluntary context switch within RCU read-side critical section!
Apr 29 17:15:01 cluster1 kernel: [ 161.250990] WARNING: CPU: 2 PID: 510 at kernel/rcu/tree_plugin.h:320 rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251003] Modules linked in: nft_masq nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vxlan ip6_udp_tunnel udp_tunnel dummy br
idge stp llc zfs(PO) spl(O) nf_tables libcrc32c nfnetlink vhost_vsock vhost vhost_iotlb binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common kvm_intel kvm irqbypass crct10dif
_pclmul crc32_pclmul virtio_gpu polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 virtio_dma_buf aesni_intel vmw_vsock_virtio_transport 9pnet_virtio xhci_
pci drm_shmem_helper i2c_i801 ahci 9pnet vmw_vsock_virtio_transport_common xhci_pci_renesas drm_kms_helper libahci crypto_simd joydev virtio_input cryptd lpc_ich virtiofs i2c_smbus
vsock psmouse input_leds mac_hid serio_raw rapl qemu_fw_cfg vmgenid nfsd dm_multipath auth_rpcgss scsi_dh_rdac nfs_acl lockd scsi_dh_emc scsi_dh_alua grace sch_fq_codel drm sunrpc
efi_pstore virtio_rng ip_tables x_tables autofs4
Apr 29 17:15:01 cluster1 kernel: [ 161.251085] CPU: 2 PID: 510 Comm: nmbd Tainted: P O 6.5.0-28-generic #29~22.04.1-Ubuntu
Apr 29 17:15:01 cluster1 kernel: [ 161.251089] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS unknown 2/2/2022
Apr 29 17:15:01 cluster1 kernel: [ 161.251091] RIP: 0010:rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251095] Code: 08 f0 83 44 24 fc 00 48 89 de 4c 89 f7 e8 d1 af ff ff e9 1e fe ff ff 48 c7 c7 d0 60 56 88 c6 05 e6 27 40 02 01 e8 79 b2 f2 ff
<0f> 0b e9 bd fd ff ff a9 ff ff ff 7f 0f 84 75 fe ff ff 65 48 8b 3c
Apr 29 17:15:01 cluster1 kernel: [ 161.251098] RSP: 0018:ffffb9cbc11dbbc8 EFLAGS: 00010046
Apr 29 17:15:01 cluster1 kernel: [ 161.251101] RAX: 0000000000000000 RBX: ffff941ef7cb3f80 RCX: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251103] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251104] RBP: ffffb9cbc11dbbe8 R08: 0000000000000000 R09: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251106] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251111] R13: ffff941d893e9980 R14: 0000000000000000 R15: ffff941d80ad7a80
Apr 29 17:15:01 cluster1 kernel: [ 161.251113] FS: 00007c7dcbdb8a00(0000) GS:ffff941ef7c80000(0000) knlGS:0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251115] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 29 17:15:01 cluster1 kernel: [ 161.251117] CR2: 00005a30877ae488 CR3: 0000000105888003 CR4: 0000000000170ee0
Apr 29 17:15:01 cluster1 kernel: [ 161.251122] Call Trace:
Apr 29 17:15:01 cluster1 kernel: [ 161.251128] <TASK>
Apr 29 17:15:01 cluster1 kernel: [ 161.251133] ? show_regs+0x6d/0x80
Apr 29 17:15:01 cluster1 kernel: [ 161.251145] ? __warn+0x89/0x160
Apr 29 17:15:01 cluster1 kernel: [ 161.251152] ? rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251155] ? report_bug+0x17e/0x1b0
Apr 29 17:15:01 cluster1 kernel: [ 161.251172] ? handle_bug+0x46/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251187] ? exc_invalid_op+0x18/0x80
Apr 29 17:15:01 cluster1 kernel: [ 161.251190] ? asm_exc_invalid_op+0x1b/0x20
Apr 29 17:15:01 cluster1 kernel: [ 161.251202] ? rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251205] ? rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251208] __schedule+0xcc/0x750
Apr 29 17:15:01 cluster1 kernel: [ 161.251218] schedule+0x63/0x110
Apr 29 17:15:01 cluster1 kernel: [ 161.251222] schedule_hrtimeout_range_clock+0xbc/0x130
Apr 29 17:15:01 cluster1 kernel: [ 161.251238] ? __pfx_hrtimer_wakeup+0x10/0x10
Apr 29 17:15:01 cluster1 kernel: [ 161.251245] schedule_hrtimeout_range+0x13/0x30
Apr 29 17:15:01 cluster1 kernel: [ 161.251248] ep_poll+0x33f/0x390
Apr 29 17:15:01 cluster1 kernel: [ 161.251254] ? __pfx_ep_autoremove_wake_function+0x10/0x10
Apr 29 17:15:01 cluster1 kernel: [ 161.251257] do_epoll_wait+0xdb/0x100
Apr 29 17:15:01 cluster1 kernel: [ 161.251259] __x64_sys_epoll_wait+0x6f/0x110
Apr 29 17:15:01 cluster1 kernel: [ 161.251265] do_syscall_64+0x5b/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251270] ? do_epoll_ctl+0x3cb/0x860
Apr 29 17:15:01 cluster1 kernel: [ 161.251273] ? __task_pid_nr_ns+0x6c/0xc0
Apr 29 17:15:01 cluster1 kernel: [ 161.251279] ? exit_to_user_mode_prepare+0x30/0xb0
Apr 29 17:15:01 cluster1 kernel: [ 161.251284] ? syscall_exit_to_user_mode+0x37/0x60
Apr 29 17:15:01 cluster1 kernel: [ 161.251286] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251288] ? syscall_exit_to_user_mode+0x37/0x60
Apr 29 17:15:01 cluster1 kernel: [ 161.251300] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251304] ? syscall_exit_to_user_mode+0x37/0x60
Apr 29 17:15:01 cluster1 kernel: [ 161.251306] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251309] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251313] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Apr 29 17:15:01 cluster1 kernel: [ 161.251316] RIP: 0033:0x7c7dcf325dea
Apr 29 17:15:01 cluster1 kernel: [ 161.251333] Code: 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 e8 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 5e c3 0f 1f 44 00 00 48 83 ec 28 89 54 24 18
Apr 29 17:15:01 cluster1 kernel: [ 161.251335] RSP: 002b:00007ffdde5e0278 EFLAGS: 00000246 ORIG_RAX: 00000000000000e8
Apr 29 17:15:01 cluster1 kernel: [ 161.251338] RAX: ffffffffffffffda RBX: 00005a30877a2ea0 RCX: 00007c7dcf325dea
Apr 29 17:15:01 cluster1 kernel: [ 161.251340] RDX: 0000000000000001 RSI: 00007ffdde5e02ac RDI: 0000000000000005
Apr 29 17:15:01 cluster1 kernel: [ 161.251341] RBP: 00005a3087794590 R08: 00000000000f423f R09: 00007ffdde5e0357
Apr 29 17:15:01 cluster1 kernel: [ 161.251343] R10: 00000000000003e8 R11: 0000000000000246 R12: 00005a30877a2f30
Apr 29 17:15:01 cluster1 kernel: [ 161.251345] R13: 00000000000003e8 R14: 0000000000000090 R15: 000000000000000a
Apr 29 17:15:01 cluster1 kernel: [ 161.251348] </TASK>
Apr 29 17:15:01 cluster1 kernel: [ 161.251349] ---[ end trace 0000000000000000 ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064176/+subscriptions

[Bug 2069961] Re: turbostat fails with too many open files on large systems

[Bug 2074380] Re: [UBUNTU 22.04] s390/cpum_cf: make crypto counters upward compatible

[Bug 2077321] Re: Please backport the more restrictive XSAVES deactivation for Zen1/2 arch

[Bug 2080378] Re: IOMMU warnings on AMD systems after booting into kdump kernel

[Bug 2085082] Re: Cannot detect audio sinks and sources in proposed kernel

[Bug 2077260] Re: freeze after updating to newest kernel on log in sreen or just after log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

Hi.
Anyone of the affected users got rid of this issue? If so, how?
I still facing the issue...

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077260

Title:
freeze after updating to newest kernel on log in sreen or just after
log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

Status in linux package in Ubuntu:
Confirmed

Bug description:
freeze after updating to newest kernel on log in sreen or just after
log in (6.8.0-45 ?). Had to use Grub to rester to 6.5.0-45

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-45-generic 6.5.0-45.45~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 18 15:53:56 2024
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: michal 2670 F.... wireplumber
/dev/snd/seq: michal 2665 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
MachineType: Hewlett-Packard HP G62 Notebook PC
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic root=UUID=62689215-60a8-4e0a-8e4e-fb3115fd7b88 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
RelatedPackageVersions:
linux-restricted-modules-6.5.0-45-generic N/A
linux-backports-modules-6.5.0-45-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.2
Tags: noble wayland-session
Uname: Linux 6.5.0-45-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/29/2010
dmi.bios.release: 15.37
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.37
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1439
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 60.3F
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 60.63
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.37:bd10/29/2010:br15.37:efr60.63:svnHewlett-Packard:pnHPG62NotebookPC:pvr0594110000252710001020100:rvnHewlett-Packard:rn1439:rvr60.3F:cvnHewlett-Packard:ct10:cvrChassisVersion:skuLD667EA#AKD:
dmi.product.family: 103C_5335KV
dmi.product.name: HP G62 Notebook PC
dmi.product.sku: LD667EA#AKD
dmi.product.version: 0594110000252710001020100
dmi.sys.vendor: Hewlett-Packard
mtime.conffile..etc.init.d.apport: 2024-07-22T14:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077260/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules/5.15.0-132.143)

All autopkgtests for the newly accepted linux-restricted-modules (5.15.0-132.143) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-525/unknown (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013

Title:
Packaging resync

Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix

Bug description:
Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 2095199] [NEW] Focal update: v5.4.288 upstream stable release

Public bug reported:

SRU Justification

Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:

v5.4.288 upstream stable release
from git://git.kernel.org/

usb: host: max3421-hcd: Correctly abort a USB request.
ata: sata_highbank: fix OF node reference leak in highbank_initialize_phys()
usb: dwc2: hcd: Fix GetPortStatus & SetPortFeature
usb: ehci-hcd: fix call balance of clocks handling routines
usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer
xfs: don't drop errno values when we fail to ficlone the entire range
bpf, sockmap: Fix update element with same
batman-adv: Do not send uninitialized TT changes
batman-adv: Remove uninitialized data in full table TT response
batman-adv: Do not let TT changes list grows indefinitely
tipc: fix NULL deref in cleanup_bearer()
net: lapb: increase LAPB_HEADER_LEN
ACPI: resource: Fix memory resource type union access
qca_spi: Fix clock speed for multiple QCA7000
qca_spi: Make driver probing reliable
net/sched: netem: account for backlog updates from child qdisc
ACPICA: events/evxfregn: don't release the ContextMutex that was never acquired
blk-iocost: clamp inuse and skip noops in __propagate_weights()
blk-iocost: fix weight updates of inner active iocgs
blk-iocost: Avoid using clamp() on inuse in __propagate_weights()
KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status
tracing/kprobes: Skip symbol counting logic for module symbols in create_local_trace_kprobe()
xen/netfront: fix crash when removing device
ALSA: usb-audio: Fix a DMA to stack memory bug
Linux 5.4.288
UBUNTU: Upstream stable to v5.4.288

** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid

** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Noah Wager (nwager)
Status: In Progress

** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New

** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Noah Wager (nwager)

** Description changed:

SRU Justification

Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:

v5.4.288 upstream stable release
from git://git.kernel.org/

-
+ usb: host: max3421-hcd: Correctly abort a USB request.
+ ata: sata_highbank: fix OF node reference leak in highbank_initialize_phys()
+ usb: dwc2: hcd: Fix GetPortStatus & SetPortFeature
+ usb: ehci-hcd: fix call balance of clocks handling routines
+ usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer
+ xfs: don't drop errno values when we fail to ficlone the entire range
+ bpf, sockmap: Fix update element with same
+ batman-adv: Do not send uninitialized TT changes
+ batman-adv: Remove uninitialized data in full table TT response
+ batman-adv: Do not let TT changes list grows indefinitely
+ tipc: fix NULL deref in cleanup_bearer()
+ net: lapb: increase LAPB_HEADER_LEN
+ ACPI: resource: Fix memory resource type union access
+ qca_spi: Fix clock speed for multiple QCA7000
+ qca_spi: Make driver probing reliable
+ net/sched: netem: account for backlog updates from child qdisc
+ ACPICA: events/evxfregn: don't release the ContextMutex that was never acquired
+ blk-iocost: clamp inuse and skip noops in __propagate_weights()
+ blk-iocost: fix weight updates of inner active iocgs
+ blk-iocost: Avoid using clamp() on inuse in __propagate_weights()
+ KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status
+ tracing/kprobes: Skip symbol counting logic for module symbols in create_local_trace_kprobe()
+ xen/netfront: fix crash when removing device
+ ALSA: usb-audio: Fix a DMA to stack memory bug
Linux 5.4.288
- ALSA: usb-audio: Fix a DMA to stack memory bug
- xen/netfront: fix crash when removing device
- tracing/kprobes: Skip symbol counting logic for module symbols in create_local_trace_kprobe()
- KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status
- blk-iocost: Avoid using clamp() on inuse in __propagate_weights()
- blk-iocost: fix weight updates of inner active iocgs
- blk-iocost: clamp inuse and skip noops in __propagate_weights()
- ACPICA: events/evxfregn: don't release the ContextMutex that was never acquired
- net/sched: netem: account for backlog updates from child qdisc
- qca_spi: Make driver probing reliable
- qca_spi: Fix clock speed for multiple QCA7000
- ACPI: resource: Fix memory resource type union access
- net: lapb: increase LAPB_HEADER_LEN
- tipc: fix NULL deref in cleanup_bearer()
- batman-adv: Do not let TT changes list grows indefinitely
- batman-adv: Remove uninitialized data in full table TT response
- batman-adv: Do not send uninitialized TT changes
- bpf, sockmap: Fix update element with same
- xfs: don't drop errno values when we fail to ficlone the entire range
- usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer
- usb: ehci-hcd: fix call balance of clocks handling routines
- usb: dwc2: hcd: Fix GetPortStatus & SetPortFeature
- ata: sata_highbank: fix OF node reference leak in highbank_initialize_phys()
- usb: host: max3421-hcd: Correctly abort a USB request.
+ UBUNTU: Upstream stable to v5.4.288

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2095199

Title:
Focal update: v5.4.288 upstream stable release

Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress

Bug description:

SRU Justification

Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:

v5.4.288 upstream stable release
from git://git.kernel.org/

usb: host: max3421-hcd: Correctly abort a USB request.
ata: sata_highbank: fix OF node reference leak in highbank_initialize_phys()
usb: dwc2: hcd: Fix GetPortStatus & SetPortFeature
usb: ehci-hcd: fix call balance of clocks handling routines
usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer
xfs: don't drop errno values when we fail to ficlone the entire range
bpf, sockmap: Fix update element with same
batman-adv: Do not send uninitialized TT changes
batman-adv: Remove uninitialized data in full table TT response
batman-adv: Do not let TT changes list grows indefinitely
tipc: fix NULL deref in cleanup_bearer()
net: lapb: increase LAPB_HEADER_LEN
ACPI: resource: Fix memory resource type union access
qca_spi: Fix clock speed for multiple QCA7000
qca_spi: Make driver probing reliable
net/sched: netem: account for backlog updates from child qdisc
ACPICA: events/evxfregn: don't release the ContextMutex that was never acquired
blk-iocost: clamp inuse and skip noops in __propagate_weights()
blk-iocost: fix weight updates of inner active iocgs
blk-iocost: Avoid using clamp() on inuse in __propagate_weights()
KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status
tracing/kprobes: Skip symbol counting logic for module symbols in create_local_trace_kprobe()
xen/netfront: fix crash when removing device
ALSA: usb-audio: Fix a DMA to stack memory bug
Linux 5.4.288
UBUNTU: Upstream stable to v5.4.288

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2095199/+subscriptions

[Bug 2086606] Re: Add list of source files to linux-buildinfo

This bug is awaiting verification that the linux/5.15.0-132.143 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' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.

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-v2 verification-needed-jammy-linux

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2086606

Title:
Add list of source files to linux-buildinfo

Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Fix Committed
Status in linux source package in Plucky:
Fix Committed

Bug description:
[Impact]

For CVE triaging, it's helpful to have an exact list of the source
files used for a build. Add that information to the linux-buildinfo
packages.

[Test Case]

Check content of linux-buildinfo packages of the individual kernels.

Test packages for Noble, Jammy and Focal:
https://launchpad.net/~juergh/+archive/ubuntu/linux/+packages

[Where Problems Could Occur]

Build failures. This does not change the functionality of any of the
kernel packages but just adds another text file to the linux-buildinfo
packages so should not cause any user visible issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086606/+subscriptions