[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
Meanwhile impish reached it's end of life and starting with Ubuntu 22.04 LTS, POWER9 and POWER10 processors are supported and the support for POWER8 ended with Ubuntu 21.10, respectively Ubuntu 20.04 LTS (https://ubuntu.com/download/server/power) and this bug is limited to P8, I'm going to close the 'affects Impish' entry to 'Won't Fix'. ** Changed in: linux (Ubuntu Impish) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998285] Re: 5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
There was a kernel upgrade today (5.15.0.73). there is still that
overflow followed by a crash.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998285
Title:
5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
Status in linux package in Ubuntu:
Confirmed
Bug description:
from dmesg
1.313665] UBSAN: shift-out-of-bounds in
/build/linux-JjvoxS/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
[1.313668] shift exponent 64 is too large for 64-bit type 'long long
unsigned int'
there is also a crash but i don't know if it's related.
1.313671] Call Trace:
[1.313672]
[1.313673] show_stack+0x52/0x5c
[1.313676] dump_stack_lvl+0x4a/0x63
[1.313678] dump_stack+0x10/0x16
[1.313679] ubsan_epilogue+0x9/0x49
[1.313680] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[1.313682] initialize_nocpsch.cold+0x15/0x59 [amdgpu]
[1.313841] device_queue_manager_init+0x208/0x3b0 [amdgpu]
[1.313946] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu]
[1.314079] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu]
[1.314178] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu]
[1.314323] amdgpu_device_init.cold+0x25b/0x7db [amdgpu]
[1.314463] ? do_pci_enable_device+0xdb/0x110
[1.314466] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
[1.314556] amdgpu_pci_probe+0x1ce/0x260 [amdgpu]
[1.314642] local_pci_probe+0x48/0x90
[1.314644] pci_device_probe+0x119/0x1f0
[1.314645] really_probe+0x21f/0x420
[1.314647] __driver_probe_device+0x119/0x190
[1.314648] driver_probe_device+0x23/0xc0
[1.314650] __driver_attach+0xbd/0x1f0
[1.314651] ? __device_attach_driver+0x120/0x120
[1.314652] bus_for_each_dev+0x7c/0xd0
[1.314654] driver_attach+0x1e/0x30
[1.314655] bus_add_driver+0x148/0x220
[1.314656] driver_register+0x95/0x100
[1.314657] __pci_register_driver+0x68/0x70
[1.314659] amdgpu_init+0x7c/0x1000 [amdgpu]
[1.314747] ? 0xc0fc
[1.314748] do_one_initcall+0x46/0x1e0
[1.314750] ? kmem_cache_alloc_trace+0x19e/0x2e0
[1.314752] do_init_module+0x52/0x260
[1.314753] load_module+0xb2b/0xbc0
[1.314754] __do_sys_finit_module+0xbf/0x120
[1.314756] __x64_sys_finit_module+0x18/0x20
[1.314757] do_syscall_64+0x59/0xc0
[1.314758] ? ksys_lseek+0x85/0xc0
[1.314759] ? exit_to_user_mode_prepare+0x37/0xb0
[1.314761] ? syscall_exit_to_user_mode+0x27/0x50
[1.314762] ? __x64_sys_lseek+0x18/0x20
[1.314763] ? do_syscall_64+0x69/0xc0
[1.314764] entry_SYSCALL_64_after_hwframe+0x61/0xcb
[1.314766] RIP: 0033:0x7fef87ab8a3d
[1.314767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
[1.314768] RSP: 002b:7fffe67aa7c8 EFLAGS: 0246 ORIG_RAX:
0139
[1.314770] RAX: ffda RBX: 55d1d00078a0 RCX:
7fef87ab8a3d
[1.314771] RDX: RSI: 7fef87c4f441 RDI:
0018
[1.314772] RBP: 0002 R08: R09:
0002
[1.314772] R10: 0018 R11: 0246 R12:
7fef87c4f441
[1.314773] R13: 55d1d002ea30 R14: 55d1d0011600 R15:
55d1d002eb10
[1.314774]
[1.314778]
gpu is Amd r 380 tonga 4Gb.
I was adviced to try 6.0 series of kernel and I dont see the ubsan error
there but I would like to get the fixes backported 5.15 series.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarkko 1322 F pulseaudio
/dev/snd/controlC1: jarkko 1322 F pulseaudio
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-09-19 (71 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: ASUS System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1007-oem
root=UUID=62a471af-17fd-40e2-9304-b3e113e4f47f ro quiet splash
ProcVersionSignature: Ubuntu 6.0.0-1007.7-oem 6.0.3
RelatedPackageVersions:
linux-restricted-modules-6.0.0-1007-oem N/A
linux-backports-modules-6.0.0-1007-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: vanessa
Uname: Linux 6.0.0-1007-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip
[Kernel-packages] [Bug 2021933] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021933 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: il sottoprocesso installato pacchetto linux- headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 Status in linux package in Ubuntu: Confirmed Bug description: the kernel don't work properly and can't be unintalled or repared ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libkpathsea6:amd64: Install libsynctex2:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: corof 1821 F wireplumber /dev/snd/controlC0: corof 1821 F wireplumber /dev/snd/controlC1: corof 1821 F wireplumber /dev/snd/seq:corof 1818 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 31 06:40:52 2023 ErrorMessage: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2023-02-20 (99 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. enx0050b61f72cc no wireless extensions. MachineType: Dell Inc. Inspiron 560 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=7aa5bd90-70e2-4f81-aae9-f1d3a7582b96 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2010 dmi.bios.release: 0.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 018D1Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/10/2010:br0.5:svnDellInc.:pnInspiron560:pvr00:rvnDellInc.:rn018D1Y:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0: dmi.product.family: 0 dmi.product.name: Inspiron 560 dmi.product.sku: 0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021933] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script post-ins
Public bug reported: the kernel don't work properly and can't be unintalled or repared ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libkpathsea6:amd64: Install libsynctex2:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: corof 1821 F wireplumber /dev/snd/controlC0: corof 1821 F wireplumber /dev/snd/controlC1: corof 1821 F wireplumber /dev/snd/seq:corof 1818 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 31 06:40:52 2023 ErrorMessage: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2023-02-20 (99 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. enx0050b61f72cc no wireless extensions. MachineType: Dell Inc. Inspiron 560 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=7aa5bd90-70e2-4f81-aae9-f1d3a7582b96 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2010 dmi.bios.release: 0.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 018D1Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/10/2010:br0.5:svnDellInc.:pnInspiron560:pvr00:rvnDellInc.:rn018D1Y:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0: dmi.product.family: 0 dmi.product.name: Inspiron 560 dmi.product.sku: 0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021933 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: il sottoprocesso installato pacchetto linux- headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 Status in linux package in Ubuntu: Confirmed Bug description: the kernel don't work properly and can't be unintalled or repared ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libkpathsea6:amd64: Install libsynctex2:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: corof 1821 F wireplumber /dev/snd/controlC0: corof 1821 F wireplumber /dev/snd/controlC1: corof 1821 F wireplumber /dev/snd/seq:corof 1818 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 31 06:40:52 2023 ErrorMessage: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2023-02-20 (99 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. enx0050b61f72cc no wireless extensions. MachineType: Dell Inc. Inspiron 560 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=7aa5bd90-70e2-4f81-aae9-f1d3a7582b96 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script
[Kernel-packages] [Bug 2013353] Re: amdgpu is broken by kernel version 5.4.0-146-generic
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013353 Title: amdgpu is broken by kernel version 5.4.0-146-generic Status in linux package in Ubuntu: Expired Bug description: linux-image-5.4.0-146-generic breaks amdgpu and ROCm 5.4.3 with the following error: > sudo /opt/rocm-5.4.3/bin/rocminfo ROCk module is loaded hsa api call failure at: /long_pathname_so_that_rpms_can_package_the_debug_info/src/rocminfo/rocminfo.cc:1148 Call returned HSA_STATUS_ERROR_OUT_OF_RESOURCES: The runtime failed to allocate the necessary resources. This error may also occur when the core runtime library needs to spawn threads or create internal OS-specific events. strace tool show access issue with the file /dev/dri/renderD128: openat(AT_FDCWD, "/dev/dri/renderD128", O_RDWR|O_CLOEXEC) = -1 EINVAL (Invalid argument) The access groups are set correctly: > ls -l /dev/dri/renderD128 crw-rw 1 root render 226, 128 Mar 30 12:46 /dev/dri/renderD128 > groups marcusmae adm cdrom sudo dip video plugdev render lxd docker I believe the (pseudo)file access is broken due to an issue in kernel module not playing well with a new linux image updated via unattended system update mechanism. EXPECTED RESULT: rocminfo tool works correctly in linux- image-5.4.0-144-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021830] Re: GVE: Performance improvement for "jumbo" frames
** Changed in: linux-gcp (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-gcp (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux-gcp (Ubuntu)
Assignee: (unassigned) => Khaled El Mously (kmously)
** Changed in: linux-gcp (Ubuntu Kinetic)
Assignee: (unassigned) => Khaled El Mously (kmously)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2021830
Title:
GVE: Performance improvement for "jumbo" frames
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Kinetic:
New
Bug description:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and
is being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2021830/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021930] [NEW] kdump cannot generate coredump file on bluefield with 5.4 kernel
Public bug reported: kdump cannot generate coredump file on bluefield with 5.4 kernel Bug description: Following the instruction in https://ubuntu.com/server/docs/kernel-crash-dump, the coredump file cannot be generated. Bluefield is running 5.4 kernel bf2:~$ uname -a Linux sw-mtx-008-bf2 5.4.0-1060-bluefield #66-Ubuntu SMP PREEMPT Mon Mar 27 15:52:50 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux crashkernel parameter is configured bf2:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M bf2:~$ dmesg | grep -i crash [0.00] crashkernel reserved: 0xcfe0 - 0xefe0 (512 MB) [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M [8.070921] pstore: Using crash dump compression: deflate kdump-config is as below: bf2:~$ kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1060-bluefield kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1060-bluefield current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz sysrq: bf2:/# cat /proc/sys/kernel/sysrq 176 After trigged the crash manually with "echo c > /proc/sysrq-trigger", the system could not come up because of OOM. And after change the crashkernel with 1024M memory it still hangs. With default 512M, it hangs at "Killed process 674" [8.718188] systemd-journald[368]: File /var/log/journal/8244d38b2f804fc692f3f2dbf8206f57/system.journal corrupted or uncleanly shut down, renaming and re. [ 30.252513] Out of memory: Killed process 651 (systemd-resolve) total-vm:24380kB, anon-rss:3812kB, file-rss:1828kB, shmem-rss:0kB, UID:101 pgtables:80kB o0 ... [ 34.651927] Out of memory: Killed process 674 (dbus-daemon) total-vm:7884kB, anon-rss:552kB, file-rss:1380kB, shmem-rss:0kB, UID:103 pgtables:52kB oom_sco0 With 1024M, it hangs at following [8.733323] systemd-journald[369]: File /var/log/journal/8244d38b2f804fc692f3f2dbf8206f57/system.journal corrupted or uncleanly shut down, renaming and re. After soft reboot the Bluefield, there's no coredump file generated. bf2:~$ ls /var/crash/ -la total 52 drwxrwxrwt 3 root root4096 May 31 01:43 . drwxr-xr-x 14 root root4096 Apr 30 11:26 .. drwxrwxr-x 2 ubuntu ubuntu 4096 May 31 01:43 202305310143 -rw-r- 1 root root 34307 May 31 01:18 _usr_share_netplan_netplan.script.0.crash -rw-r--r-- 1 root root 0 May 31 03:47 kdump_lock -rw-r--r-- 1 root root 358 May 31 03:48 kexec_cmd bf2:~$ ls /var/crash/202305310143/ -la total 8 drwxrwxr-x 2 ubuntu ubuntu 4096 May 31 01:43 . drwxrwxrwt 3 root root 4096 May 31 01:43 .. This issue also happens on 5.4.0-1049-bluefield kernel. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2021930 Title: kdump cannot generate coredump file on bluefield with 5.4 kernel Status in linux-bluefield package in Ubuntu: New Bug description: kdump cannot generate coredump file on bluefield with 5.4 kernel Bug description: Following the instruction in https://ubuntu.com/server/docs/kernel-crash-dump, the coredump file cannot be generated. Bluefield is running 5.4 kernel bf2:~$ uname -a Linux sw-mtx-008-bf2 5.4.0-1060-bluefield #66-Ubuntu SMP PREEMPT Mon Mar 27 15:52:50 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux crashkernel parameter is configured bf2:~$ cat /proc/cmdline
[Kernel-packages] [Bug 2008977] Re: Make Wayland sessions work with fbdev
** Description changed: Make Wayland sessions work with fbdev. For when KMS/DRM support is missing in the kernel but the device still has legacy graphics. Currently Xorg already does this with a custom driver that allows it to fall back to using fbdev. We could do the same with mutter but it's unlikely to be accepted by upstream since Fedora opted to solve it by just enabling SimpleDRM in the kernel: https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers This started out being a personal goal for me but will also be a - business requirement in future as Ubuntu Core Desktop does not ship Xorg - (but does ship Xwayland). So we need to give mutter some way of using - fbdev graphics. + business requirement in future to not ship Xorg. So we need to give + mutter some way of using fbdev graphics. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008977 Title: Make Wayland sessions work with fbdev Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Bug description: Make Wayland sessions work with fbdev. For when KMS/DRM support is missing in the kernel but the device still has legacy graphics. Currently Xorg already does this with a custom driver that allows it to fall back to using fbdev. We could do the same with mutter but it's unlikely to be accepted by upstream since Fedora opted to solve it by just enabling SimpleDRM in the kernel: https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers This started out being a personal goal for me but will also be a business requirement in future to not ship Xorg. So we need to give mutter some way of using fbdev graphics. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021572] Re: dGPU cannot resume because system firmware stuck in IPCS method
** Tags added: oem-priority originate-from-2012589 stella ** Tags added: originate-from-1955560 ** Tags added: originate-from-1969426 ** Tags added: originate-from-1943101 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2021572 Title: dGPU cannot resume because system firmware stuck in IPCS method Status in HWE Next: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: [Impact] When a dGPU on a laptop is in PCIe D3cold and TBT port is connected to a monitor via a cable, unplugging the cable will make the dGPU unable to resume to D0. [Fix] There's a part of system firmware, IOM, need the driver to disconnect all TBT/Type-C phy to let dGPU function normally. [Test] With the fix applied, the dGPU continues to work after replugging video cable many times. [Where problems could occur] The fix is composed of several overhaul, so it's likely to regression i915 GFX driver. To limit the impact, only target OEM kernel for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-iot/5.4.0.1016.14)
All autopkgtests for the newly accepted linux-meta-iot (5.4.0.1016.14) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-iot/5.4.0-1016.17 (arm64) 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/focal/update_excuses.html#linux-meta-iot [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021907] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676788/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting
[Kernel-packages] [Bug 2021907] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676786/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM:
[Kernel-packages] [Bug 2021907] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676787/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state
[Kernel-packages] [Bug 2021907] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676785/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM:
[Kernel-packages] [Bug 2021907] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676784/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM:
[Kernel-packages] [Bug 2021907] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676781/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state
[Kernel-packages] [Bug 2021907] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676783/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state
[Kernel-packages] [Bug 2021907] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676782/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight
[Kernel-packages] [Bug 2021907] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676780/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring
[Kernel-packages] [Bug 2021907] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676779/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM:
[Kernel-packages] [Bug 2021907] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676777/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM:
[Kernel-packages] [Bug 2021907] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676778/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM:
[Kernel-packages] [Bug 2021907] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676775/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM:
[Kernel-packages] [Bug 2021907] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676776/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM: suspend
[Kernel-packages] [Bug 2021907] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676774/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM: suspend
[Kernel-packages] [Bug 2021907] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676773/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM:
[Kernel-packages] [Bug 2021907] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676772/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state
[Kernel-packages] [Bug 2021907] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2021907/+attachment/5676771/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM: suspend
[Kernel-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
apport information ** Tags added: apport-collected vera ** Description changed: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM: suspend exit wls1: authenticate with 00:5f:67:61:e0:ba wls1: send auth to 00:5f:67:61:e0:ba (try 1/3) wls1: authenticated wls1: associate with 00:5f:67:61:e0:ba (try 1/3) wls1: RX AssocResp from 00:5f:67:61:e0:ba (capab=0x411 status=0 aid=3) wls1: associated IPv6: ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready The cursor also seems to dissapear after some use,
[Kernel-packages] [Bug 2021907] 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 2021907 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Incomplete Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core
[Kernel-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
** Attachment added: "Some letters in filenames are corrupted, and seem to be corrupted in the same way." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021907/+attachment/5676769/+files/PXL_20230529_131221080.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Incomplete Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer
[Kernel-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
** Attachment added: "Chromium freeze shown on secondary display, before it unfreezes. Internal screen was off." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021907/+attachment/5676768/+files/PXL_20230529_145115592.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in linux package in Ubuntu: Incomplete Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM
[Kernel-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
The following is various system info: /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz stepping: 5 microcode : 0x7 cpu MHz : 1596.109 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm arat flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown bogomips: 6118.41 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz stepping: 5 microcode : 0x7 cpu MHz : 1345.395 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm arat flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown bogomips: 6118.41 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz stepping: 5 microcode : 0x7 cpu MHz : 1197.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 2 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm arat flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown bogomips: 6118.41 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz stepping: 5 microcode : 0x7 cpu MHz : 1379.151 cache size : 4096 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 2 apicid : 5 initial apicid : 5 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm arat flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown bogomips: 6118.41 clflush size: 64
[Kernel-packages] [Bug 2021907] [NEW] Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
Public bug reported: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed OOM killer enabled. Restarting tasks ... done. video LNXVIDEO:00: Restoring backlight state PM: suspend exit wls1: authenticate with 00:5f:67:61:e0:ba wls1: send auth to 00:5f:67:61:e0:ba (try 1/3) wls1: authenticated wls1: associate with 00:5f:67:61:e0:ba (try 1/3) wls1: RX AssocResp from 00:5f:67:61:e0:ba (capab=0x411 status=0 aid=3) wls1: associated IPv6: ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready The cursor also seems to dissapear after some use, although it remains functional. What I mean is the "icon" for it doesn't exist anymore, but moving the mouse around I can see some buttons display their shadows indicating that the mouse is above them and clicking the buttons works. Using SWcursor in Xorg "fixes"
[Kernel-packages] [Bug 2021900] [NEW] Ubuntu 22.04 with Nvidia: linux-image-5.15.0-72-generic: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to allocate NvKmsKapiDevic
Public bug reported: After updating from linux-image-5.15.0-71-generic, my machine failed to load the module properly and was only running minimal resolution in the desktop environment. Part of journalctl -t kernel: Mai 30 19:22:44 iso-deskubuntu kernel: NVRM gpuInitOptimusSettings_IMPL: SBIOS did not acknowledge cfg space owner change Mai 30 19:22:44 iso-deskubuntu kernel: NVRM: Open nvidia.ko is only ready for use on Data Center GPUs. Mai 30 19:22:44 iso-deskubuntu kernel: NVRM: To force use of Open nvidia.ko on other GPUs, see the Mai 30 19:22:44 iso-deskubuntu kernel: NVRM: 'OpenRmEnableUnsupportedGpus' kernel module parameter described Mai 30 19:22:44 iso-deskubuntu kernel: NVRM: in the README. Mai 30 19:22:45 iso-deskubuntu kernel: NVRM: GPU :09:00.0: RmInitAdapter failed! (0x62:0x0:1835) Mai 30 19:22:45 iso-deskubuntu kernel: NVRM: GPU :09:00.0: rm_init_adapter failed, device minor number 0 Mai 30 19:22:45 iso-deskubuntu kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0900] Failed to allocate NvKmsKapiDevice Mai 30 19:22:45 iso-deskubuntu kernel: [drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0900] Failed to register device The issue does not occur when booting the older still installed kernel (by selecting it in grub loader). I had nvidia-driver-525-open installed, but the issue also occurs with nvidia-driver-530-open. nvidia-driver-530 (without -open) does not have the problem. I was also able to use -open again by creating a file with content "options nvidia NVreg_OpenRmEnableUnsupportedGpus=1" in /etc/modprobe.d/nvidia-open-unsupported-gpus.conf. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2021900 Title: Ubuntu 22.04 with Nvidia: linux-image-5.15.0-72-generic: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0900] Failed to allocate NvKmsKapiDevice Status in linux-signed package in Ubuntu: New Bug description: After updating from linux-image-5.15.0-71-generic, my machine failed to load the module properly and was only running minimal resolution in the desktop environment. Part of journalctl -t kernel: Mai 30 19:22:44 iso-deskubuntu kernel: NVRM gpuInitOptimusSettings_IMPL: SBIOS did not acknowledge cfg space owner change Mai 30 19:22:44 iso-deskubuntu kernel: NVRM: Open nvidia.ko is only ready for use on Data Center GPUs. Mai 30 19:22:44 iso-deskubuntu kernel: NVRM: To force use of Open nvidia.ko on other GPUs, see the Mai 30 19:22:44 iso-deskubuntu kernel: NVRM: 'OpenRmEnableUnsupportedGpus' kernel module parameter described Mai 30 19:22:44 iso-deskubuntu kernel: NVRM: in the README. Mai 30 19:22:45 iso-deskubuntu kernel: NVRM: GPU :09:00.0: RmInitAdapter failed! (0x62:0x0:1835) Mai 30 19:22:45 iso-deskubuntu kernel: NVRM: GPU :09:00.0: rm_init_adapter failed, device minor number 0 Mai 30 19:22:45 iso-deskubuntu kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0900] Failed to allocate NvKmsKapiDevice Mai 30 19:22:45 iso-deskubuntu kernel: [drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0900] Failed to register device The issue does not occur when booting the older still installed kernel (by selecting it in grub loader). I had nvidia-driver-525-open installed, but the issue also occurs with nvidia-driver-530-open. nvidia-driver-530 (without -open) does not have the problem. I was also able to use -open again by creating a file with content "options nvidia NVreg_OpenRmEnableUnsupportedGpus=1" in /etc/modprobe.d/nvidia-open-unsupported-gpus.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2021900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950721] Re: Re-enable CONFIG_PINCTRL_ELKHARTLAKE
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950721 Title: Re-enable CONFIG_PINCTRL_ELKHARTLAKE Status in HWE Next: Fix Released Status in linux-intel-5.13 package in Ubuntu: Fix Released Bug description: We have test BIOS now for supporting pinctrl. From what we learnt, ODMs also got the BIOS fix, it's now time to re-enable this kernel config. [Impact] Without this fix, pinctrl functionality will be missing. [Test plan] 1. Make sure the computer has a BIOS that supports pinctrl for EHL 2. Before installing the new kernel, GPIO should not work 3. Install the new kernel, and confirm GPIO works [Where problems could occur] If the computer does not have a BIOS that support pinctrl, you will get an error like "kernel NULL pointer dereference in intel_pinctrl_get_soc_data" during system boot. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021886] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021886 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: kernel panic unable to mount root fs ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libssl3:amd64: Install libssl3:i386: Install openssl:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: victor 2001 F wireplumber /dev/snd/seq:victor 1998 F pipewire CasperMD5CheckResult: unknown Date: Tue May 30 13:37:34 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=084bb2c6-46f7-4374-b02f-59e4f2e61288 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-29 (30 days ago) dmi.bios.date: 07/24/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4212 dmi.board.asset.tag: Default string dmi.board.name: H110I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4212:bd07/24/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110I-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021886] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021886 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: kernel panic unable to mount root fs ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libssl3:amd64: Install libssl3:i386: Install openssl:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: victor 2001 F wireplumber /dev/snd/seq:victor 1998 F pipewire CasperMD5CheckResult: unknown Date: Tue May 30 13:37:34 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=084bb2c6-46f7-4374-b02f-59e4f2e61288 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-29 (30 days ago) dmi.bios.date: 07/24/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4212 dmi.board.asset.tag: Default string dmi.board.name: H110I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4212:bd07/24/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110I-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021886] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess
Public bug reported: kernel panic unable to mount root fs ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libssl3:amd64: Install libssl3:i386: Install openssl:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: victor 2001 F wireplumber /dev/snd/seq:victor 1998 F pipewire CasperMD5CheckResult: unknown Date: Tue May 30 13:37:34 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=084bb2c6-46f7-4374-b02f-59e4f2e61288 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-29 (30 days ago) dmi.bios.date: 07/24/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4212 dmi.board.asset.tag: Default string dmi.board.name: H110I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4212:bd07/24/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110I-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021886 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: kernel panic unable to mount root fs ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libssl3:amd64: Install libssl3:i386: Install openssl:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: victor 2001 F wireplumber /dev/snd/seq:victor 1998 F pipewire CasperMD5CheckResult: unknown Date: Tue May 30 13:37:34 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=084bb2c6-46f7-4374-b02f-59e4f2e61288 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-29 (30 days ago) dmi.bios.date: 07/24/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4212 dmi.board.asset.tag:
[Kernel-packages] [Bug 2019222] Re: [IOTG][RPL] Integrated TSN controller (stmmac) driver enabling
** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-intel-iotg (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2019222 Title: [IOTG][RPL] Integrated TSN controller (stmmac) driver enabling Status in linux-intel-iotg package in Ubuntu: Fix Committed Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/1996592 - Description Enable Integrated TSN controller (stmmac) driver Hardware: Raptor Lake Target Release: 22.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.19-linux-221019T120731Z 0001-igc-Disable-PTM-sequences-when-interface-goes-down.tsn 0001-taprio-Add-support-for-frame-preemption-offload.tsn 0002-xsk-add-txtime-field-in-xdp_desc-struct.tsn 0003-tc-Add-index-of-FPE-QMASK.tsn 0004-net-pcs-xpcs-enable-xpcs-reset-skipping.tsn 0007-net-stmmac-add-FPE-preempt-setting-for-TxQ-preemptible.tsn 0008-net-stmmac-support-recalculating-of-CBS-idle-slope-und.tsn 0009-net-stmmac-Add-module-param-to-del-keep-est-hw-conf.tsn 0011-net-stmmac-restructure-Rx-Tx-hardware-timestamping-fun.tsn 0013-net-stmmac-introduce-AF_XDP-ZC-TX-HW-timestamps.tsn 0018-net-stmmac-skip-runtime-handling-in-mdio-read-write.tsn 0019-net-stmmac-Add-support-for-HW-accelerated-VLAN-strippi.tsn 0025-net-phy-add-wrapper-function-for-setup-master-slave-se.tsn 0027-net-stmmac-Adjust-mac_capabilities-for-Intel-mGbE-2.5G.tsn 0031-net-stmmac-fix-deadlock-caused-by-taking-RTNL-in-RPM-r.tsn 0034-stmmac-intel-Separate-ADL-N-and-RPL-P-device-ID-from-T.tsn 0038-stmmac-intel-skip-xpcs-reset-for-2.5Gbps-on-Intel-Alde.tsn 0001-net-phy-marvell10g-Add-check-after-reading-phy-interru.tsn 0002-taprio-Add-check-for-NULL-struct-before-accessing-the-.tsn 0001-Revert-igc-Disable-PTM-sequences-when-interface-goes-d.tsn 0002-igc-Set-the-RX-packet-buffer-size-for-TSN-mode.tsn 0003-igc-Only-dump-registers-if-configured-to-dump-HW-infor.tsn 0004-ethtool-Add-support-for-configuring-and-verifying-fram.tsn 0005-core-Introduce-netdev_tc_map_to_queue_mask.tsn 0006-taprio-Replace-tc_map_to_queue_mask.tsn 0007-mqprio-Add-support-for-frame-preemption-offload.tsn 0008-igc-Add-support-for-enabling-frame-preemption-via-etht.tsn 0009-ethtool-Add-support-for-configuring-frame-preemption-v.tsn 0010-igc-Add-support-for-TC_SETUP_PREEMPT.tsn 0011-igc-Add-support-for-setting-frame-preemption-configura.tsn 0012-igc-Add-support-for-Frame-Preemption-verification.tsn 0013-igc-Add-support-for-exposing-frame-preemption-stats-re.tsn 0014-igc-Optimize-the-packet-buffer-utilization.tsn 0015-igc-Add-support-for-enabling-all-packets-to-be-receive.tsn 0016-igc-Fix-race-condition-in-PTP-Tx-code.tsn 0017-igc-Add-support-for-DMA-timestamp-for-non-PTP-packets.tsn 0018-igc-Correct-the-launchtime-offset.tsn 0019-igc-Export-LEDs.tsn --> cf8331825a8d10e46fa574fdf015a65cb5a6db86 (v5.15-rc1) 0020-bpf-add-btf-register-unregister-API.tsn 0021-net-core-XDP-metadata-BTF-netlink-API.tsn 0022-rtnetlink-Fix-unchecked-return-value-of-dev_xdp_query_.tsn 0023-rtnetlink-Add-return-value-check.tsn 0024-tools-bpf-Query-XDP-metadata-BTF-ID.tsn 0025-tools-bpf-Add-xdp-set-command-for-md-btf.tsn 0026-igc-Add-BTF-based-metadata-for-XDP.tsn 0027-igc-Enable-HW-RX-Timestamp-for-AF_XDP-ZC.tsn 0028-igc-Enable-HW-TX-Timestamp-for-AF_XDP-ZC.tsn 0029-igc-Enable-trace-for-HW-TX-Timestamp-AF_XDP-ZC.tsn 0030-igc-Remove-the-CONFIG_DEBUG_MISC-condition-for-trace.tsn 0031-igc-Take-care-of-DMA-timestamp-rollover.tsn 0032-igc-Use-strict-cycles-for-LaunchTime-mode.tsn 0033-igc-Fix-sending-packets-too-early.tsn 0034-igc-Add-SO_TXTIME-for-AF_XDP-ZC.tsn 0035-igc-Fix-scheduling-multiple-packets-for-next-cycle.tsn 0036-igc-Add-context-for-empty-packet.tsn 0037-igc-Reodering-the-empty-packet-buffers-and-descriptors.tsn 0038-igc-Add-trace-for-launchtime-calculation-corner-case.tsn 0039-igc-Configure-BaseT-after-start-and-end-time-queue-reg.tsn 0040-igc-Remove-PTM-trigger-from-initialization-sequence.tsn 0001-net-stmmac-update-MAC-capabilities-when-tx-queues-are-.tsn 0002-net-stmmac-add-check-for-2.5G-mode-to-prevent-MAC-capa.tsn 0001-Revert-tc-Add-index-of-FPE-QMASK.tsn 0002-Revert-ethtool-Add-support-for-configuring-and-verifyi.tsn 0003-Revert-ethtool-Add-support-for-configuring-frame-preem.tsn 0004-ethtool-Add-support-for-configuring-frame-preemption.tsn 0005-ethtool-Add-support-for-Frame-Preemption-verification.tsn 0001-net-stmmac-check-supported-linkmode-request-for-set-ee.tsn To manage notifications about this bug go to:
[Kernel-packages] [Bug 2021474] 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 2021474 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021474 Title: Linux kernel image 5.19-0-42.43~22.04.1 crashs VM in Virtualbox Status in linux package in Ubuntu: Incomplete Bug description: After upgrading the Linux kernel of an Ubuntu 22.04.2 VM in Virtualbox (version 6.1.44 r156814) to version 5.19-0-42.43 the VM crashs on some graphical operations, e.g. starting Firefox. The VM lgofile shows at this moment: 03:08:01.362162 Display::i_handleDisplayResize: uScreenId=0 pvVRAM= w=1920 h=1200 bpp=0 cbLine=0x0 flags=0x2 origin=0,0 There is no reset of these settings to reasonable values as in an similar operation before: 03:06:14.431345 Display::i_handleDisplayResize: uScreenId=0 pvVRAM= w=1920 h=1200 bpp=0 cbLine=0x0 flags=0x2 origin=0,0 03:06:14.433677 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=7f354df0 w=1920 h=1200 bpp=32 cbLine=0x1E00 flags=0x1 origin=0,0 The VM display is completely black and no input is accepted anymore even Virtualbox control commands like "VBoxManage controlvm VM acpipowerbutton" are ignored. There were no such problems with kernels up to 5.19-0-41. To be exact the system in the VM doesn't really crashs, it is still working in some way (I was able to verify that by the load generated by scheduled virus scan runs in the VM) but no output is shown nor any input is accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021474] Re: Linux kernel image 5.19-0-42.43~22.04.1 crashs VM in Virtualbox
** Package changed: linux-hwe-5.19 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021474 Title: Linux kernel image 5.19-0-42.43~22.04.1 crashs VM in Virtualbox Status in linux package in Ubuntu: Incomplete Bug description: After upgrading the Linux kernel of an Ubuntu 22.04.2 VM in Virtualbox (version 6.1.44 r156814) to version 5.19-0-42.43 the VM crashs on some graphical operations, e.g. starting Firefox. The VM lgofile shows at this moment: 03:08:01.362162 Display::i_handleDisplayResize: uScreenId=0 pvVRAM= w=1920 h=1200 bpp=0 cbLine=0x0 flags=0x2 origin=0,0 There is no reset of these settings to reasonable values as in an similar operation before: 03:06:14.431345 Display::i_handleDisplayResize: uScreenId=0 pvVRAM= w=1920 h=1200 bpp=0 cbLine=0x0 flags=0x2 origin=0,0 03:06:14.433677 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=7f354df0 w=1920 h=1200 bpp=32 cbLine=0x1E00 flags=0x1 origin=0,0 The VM display is completely black and no input is accepted anymore even Virtualbox control commands like "VBoxManage controlvm VM acpipowerbutton" are ignored. There were no such problems with kernels up to 5.19-0-41. To be exact the system in the VM doesn't really crashs, it is still working in some way (I was able to verify that by the load generated by scheduled virus scan runs in the VM) but no output is shown nor any input is accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation
This bug is awaiting verification that the linux-kvm/5.15.0-1035.40 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-kvm verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-kvm source package in Jammy: Confirmed Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021605] Re: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Lunar) Assignee: (unassigned) => Andrei Gherzan (agherzan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021605 Title: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Lunar: Incomplete Status in linux-aws source package in Lunar: New Status in linux source package in Mantic: Incomplete Status in linux-aws source package in Mantic: New Bug description: [Impact] Provide a variable do_lib_rust=true|false in the kernel build system to selectively enable the Rust packaging (linux-lib-rust) with specific kernels and specific architectures. Right now Rust should be enabled only in lunar and mantic and only on amd64. [Test case] Build the kernel producing all the debs. [Fix] Introduce a do_lib_rust=true variable that will be defined only in debian.master/rules.d/amd64.mk for now. [Regression potential] Kernels may need to set this variables if they want to enable the Rust support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-74.81~20.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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal-linux-hwe-5.15 verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021830] [NEW] GVE: Performance improvement for "jumbo" frames
Public bug reported:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and is
being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
** Affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-gcp (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: debootstrap (Ubuntu)
** Also affects: linux-gcp (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2021830
Title:
GVE: Performance improvement for "jumbo" frames
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Kinetic:
New
Bug description:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and
is being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2021830/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021439] Re: firmware rtl8168e-3.fw for r8169 10ec:8168 doesn't load
Can you attach dmesg from the Ubuntu kernel, please? ** Changed in: linux-meta-hwe-5.19 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2021439 Title: firmware rtl8168e-3.fw for r8169 10ec:8168 doesn't load Status in linux-meta-hwe-5.19 package in Ubuntu: Incomplete Bug description: After a reboot, my NIC has status and activity leds working, mii-tool reports link status and speed, but ethtool reports unknown speed and duplex and 'ip link' reports status DOWN. I have no connectivity and cannot use the interface at all. Booting the system using Debian stable, works. The NIC also works in Windows 10. I observed that Debian kernel 5.10 loads the firmware file rtl_nic/rtl8168e-3.fw, while ubuntu doesn't even attempt to (or does not report back) $ sudo mii-tool ens3 ens3: negotiated 1000baseT-FD flow-control, link ok $ ip link show dev ens3 3: ens3: mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether a0:2e:15:00:02:41 brd ff:ff:ff:ff:ff:ff altname enp2s0 $ sudo ethtool ens3 Settings for ens3: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on master-slave cfg: preferred slave master-slave status: unknown Port: Twisted Pair PHYAD: 0 Transceiver: external MDI-X: Unknown Supports Wake-on: pumbg Wake-on: d Link detected: no $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-meta-hwe-5.19 N: Unable to locate package linux-meta-hwe-5.19 N: Couldn't find any package by glob 'linux-meta-hwe-5.19' N: Couldn't find any package by regex 'linux-meta-hwe-5.19' $ apt-cache policy linux-image-generic-hwe-22.04 linux-image-generic-hwe-22.04: Installed: 5.19.0.42.43~22.04.15 Candidate: 5.19.0.42.43~22.04.15 Version table: *** 5.19.0.42.43~22.04.15 500 500 http://ro.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://ro.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-22.04 5.19.0.42.43~22.04.15 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon May 29 03:25:52 2023 InstallationDate: Installed on 2021-11-30 (544 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-meta-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-01-25 (488 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2021439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021563] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676623/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType:
[Kernel-packages] [Bug 2021563] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676620/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB:
[Kernel-packages] [Bug 2021563] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676622/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0
[Kernel-packages] [Bug 2021563] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676619/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed)
[Kernel-packages] [Bug 2021563] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676621/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb
[Kernel-packages] [Bug 2021563] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676616/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB:
[Kernel-packages] [Bug 2021563] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676617/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not
[Kernel-packages] [Bug 2021563] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676618/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB:
[Kernel-packages] [Bug 2021563] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676615/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb
[Kernel-packages] [Bug 2021563] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676614/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0
[Kernel-packages] [Bug 2021563] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676613/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0
[Kernel-packages] [Bug 2021563] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676612/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb
[Kernel-packages] [Bug 2021563] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676611/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0
[Kernel-packages] [Bug 2021563] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676610/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb
[Kernel-packages] [Bug 2021563] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676608/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed)
[Kernel-packages] [Bug 2021563] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676609/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0
[Kernel-packages] [Bug 2021563] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2021563/+attachment/5676607/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Confirmed Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1469 F wireplumber /dev/snd/seq:bernie 1464 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-31 (364 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP EliteBook 8560p Package: linux (not installed) ProcFB: 0 i915drmfb
[Kernel-packages] [Bug 2021563] Re: Unknown kernel command line parameters
apport information ** Tags added: apport-collected ** Description changed: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: bernie 1469 F wireplumber + /dev/snd/seq:bernie 1464 F pipewire + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-05-31 (364 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: Hewlett-Packard HP EliteBook 8560p + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init + ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 + PulseList: Error: command
Re: [Kernel-packages] [Bug 2021438] Status changed to Confirmed
thank you very much. Att. Luciley Brito Ícone "Verificada pela comunidade" Em 29/05/2023 04:00, Ubuntu Kernel Bot escreveu: > This change was made by a bot. > > ** Changed in: linux (Ubuntu) > Status: New => Confirmed > ** Attachment added: "ZwkSWhMG0ImJQvgs.png" https://bugs.launchpad.net/bugs/2021438/+attachment/5676604/+files/ZwkSWhMG0ImJQvgs.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021438 Title: Lenovo IdeaPad L340-15IRH screen does not turn on when woken (until the backlight is adjusted) Status in linux package in Ubuntu: Confirmed Bug description: When the system turns off the screen by power management, the screen does not come back active again, having to activate the brightness keys for it to come back. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 28 21:14:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:3a2d] NVIDIA Corporation GP107M [GeForce GTX 1050 3 GB Max-Q] [10de:1c91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP107M [GeForce GTX 1050 3 GB Max-Q] [17aa:3a2d] InstallationDate: Installed on 2023-05-28 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 81TR ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=efac633a-69bd-49a0-b3ca-ba7e617e416a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO IDEAPAD L340-15IRH dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrBGCN34WW:bd05/21/2021:br1.34:efr1.34:svnLENOVO:pn81TR:pvrLENOVOIDEAPADL340-15IRH:rvnLENOVO:rnINVALID:rvrNoDPK:cvnLENOVO:ct10:cvrLENOVOIDEAPADL340-15IRH:skuLENOVO_MT_81TR_BU_idea_FM_IDEAPAD: dmi.product.family: IDEAPAD dmi.product.name: 81TR dmi.product.sku: LENOVO_MT_81TR_BU_idea_FM_IDEAPAD dmi.product.version: LENOVO IDEAPAD L340-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021748] Re: powerpc/eeh:eeh-basic.sh test fails for lunar and kinetic
** Attachment added: "dmesg_broken.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021748/+attachment/5676603/+files/dmesg_log_broke.txt ** Changed in: linux (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: linux (Ubuntu Lunar) Status: New => Confirmed ** Summary changed: - powerpc/eeh:eeh-basic.sh test fails for lunar and kinetic + powerpc/eeh:eeh-basic.sh ubuntu_kernel_selftests fails for lunar and kinetic ** Description changed: ubuntu_kernel_selftests:powerpc/eeh:eeh-basic.sh is failing for lunar and kinetic with pci devices failing to recover with EEH error recovery handling, ... [stdout] # 0003:01:00.0, Failed to recover! [stdout] # Breaking 0004:02:00.0... [stdout] # 0004:02:00.0, Recovered after 0 seconds [stdout] # Breaking 0005:01:00.0... [stdout] # 0005:01:00.0, Failed to recover! [stdout] # 3 devices failed to recover (4 tested) - The problematic commit that seems to introduce this issue via an upstream stable update is + The problematic commit in kinetic that seems to introduce this issue via an upstream stable update is: commit d71c64381810850d55d5868ab1e29ac117e22f1c PCI: Unify delay handling for reset and resume BugLink: https://bugs.launchpad.net/bugs/2018948 commit ac91e6980563ed53afadd925fa6585ffd2bc4a2c upstream. where reverting the commit fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021748 Title: powerpc/eeh:eeh-basic.sh ubuntu_kernel_selftests fails for lunar and kinetic Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Confirmed Bug description: ubuntu_kernel_selftests:powerpc/eeh:eeh-basic.sh is failing for lunar and kinetic with pci devices failing to recover with EEH error recovery handling, ... [stdout] # 0003:01:00.0, Failed to recover! [stdout] # Breaking 0004:02:00.0... [stdout] # 0004:02:00.0, Recovered after 0 seconds [stdout] # Breaking 0005:01:00.0... [stdout] # 0005:01:00.0, Failed to recover! [stdout] # 3 devices failed to recover (4 tested) The problematic commit in kinetic that seems to introduce this issue via an upstream stable update is: commit d71c64381810850d55d5868ab1e29ac117e22f1c PCI: Unify delay handling for reset and resume BugLink: https://bugs.launchpad.net/bugs/2018948 commit ac91e6980563ed53afadd925fa6585ffd2bc4a2c upstream. where reverting the commit fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021748] Re: powerpc/eeh:eeh-basic.sh test fails for lunar and kinetic
** Attachment added: "dmesg_after_revert" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021748/+attachment/5676602/+files/dmesg_log_verygood.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021748 Title: powerpc/eeh:eeh-basic.sh ubuntu_kernel_selftests fails for lunar and kinetic Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Confirmed Bug description: ubuntu_kernel_selftests:powerpc/eeh:eeh-basic.sh is failing for lunar and kinetic with pci devices failing to recover with EEH error recovery handling, ... [stdout] # 0003:01:00.0, Failed to recover! [stdout] # Breaking 0004:02:00.0... [stdout] # 0004:02:00.0, Recovered after 0 seconds [stdout] # Breaking 0005:01:00.0... [stdout] # 0005:01:00.0, Failed to recover! [stdout] # 3 devices failed to recover (4 tested) The problematic commit in kinetic that seems to introduce this issue via an upstream stable update is: commit d71c64381810850d55d5868ab1e29ac117e22f1c PCI: Unify delay handling for reset and resume BugLink: https://bugs.launchpad.net/bugs/2018948 commit ac91e6980563ed53afadd925fa6585ffd2bc4a2c upstream. where reverting the commit fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021748] [NEW] powerpc/eeh:eeh-basic.sh ubuntu_kernel_selftests fails for lunar and kinetic
Public bug reported: ubuntu_kernel_selftests:powerpc/eeh:eeh-basic.sh is failing for lunar and kinetic with pci devices failing to recover with EEH error recovery handling, ... [stdout] # 0003:01:00.0, Failed to recover! [stdout] # Breaking 0004:02:00.0... [stdout] # 0004:02:00.0, Recovered after 0 seconds [stdout] # Breaking 0005:01:00.0... [stdout] # 0005:01:00.0, Failed to recover! [stdout] # 3 devices failed to recover (4 tested) The problematic commit in kinetic that seems to introduce this issue via an upstream stable update is: commit d71c64381810850d55d5868ab1e29ac117e22f1c PCI: Unify delay handling for reset and resume BugLink: https://bugs.launchpad.net/bugs/2018948 commit ac91e6980563ed53afadd925fa6585ffd2bc4a2c upstream. where reverting the commit fixes the issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Description changed: ubuntu_kernel_selftests:powerpc/eeh:eeh-basic.sh is failing for lunar and kinetic with pci devices failing to recover with EEH error recovery handling, ... [stdout] # 0003:01:00.0, Failed to recover! [stdout] # Breaking 0004:02:00.0... [stdout] # 0004:02:00.0, Recovered after 0 seconds [stdout] # Breaking 0005:01:00.0... [stdout] # 0005:01:00.0, Failed to recover! [stdout] # 3 devices failed to recover (4 tested) - - The problematic commit that seems to introduce this issue via an upstream stable update is + The problematic commit that seems to introduce this issue via an upstream stable update is commit d71c64381810850d55d5868ab1e29ac117e22f1c PCI: Unify delay handling for reset and resume BugLink: https://bugs.launchpad.net/bugs/2018948 commit ac91e6980563ed53afadd925fa6585ffd2bc4a2c upstream. - where reverting the commit + where reverting the commit fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021748 Title: powerpc/eeh:eeh-basic.sh ubuntu_kernel_selftests fails for lunar and kinetic Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Confirmed Bug description: ubuntu_kernel_selftests:powerpc/eeh:eeh-basic.sh is failing for lunar and kinetic with pci devices failing to recover with EEH error recovery handling, ... [stdout] # 0003:01:00.0, Failed to recover! [stdout] # Breaking 0004:02:00.0... [stdout] # 0004:02:00.0, Recovered after 0 seconds [stdout] # Breaking 0005:01:00.0... [stdout] # 0005:01:00.0, Failed to recover! [stdout] # 3 devices failed to recover (4 tested) The problematic commit in kinetic that seems to introduce this issue via an upstream stable update is: commit d71c64381810850d55d5868ab1e29ac117e22f1c PCI: Unify delay handling for reset and resume BugLink: https://bugs.launchpad.net/bugs/2018948 commit ac91e6980563ed53afadd925fa6585ffd2bc4a2c upstream. where reverting the commit fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021749] [NEW] mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors
Public bug reported: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2021749 Title: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2021749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Same problem. It works, when you start "google-chrome" with the parameter "--no-sandbox" (which is not a solution, because it raises security concerns). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021605] 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 2021605 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 ** Changed in: linux (Ubuntu Lunar) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021605 Title: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package Status in linux package in Ubuntu: Incomplete Status in linux source package in Lunar: Incomplete Status in linux source package in Mantic: Incomplete Bug description: [Impact] Provide a variable do_lib_rust=true|false in the kernel build system to selectively enable the Rust packaging (linux-lib-rust) with specific kernels and specific architectures. Right now Rust should be enabled only in lunar and mantic and only on amd64. [Test case] Build the kernel producing all the debs. [Fix] Introduce a do_lib_rust=true variable that will be defined only in debian.master/rules.d/amd64.mk for now. [Regression potential] Kernels may need to set this variables if they want to enable the Rust support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021605] [NEW] introduce do_lib_rust=true|false to enable/disable linux-lib-rust package
Public bug reported: [Impact] Provide a variable do_lib_rust=true|false in the kernel build system to selectively enable the Rust packaging (linux-lib-rust) with specific kernels and specific architectures. Right now Rust should be enabled only in lunar and mantic and only on amd64. [Test case] Build the kernel producing all the debs. [Fix] Introduce a do_lib_rust=true variable that will be defined only in debian.master/rules.d/amd64.mk for now. [Regression potential] Kernels may need to set this variables if they want to enable the Rust support. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021605 Title: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package Status in linux package in Ubuntu: Incomplete Status in linux source package in Lunar: Incomplete Status in linux source package in Mantic: Incomplete Bug description: [Impact] Provide a variable do_lib_rust=true|false in the kernel build system to selectively enable the Rust packaging (linux-lib-rust) with specific kernels and specific architectures. Right now Rust should be enabled only in lunar and mantic and only on amd64. [Test case] Build the kernel producing all the debs. [Fix] Introduce a do_lib_rust=true variable that will be defined only in debian.master/rules.d/amd64.mk for now. [Regression potential] Kernels may need to set this variables if they want to enable the Rust support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021569] Re: [aarch64] Please help to enable CONFIG_REGULATOR_MT6359
However, CONFIG_REGULATOR_MT6359 seems need to be assigned as built-in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021569 Title: [aarch64] Please help to enable CONFIG_REGULATOR_MT6359 Status in linux-meta package in Ubuntu: New Bug description: Please help to enable CONFIG_REGULATOR_MT6359 for [aarch64] The CONFIG_REGULATOR_MT6359 option is required for MediaTek's MT8195/MT8390. This is the maintatory PMIC for MT8195/MT8390. It is currently disabled in the Mantic, Lunar. and Kinetic -generic kernel. While it is enabled in the arm-generic kernel: https://elixir.bootlin.com/linux/v5.19/source/arch/arm64/configs/defconfig#L658 https://elixir.bootlin.com/linux/latest/source/arch/arm64/configs/defconfig#L689 Please help to enable CONFIG_REGULATOR_MT6359 and related settings CONFIG_REGULATOR_MT6359=y (or m) CONFIG_SND_SOC_MT6359=m CONFIG_SND_SOC_MT6359_ACCDET=m The same goes for Mantic, Lunar. Kinetic. Thanks Macpaul Lin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
SRU: https://lists.ubuntu.com/archives/kernel-team/2023-May/139828.html (lunar) ** Description changed: + [SRU Justfication] + + [Impact] + + On AMD Phoenix platforms, system may hang, or reboot while resuming from + suspend. + + [Fix] + + Two patches in v6.4-rc3 for amdgpu. The first one is pulled for + dependency. + + [Test Case] + + $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto + $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 + $ checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots + + [Where problems could occur] + + The fix is to safely guard register access as it should be. No potential + problem identified so far. + + [Other Info] + + This should affects v6.1 or above as which AMD Phoenix are supported, + and has been included in mantic-6.3 through stable-6.3.4 and in oem-6.1 + through stable-6.1.30, leaving lunar-6.2 unfixed only. + + == original bug report == + To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1277 F pulseaudio - /dev/snd/controlC1: ubuntu 1277 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1277 F pulseaudio + /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-stella-jammy-amd64-20230421-366 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-6.1.0-1014-oem N/A - linux-backports-modules-6.1.0-1014-oem N/A - linux-firmware 20220329.git681281e4-0ubuntu3.13 + linux-restricted-modules-6.1.0-1014-oem N/A + linux-backports-modules-6.1.0-1014-oem N/A + linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in
[Kernel-packages] [Bug 2021563] 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 2021563 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Incomplete Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro To manage notifications about this bug go to:
[Kernel-packages] [Bug 2021563] Re: Unknown kernel command line parameters
There is no 'kernel-package' in recent releases of Ubuntu so moving to 'linux'. ** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) ** Tags added: jammy kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021563 Title: Unknown kernel command line parameters Status in linux package in Ubuntu: Incomplete Bug description: oot@prod:/home/bernie22# journalctl -b |grep lockdown Mai 30 08:25:44 prod kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 initcall_blacklist=serial8250_init Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters "security_lockdown_lsm_early noplymouth BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space. Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015956] Re: selftest: fib_tests: Always cleanup before exit
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2015956 Title: selftest: fib_tests: Always cleanup before exit Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Copied from the commit message: Usage of `set -e` before executing a command causes immediate exit on failure, without cleanup up the resources allocated at setup. This can affect the next tests that use the same resources, leading to a chain of failures. A simple fix is to always call cleanup function when the script exists. This approach is already used by other existing tests. [Fix] * b60417a9f2 selftest: fib_tests: Always cleanup before exit This patch can be cherry-picked into affected kernels. [Test] Run the patched fib_tests.sh on KVM kernels, which is expected to fail due to bug 2007458. Check with `ip netns`, the ns1 added during setup() should be removed. [Where problems could occur] Test robustness improvement, this should not break things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
the platform that needs this already moved to 6.1, so closing for 6.0 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021572] [NEW] dGPU cannot resume because system firmware stuck in IPCS method
Public bug reported: [Impact] When a dGPU on a laptop is in PCIe D3cold and TBT port is connected to a monitor via a cable, unplugging the cable will make the dGPU unable to resume to D0. [Fix] There's a part of system firmware, IOM, need the driver to disconnect all TBT/Type-C phy to let dGPU function normally. [Test] With the fix applied, the dGPU continues to work after replugging video cable many times. [Where problems could occur] The fix is composed of several overhaul, so it's likely to regression i915 GFX driver. To limit the impact, only target OEM kernel for now. ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: High Status: Confirmed ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2021572 Title: dGPU cannot resume because system firmware stuck in IPCS method Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: [Impact] When a dGPU on a laptop is in PCIe D3cold and TBT port is connected to a monitor via a cable, unplugging the cable will make the dGPU unable to resume to D0. [Fix] There's a part of system firmware, IOM, need the driver to disconnect all TBT/Type-C phy to let dGPU function normally. [Test] With the fix applied, the dGPU continues to work after replugging video cable many times. [Where problems could occur] The fix is composed of several overhaul, so it's likely to regression i915 GFX driver. To limit the impact, only target OEM kernel for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2021572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021571] [NEW] cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
Public bug reported: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Description changed: Issue: ```console - # time cat /sys/fs/cgroup/blkio/blkio.time_recursive + # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux + + + Would be appreciated to know any operations to identify the issue, Thank you very much for the help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: New Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020062] Re: No HDMI/DP audio output on dock(Nvidia GPU)
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2020062
Title:
No HDMI/DP audio output on dock(Nvidia GPU)
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Impact]
When the machine is docked with an external monitor, it is able to output
display, but the HDMI/DP audio output option is lost in DGFF Hybrid
Discrete/Discrete mode(Nvidia GPU).
[Fix]
Nvidia provides a patch to fix it
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/
[Test]
Verified on the target machine.
{Where problems could occur]
The patch just adds IDs, and won't lead to any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020062/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020656] Re: system freeze (cpu fan goes high)
modifying the kernel command line this way (adding amdgpu.dcdebugmask=0x10) GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dcdebugmask=0x10" seems to give huge improvement $> uptime -p up 1 day, 14 hours, 31 minutes NEW RECORD -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2020656 Title: system freeze (cpu fan goes high) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: More than once a day the system totally freeze. CPU fan then goes higher and higher. Does not seem to be related to system load as yesterday it happend during lunch break. Today's journalctl -b -1 last message is mai 24 11:50:06 ThinkPad-P14s kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 167s! [opt ax7ixzwwoey:158586] There are many more of the same kind just before $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-image-5.19.0-42-generic linux-image-5.19.0-42-generic: Installé : 5.19.0-42.43~22.04.1 Candidat : 5.19.0-42.43~22.04.1 Table de version : *** 5.19.0-42.43~22.04.1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status Note this problem was present before last kernel updates ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-42-generic 5.19.0-42.43~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 24 12:00:08 2023 InstallationDate: Installed on 2023-03-25 (59 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017444] Re: Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
** Changed in: linux (Ubuntu)
Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2017444
Title:
Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux source package in Lunar:
Fix Committed
Status in linux-firmware source package in Lunar:
Invalid
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 (maintainer:STAGING - ATOMISP DRIVER)
Mauro Carvalho Chehab (maintainer:STAGING - ATOMISP
DRIVER)
Sakari Ailus (reviewer:STAGING - ATOMISP
DRIVER)
Greg Kroah-Hartman (supporter:STAGING SUBSYSTEM)
linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
linux-ker...@vger.kernel.org (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://www.mail-archive.com/kernel-
packa...@lists.launchpad.net/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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017444/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021569] [NEW] [aarch64] Please help to enable CONFIG_REGULATOR_MT6359
Public bug reported: Please help to enable CONFIG_REGULATOR_MT6359 for [aarch64] The CONFIG_REGULATOR_MT6359 option is required for MediaTek's MT8195/MT8390. This is the maintatory PMIC for MT8195/MT8390. It is currently disabled in the Mantic, Lunar. and Kinetic -generic kernel. While it is enabled in the arm-generic kernel: https://elixir.bootlin.com/linux/v5.19/source/arch/arm64/configs/defconfig#L658 https://elixir.bootlin.com/linux/latest/source/arch/arm64/configs/defconfig#L689 Please help to enable CONFIG_REGULATOR_MT6359 and related settings CONFIG_REGULATOR_MT6359=y (or m) CONFIG_SND_SOC_MT6359=m CONFIG_SND_SOC_MT6359_ACCDET=m The same goes for Mantic, Lunar. Kinetic. Thanks Macpaul Lin ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021569 Title: [aarch64] Please help to enable CONFIG_REGULATOR_MT6359 Status in linux-meta package in Ubuntu: New Bug description: Please help to enable CONFIG_REGULATOR_MT6359 for [aarch64] The CONFIG_REGULATOR_MT6359 option is required for MediaTek's MT8195/MT8390. This is the maintatory PMIC for MT8195/MT8390. It is currently disabled in the Mantic, Lunar. and Kinetic -generic kernel. While it is enabled in the arm-generic kernel: https://elixir.bootlin.com/linux/v5.19/source/arch/arm64/configs/defconfig#L658 https://elixir.bootlin.com/linux/latest/source/arch/arm64/configs/defconfig#L689 Please help to enable CONFIG_REGULATOR_MT6359 and related settings CONFIG_REGULATOR_MT6359=y (or m) CONFIG_SND_SOC_MT6359=m CONFIG_SND_SOC_MT6359_ACCDET=m The same goes for Mantic, Lunar. Kinetic. Thanks Macpaul Lin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
In Ubuntu-6.3.0-5.5. ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
Committed as v6.1.30 merged into oem-6.1-next. See http://10.131.201.69/kernel/jammy-linux-oem/pulls/5. ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676511/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676512/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676510/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676509/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676508/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676507/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676506/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676504/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676505/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676502/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676501/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676500/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2020685/+attachment/5676503/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
