[Kernel-packages] [Bug 1898633] Re: timer_settime01 from ubuntu_ltp_syscalls failed on bionic /aws-4.15 on c5.metal
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-syscalls -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1898633 Title: timer_settime01 from ubuntu_ltp_syscalls failed on bionic /aws-4.15 on c5.metal Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Invalid Bug description: 21367.09/25 08:38:06 DEBUG| utils:0153| [stdout] startup='Fri Sep 25 08:37:00 2020' 21368.09/25 08:38:06 DEBUG| utils:0153| [stdout] tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s 21369.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:85: TINFO: Testing variant: syscall with old kernel spec 21370.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:96: TINFO: Testing for general initialization: 21371.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME) passed 21372.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_MONOTONIC) passed 21373.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_PROCESS_CPUTIME_ID) passed 21374.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_THREAD_CPUTIME_ID) passed 21375.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME) passed 21376.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME_ALARM) passed 21377.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME_ALARM) passed 21378.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_TAI) passed 21379.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:96: TINFO: Testing for setting old_value: 21380.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME) passed 21381.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_MONOTONIC) passed 21382.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_PROCESS_CPUTIME_ID) passed 21383.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_THREAD_CPUTIME_ID) passed 21384.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME) passed 21385.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME_ALARM) passed 21386.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME_ALARM) passed 21387.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_TAI) passed 21388.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:96: TINFO: Testing for using periodic timer: 21389.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME) passed 21390.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_MONOTONIC) passed 21391.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_PROCESS_CPUTIME_ID) passed 21392.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_THREAD_CPUTIME_ID) passed 21393.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME) passed 21394.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME_ALARM) passed 21395.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME_ALARM) passed 21396.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_TAI) passed 21397.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:96: TINFO: Testing for using absolute time: 21398.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME) passed 21399.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:160: TFAIL: timer_gettime(CLOCK_MONOTONIC) reported bad values (0: 5034): SUCCESS (0) 21400.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_MONOTONIC) passed 21401.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS:
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-cve -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux-ibm source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-ibm source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-ibm source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-ibm source package in Impish: Won't Fix Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs
[Kernel-packages] [Bug 1848473] Re: cgroup_fj_stress_* in controllers from ubuntu_ltp failed with dir creation / fork on B-KVM
I didn't see this issue in recent B-kvm and I didn't see this failure on the only hinted f-aws. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1848473 Title: cgroup_fj_stress_* in controllers from ubuntu_ltp failed with dir creation / fork on B-KVM Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Invalid Bug description: It looks like the test failed with cannot fork, and the following test will failed with mkdir. Take this one for example: tag=cgroup_fj_stress_perf_event_2_9_each stime=1571098406 dur=7 exit=exited stat=2 core=no cu=451 cs=280 ... ... cgroup_fj_stress_perf_event_2_9_each 1 TINFO: Attaching task 1326 to /sys/fs/cgroup/perf_event/ltp/2/1/1/2/1/2/1 cgroup_fj_stress_perf_event_2_9_each 1 TINFO: Attaching task 1329 to /sys/fs/cgroup/perf_event/ltp/2/1/1/2/1/2/1/1 /opt/ltp/testcases/bin/cgroup_fj_stress.sh: 53: /opt/ltp/testcases/bin/cgroup_fj_stress.sh: Cannot fork tag=cgroup_fj_stress_perf_event_10_3_each stime=1571098419 dur=2 exit=exited stat=2 core=no cu=134 cs=84 startup='Tue Oct 15 00:13:39 2019' cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Subsystem perf_event is mounted at /sys/fs/cgroup/perf_event cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Creating subgroups ... mkdir: cannot create directory ‘/sys/fs/cgroup/perf_event/ltp’: File exists cgroup_fj_stress_perf_event_10_3_each 1 TBROK: mkdir /sys/fs/cgroup/perf_event/ltp failed cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Removing all ltp subgroups... Failed test cases sorted alphabetically: cgroup_fj_stress_blkio_10_3_each-mkdir cgroup_fj_stress_blkio_2_9_each -cannot fork cgroup_fj_stress_cpu_10_3_each -mkdir cgroup_fj_stress_cpu_2_9_each -cannot fork cgroup_fj_stress_cpuacct_10_3_each -mkdir cgroup_fj_stress_cpuacct_2_9_each -cannot fork cgroup_fj_stress_cpuset_10_3_each -mkdir cgroup_fj_stress_cpuset_2_9_each-cannot fork cgroup_fj_stress_devices_10_3_each -mkdir cgroup_fj_stress_devices_2_9_each -cannot fork cgroup_fj_stress_freezer_10_3_each -mkdir cgroup_fj_stress_freezer_2_9_each -cannot fork cgroup_fj_stress_hugetlb_10_3_each -mkdir cgroup_fj_stress_hugetlb_2_9_each -cannot fork cgroup_fj_stress_memory_10_3_each -mkdir cgroup_fj_stress_memory_2_9_each-cannot fork cgroup_fj_stress_net_cls_10_3_each -mkdir cgroup_fj_stress_net_cls_2_9_each -cannot fork cgroup_fj_stress_net_prio_10_3_each -mkdir cgroup_fj_stress_net_prio_2_9_each -cannot fork cgroup_fj_stress_perf_event_10_3_each -mkdir cgroup_fj_stress_perf_event_2_9_each-cannot fork To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848473/+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 2046940] [NEW] package linux-nvidia-6.2-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-comm
Public bug reported: I was just using my OS and this problem emerged on its own. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-nvidia-6.2-tools-common (not installed) ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-nvidia-6.2-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Dec 18 14:43:27 2023 DpkgTerminalLog: Preparing to unpack .../linux-nvidia-6.2-tools-common_6.2.0-1003.3~22.04.1_all.deb ... Unpacking linux-nvidia-6.2-tools-common (6.2.0-1003.3~22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-nvidia-6.2-tools-common_6.2.0-1003.3~22.04.1_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 InstallationDate: Installed on 2023-07-23 (149 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-nvidia-6.2 Title: package linux-nvidia-6.2-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046940 Title: package linux-nvidia-6.2-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: I was just using my OS and this problem emerged on its own. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-nvidia-6.2-tools-common (not installed) ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-nvidia-6.2-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Dec 18 14:43:27 2023 DpkgTerminalLog: Preparing to unpack .../linux-nvidia-6.2-tools-common_6.2.0-1003.3~22.04.1_all.deb ... Unpacking linux-nvidia-6.2-tools-common (6.2.0-1003.3~22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-nvidia-6.2-tools-common_6.2.0-1003.3~22.04.1_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 InstallationDate: Installed on 2023-07-23 (149 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-nvidia-6.2 Title: package linux-nvidia-6.2-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-91.101 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2046940/+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 2045387] Re: Add ODM driver f81604 usb-can
** Tags added: patch -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 1943627] Re: Controllers test in ubuntu_ltp fails to mount on /dev/cpuctl
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- 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/1943627 Title: Controllers test in ubuntu_ltp fails to mount on /dev/cpuctl Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Found on Focal linux-gcp 5.11.0-1019.21 on g1-small instance. The tests are not able to mount on /dev/cpuctl which is causing cpu controller testing, latency tests, and cpuctl_test_fj to fail, seems to be only on g1-small instances. This error has been observed in previous cycles and is not a new regression. 20:09:23 DEBUG| [stdout] startup='Mon Sep 13 20:07:02 2021' 20:09:23 DEBUG| [stdout] TEST 1: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 3: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 4: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 5: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 97: /opt/ltp/output/cpuctl_results_stress-678.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 6: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 7: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 8: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 120: /opt/ltp/output/cpuctl_results_stress-9.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 9: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 127: /opt/ltp/output/cpuctl_results_stress-10.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 10: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TINFO Running cpuctl Latency Test 1 20:09:23 DEBUG| [stdout] TINFOThe latency check task started 20:09:23 DEBUG| [stdout] FAIL The Latency test 1 failed 20:09:23 DEBUG| [stdout] Max latency observed = 123838 in Iteration 0 20:09:23 DEBUG| [stdout] The results FAIL is just intuitive and not exact failure. Please look at cpuctl_testplan.txt in the test directory. 20:09:23 DEBUG| [stdout] Task 763103 exited abnormally with return value: 1 20:09:23 DEBUG| [stdout] TBROK Test could'nt execute for expected duration 20:09:23 DEBUG| [stdout] Doing cleanup 20:09:23 DEBUG| [stdout] Cleanup done for latency test 1 20:09:23 DEBUG|
[Kernel-packages] [Bug 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
This series conflict with below SRU for Noble, so will no submit Noble SRU until below SRU has been included https://lists.ubuntu.com/archives/kernel-team/2023-December/147538.html ** Changed in: linux (Ubuntu Mantic) 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.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] Run `iw list` should see the available frequency above 6Ghz, even it's disabled Frequencies: ... * 6835 MHz [177] (disabled) * 6855 MHz [181] (disabled) * 6875 MHz [185] (disabled) * 6895 MHz [189] (disabled) * 6915 MHz [193] (disabled) * 6935 MHz [197] (disabled) * 6955 MHz [201] (disabled) * 6975 MHz [205] (disabled) * 6995 MHz [209] (disabled) * 7015 MHz [213] (disabled) * 7035 MHz [217] (disabled) * 7055 MHz [221] (disabled) * 7075 MHz [225] (disabled) * 7095 MHz [229] (disabled) * 7115 MHz [233] (disabled) [Where problems could occur] Should have some impact to current RTL devices, but didn't see any fix patches for the 3 commits now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045622/+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 2046986] [NEW] i915 GuC hang, "engine reset failed"
Public bug reported:
According to intel/freedesktop dot org's submission guidelines, the
Mantic kernel is something that they don't want to hear about, "report
it to your distro instead". Attached is a zip with the /sys dump data
that intel would want, if they wanted it. Lunar had several of these GuC
hangs, I believe this is the first time that Mantic gave me one.
At the time, my laptop was attached to a Steam Deck Dock (on current
stable firmware), connected to an Acer monitor via DP. I had just
fullscreened a promotional video in the Steam client, it animated ~90%
of the way to a fullscreen video window when all the graphics froze.
This crash doesn't seem to be reproducable. Audio was still playing
through the video hang, and I was able to ssh into the laptop to collect
the attached /sys data.
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] *ERROR* GT0: GUC:
Engine reset failed on 0:0 (rcs0) because 0x00
00
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] GPU HANG: ecode
12:1:84db, in steamwebhelper [316201]
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] Resetting chip for GuC
failed to reset engine mask=0x1
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] *ERROR* rcs0 reset
request timed out: {request: 0001, RESET_
CTL: 0001}
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] *ERROR* rcs0 reset
request timed out: {request: 0001, RESET_
CTL: 0001}
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] steamwebhelper[316201]
context reset due to GPU hang
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] GT0: GuC firmware
i915/adlp_guc_70.bin version 70.5.1
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] GT0: HuC firmware
i915/tgl_huc.bin version 7.9.3
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] GT0: HuC:
authenticated for all workloads
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] GT0: GUC: submission
enabled
Dec 19 20:30:08 zenbook kernel: i915 :00:02.0: [drm] GT0: GUC: SLPC enabled
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 2373 F pipewire
user 2378 F wireplumber
/dev/snd/seq:user 2373 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 19 21:31:24 2023
InstallationDate: Installed on 2023-05-20 (214 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no username)
SHELL=/usr/bin/fish
TERM=tmux-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: root=UUID=9d399706-0188-4c6e-afbd-575e498f5889 ro
rootflags=subvol=@ quiet splash
resume=UUID=64f06803-7591-471e-a985-ef7bd9c4e54d vt.handoff=7
initrd=boot\initrd.img-6.5.0-14-generic
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-15 (65 days ago)
dmi.bios.date: 08/18/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX3404VA.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX3404VA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag:
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.3
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3404VA.303:bd08/18/2023:br5.27:efr3.3:svnASUSTeKCOMPUTERINC.:pnZenbookUX3404VA_Q420VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3404VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook UX3404VA_Q420VA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
** Attachment added: "some GuC related dump files from /sys/class/drm/card0 &
gt0/uc/"
https://bugs.launchpad.net/bugs/2046986/+attachment/5730847/+files/guc_crash.zip
** Description changed:
According to intel/freedesktop dot org's submission guidelines, the
Mantic kernel is something that they don't want to hear about, "report
it to your distro instead". Attached is a zip with the /sys dump data
that intel would want, if they wanted it. Lunar had several of these GuC
hangs, I believe this is the first time that Mantic gave me one.
At the time, my laptop was attached to a Steam Deck Dock (on current
stable firmware), connected to an Acer monitor via DP. I
[Kernel-packages] [Bug 814489] Re: package bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug is no longer a duplicate of bug 881028 package initramfs-tools 0.99ubuntu8 failed to install/upgrade: due to a full filesystem ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/814489 Title: package bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bcmwl package in Ubuntu: Confirmed Bug description: Upgrading system from USB stick -ubuntu natty ProblemType: Package DistroRelease: Ubuntu 11.04 Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Fri Jul 22 11:01:10 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/814489/+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 1853798] Re: umip_basic_test in kernel_misc from ubuntu_ltp failed on D-Oracle / B-oracle-4.15
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-kernel-misc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1853798 Title: umip_basic_test in kernel_misc from ubuntu_ltp failed on D-Oracle / B-oracle-4.15 Status in ubuntu-kernel-tests: New Status in linux-signed-oracle package in Ubuntu: New Bug description: <<>> tag=umip_basic_test stime=1574662675 cmdline="umip_basic_test" contacts="" analysis=exit <<>> tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1005-oracle' incrementing stop tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s umip_basic_test.c:158: INFO: cpuinfo contains umip, CPU supports umip umip_basic_test.c:40: INFO: TEST sgdt, sgdt result save at [0x7ffdd514086e] umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4 umip_basic_test.c:135: PASS: Got SIGSEGV umip_basic_test.c:50: INFO: TEST sidt, sidt result save at [0x7ffdd514086e] umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4 umip_basic_test.c:135: PASS: Got SIGSEGV umip_basic_test.c:59: INFO: TEST sldt, sldt result save at [0x7ffdd5140860] umip_basic_test.c:135: PASS: Got SIGSEGV umip_basic_test.c:68: INFO: TEST smsw, smsw result save at [0x7ffdd5140860] umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4 umip_basic_test.c:139: FAIL: Didn't receive SIGSEGV, child exited with exited with 0 umip_basic_test.c:77: INFO: TEST str, str result save at [0x7ffdd5140860] umip_basic_test.c:135: PASS: Got SIGSEGV Summary: passed 4 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9 ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21 Uname: Linux 5.0.0-1005-oracle x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Nov 25 06:18:04 2019 SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853798/+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 2045385] Re: Add ODM driver rtc-pcf85263
** Tags added: patch -- 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2045386] Re: Add ODM driver gpio-m058ssan
** Tags added: patch -- 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/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+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 1947016] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux-realtime
** Tags removed: ubuntu-kernel-selftests ubuntu-ltp ** Tags added: ubuntu-ltp-kernel-misc -- 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/1947016 Title: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux- realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Jammy: Confirmed Bug description: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux- realtime 5.11.0-27.28 on amd64 nodes. This test seems to be flaky as it doesn't fail consistently. 07:34:27 DEBUG| [stdout] startup='Tue Oct 12 07:21:09 2021' 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : found 'intel_pstate' driver, sysfs knob '/sys/devices/system/cpu/intel_pstate/no_turbo' 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : maximum speed is 300 KHz 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost enabled 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 1588 ms 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost disabled 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 1543 ms 07:34:27 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189: compare time spent with and without boost (-2%) 07:34:27 DEBUG| [stdout] tag=cpufreq_boost stime=1634023269 dur=4 exit=exited stat=1 core=no cu=303 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1947016/+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 1943732] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-kernel-misc -- 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/1943732 Title: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: Testcase cpufreq_boost from ubuntu_ltp.kernel_misc failed with focal/linux 5.4.0-85.95 on the P9 node baltar. 13:50:50 DEBUG| [stdout] startup='Wed Sep 8 13:42:39 2021' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : found 'acpi_cpufreq' driver, sysfs knob '/sys /devices/system/cpu/cpufreq/boost' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : maximum speed is 380 KHz 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost enabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2006 ms 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost disabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2027 ms 13:50:50 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189: compare time spent with and without boost (-2%) 13:50:50 DEBUG| [stdout] tag=cpufreq_boost stime=1631108559 dur=4 exit=exited stat=1 core=no cu=404 cs=2 This is not a regression as it has been failing since older versions (at least since 5.4.0-75.84). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943732/+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 2046981] [NEW] kvm kernel missing nvme block support
Public bug reported: The KVM flavour kernel is missing NVMe block support. This means one can't boot the minimal cloud images off an (emulated) nvme drive (as supported in qemu and other VMMs). root@ubuntu:~# modprobe nvme modprobe: FATAL: Module nvme not found in directory /lib/modules/5.15.0-1048-kvm Seems like CONFIG_BLK_DEV_NVME should be set, compare linux-kvm vs linux-gcp: debian.kvm/config/amd64/config.flavour.kvm: ... # # NVME Support # CONFIG_NVME_CORE=m # CONFIG_BLK_DEV_NVME is not set CONFIG_NVME_MULTIPATH=y CONFIG_NVME_FABRICS=m # CONFIG_NVME_FC is not set CONFIG_NVME_TCP=m # CONFIG_NVME_TARGET is not set # end of NVME Support ... debian.gcp/config/amd64/config.flavour.gcp: ... # NVME Support # CONFIG_NVME_CORE=y CONFIG_BLK_DEV_NVME=y CONFIG_NVME_MULTIPATH=y CONFIG_NVME_FABRICS=m CONFIG_NVME_RDMA=m CONFIG_NVME_FC=m CONFIG_NVME_TCP=m CONFIG_NVME_TARGET=m CONFIG_NVME_TARGET_LOOP=m CONFIG_NVME_TARGET_RDMA=m CONFIG_NVME_TARGET_FC=m # CONFIG_NVME_TARGET_FCLOOP is not set CONFIG_NVME_TARGET_TCP=m # end of NVME Support ... root@ubuntu:~# uname -a Linux ubuntu 5.15.0-1048-kvm #53-Ubuntu SMP Sun Nov 19 15:56:32 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# apt-cache policy linux-kvm linux-kvm: Installed: 5.15.0.1048.44 Candidate: 5.15.0.1048.44 Version table: *** 5.15.0.1048.44 100 100 /var/lib/dpkg/status root@ubuntu:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2046981 Title: kvm kernel missing nvme block support Status in linux-kvm package in Ubuntu: New Bug description: The KVM flavour kernel is missing NVMe block support. This means one can't boot the minimal cloud images off an (emulated) nvme drive (as supported in qemu and other VMMs). root@ubuntu:~# modprobe nvme modprobe: FATAL: Module nvme not found in directory /lib/modules/5.15.0-1048-kvm Seems like CONFIG_BLK_DEV_NVME should be set, compare linux-kvm vs linux-gcp: debian.kvm/config/amd64/config.flavour.kvm: ... # # NVME Support # CONFIG_NVME_CORE=m # CONFIG_BLK_DEV_NVME is not set CONFIG_NVME_MULTIPATH=y CONFIG_NVME_FABRICS=m # CONFIG_NVME_FC is not set CONFIG_NVME_TCP=m # CONFIG_NVME_TARGET is not set # end of NVME Support ... debian.gcp/config/amd64/config.flavour.gcp: ... # NVME Support # CONFIG_NVME_CORE=y CONFIG_BLK_DEV_NVME=y CONFIG_NVME_MULTIPATH=y CONFIG_NVME_FABRICS=m CONFIG_NVME_RDMA=m CONFIG_NVME_FC=m CONFIG_NVME_TCP=m CONFIG_NVME_TARGET=m CONFIG_NVME_TARGET_LOOP=m CONFIG_NVME_TARGET_RDMA=m CONFIG_NVME_TARGET_FC=m # CONFIG_NVME_TARGET_FCLOOP is not set CONFIG_NVME_TARGET_TCP=m # end of NVME Support ... root@ubuntu:~# uname -a Linux ubuntu 5.15.0-1048-kvm #53-Ubuntu SMP Sun Nov 19 15:56:32 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# apt-cache policy linux-kvm linux-kvm: Installed: 5.15.0.1048.44 Candidate: 5.15.0.1048.44 Version table: *** 5.15.0.1048.44 100 100 /var/lib/dpkg/status root@ubuntu:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2046981/+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 1942935] Re: kernel io hangs during mdcheck/resync
Linux version 6.4.12-200.fc38.x86_64 (mockbuild@30894952d3244f1ab967aeda9ed417f6) (gcc (GCC) 13.2.1 20230728 (Red Hat 13.2.1-1), GNU ld version 2.39-9.fc38) #1 SMP PREEMPT_DYNAMIC Wed Aug 23 17:46:49 UTC 2023 230 ?I< 0:00 \_ [md] 1377 ?S 6:15 \_ [md0_raid1] 1565 ?D4955:37 \_ [md4_raid6] 2772538 ?DN 111:11 \_ [md4_resync] # cat /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] md0 : active raid1 sde2[0] 13671170048 blocks super 1.2 [1/1] [U] bitmap: 1/102 pages [4KB], 65536KB chunk md4 : active raid6 sdd1[2] sdb1[5] sde1[4] sdc1[1] 11720779776 blocks super 1.2 level 6, 512k chunk, algorithm 2 [4/4] [] [=>...] check = 89.0% (5217054876/5860389888) finish=852549.6min speed=12K/sec bitmap: 9/44 pages [36KB], 65536KB chunk unused devices: # cat /proc/2772538/stack # md4_resync [<0>] raid5_get_active_stripe+0x271/0x540 [raid456] [<0>] raid5_sync_request+0x3ad/0x3d0 [raid456] [<0>] md_do_sync+0x7be/0x11c0 [<0>] md_thread+0xae/0x190 [<0>] kthread+0xe8/0x120 [<0>] ret_from_fork+0x2c/0x50 # cat /proc/1565/stack # md4_raid6 [<0>] raid5d+0x524/0x750 [raid456] [<0>] md_thread+0xae/0x190 [<0>] kthread+0xe8/0x120 [<0>] ret_from_fork+0x2c/0x50 Workarounded by: # cat /sys/block/md4/md/array_state write-pending # echo active > /sys/block/md4/md/array_state # cat /sys/block/md4/md/array_state active -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP:
[Kernel-packages] [Bug 1895426] Re: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Do you still experience that error? Can you reproduce it? ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Incomplete -- 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/1895426 Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Invalid Bug description: linux-firmware bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tirtha 1397 F pulseaudio CasperMD5CheckResult: skip Date: Sun Sep 13 11:45:12 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=a24d343d-9753-4460-ac8f-43882d4197c7 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.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895426/+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 2046985] Re: Add ODM driver rtc-pcf85263
** Tags added: originate-from-2039779 -- 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/2046985 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046985/+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 1942612] Re: cve-2017-7616 in cve from ubuntu_ltp failed on bionic with linux/linux-hwe-5.4 on i386
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-cve -- 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/1942612 Title: cve-2017-7616 in cve from ubuntu_ltp failed on bionic with linux/linux-hwe-5.4 on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Bug description: ubuntu_ltp.cve cve-2017-7616 testcase output: 16:10:41 DEBUG| [stdout] startup='Sun Aug 29 15:53:35 2021' 16:10:41 DEBUG| [stdout] tst_test.c:1346: TINFO: Timeout per run is 0h 05m 00s 16:10:41 DEBUG| [stdout] set_mempolicy05.c:66: TINFO: stack pattern is in 0xbf996ccc-0xbf9970cc 16:10:41 DEBUG| [stdout] set_mempolicy05.c:111: TFAIL: set_mempolicy should fail with EFAULT or EINVAL, instead returned 38 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cf01fb9985e8 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] HINT: You _MAY_ be vulnerable to CVE(s), see: 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-CVE-2017-7616 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] Summary: 16:10:41 DEBUG| [stdout] passed 0 16:10:41 DEBUG| [stdout] failed 1 16:10:41 DEBUG| [stdout] broken 0 16:10:41 DEBUG| [stdout] skipped 0 16:10:41 DEBUG| [stdout] warnings 0 16:10:41 DEBUG| [stdout] tag=cve-2017-7616 stime=1630252415 dur=0 exit=exited stat=1 core=no cu=0 cs=0 This is not a regression as this is a new testcase which runs only on 32-bit systems (i386 and powerpc). This test was added by ltp commit 6feed808040a86c54b7ab2dd3839fefd819a42cc (Add set_mempolicy05, CVE-2017-7616). The commit sha1 (cf01fb9985e8deb25ccf0ea54d916b8871ae0e62 - mm/mempolicy.c: fix error handling in set_mempolicy and mbind.) which fixes this CVE according to https://ubuntu.com/security/CVE-2017-7616, was applied upstream for v4.11-rc6, so both focal/linux and bionic/linux supposedly contain the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1942612/+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 1839143] Re: cve test from ubuntu_ltp will failed to fork on B-KVM
We have test split out to ubuntu-ltp-cve, and this issue does not exist anymore. ** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-cve ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839143 Title: cve test from ubuntu_ltp will failed to fork on B-KVM Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Bug description: Not sure if this has something to do with another timeout issue in controller test, the test will not get started at all: 08/06 06:14:10 INFO |ubuntu_ltp:0088| Checking virt-what to see if we need to set LTP_TIMEOUT_MUL for memcg_test_3... 08/06 06:14:10 INFO |ubuntu_ltp:0091| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL>1 (lp:1836694) for memcg_test_3 08/06 06:29:32 ERROR| test:0414| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 830, in _call_test_function raise error.UnhandledTestFail(e) UnhandledTestFail: Unhandled OSError: [Errno 11] Resource temporarily unavailable Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ltp/ubuntu_ltp.py", line 103, in run_once utils.run(cmd, ignore_status=True, verbose=False) File "/home/ubuntu/autotest/client/shared/utils.py", line 914, in run stderr_level=get_stderr_level(stderr_is_expected)),), File "/home/ubuntu/autotest/client/shared/utils.py", line 128, in __init__ stdin=stdin) File "/usr/lib/python2.7/subprocess.py", line 394, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 938, in _execute_child self.pid = os.fork() OSError: [Errno 11] Resource temporarily unavailable ~ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1039-kvm 4.15.0-1039.39 ProcVersionSignature: User Name 4.15.0-1039.39-kvm 4.15.18 Uname: Linux 4.15.0-1039-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Tue Aug 6 11:51:21 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839143/+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 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
** Description changed: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] - Run `iw list` should see something like below + Run `iw list` should see the available frequency above 6Ghz, even it's disabled Frequencies: - * 5955 MHz [1] (22.0 dBm) (no IR) - * 5975 MHz [5] (22.0 dBm) (no IR) - * 5995 MHz [9] (22.0 dBm) (no IR) - * 6015 MHz [13] (22.0 dBm) (no IR) - * 6035 MHz [17] (22.0 dBm) (no IR) - * 6055 MHz [21] (22.0 dBm) (no IR) - * 6075 MHz [25] (22.0 dBm) (no IR) - * 6095 MHz [29] (22.0 dBm) (no IR) - * 6115 MHz [33] (22.0 dBm) (no IR) - * 6135 MHz [37] (22.0 dBm) (no IR) - * 6155 MHz [41] (22.0 dBm) (no IR) - * 6175 MHz [45] (22.0 dBm) (no IR) - * 6195 MHz [49] (22.0 dBm) (no IR) - * 6215 MHz [53] (22.0 dBm) (no IR) - - And `iw reg get` shows the contry code read from BIOS and supported - freq, too - - phy#0 (self-managed) - country TW: DFS-UNSET - (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ - (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ - (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ - + ... + * 6835 MHz [177] (disabled) + * 6855 MHz [181] (disabled) + * 6875 MHz [185] (disabled) + * 6895 MHz [189] (disabled) + * 6915 MHz [193] (disabled) + * 6935 MHz [197] (disabled) + * 6955 MHz [201] (disabled) + * 6975 MHz [205] (disabled) + * 6995 MHz [209] (disabled) + * 7015 MHz [213] (disabled) + * 7035 MHz [217] (disabled) + * 7055 MHz [221] (disabled) + * 7075 MHz [225] (disabled) + * 7095 MHz [229] (disabled) + * 7115 MHz [233] (disabled) [Where problems could occur] + Should have some impact to current RTL devices, but didn't see any fix patches for the 3 commits now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] Run `iw list` should see the available frequency above 6Ghz, even it's disabled Frequencies: ... * 6835 MHz [177] (disabled) * 6855 MHz [181] (disabled) * 6875 MHz [185] (disabled) * 6895 MHz [189] (disabled) * 6915 MHz [193] (disabled) * 6935 MHz [197] (disabled) * 6955 MHz [201] (disabled) * 6975 MHz [205] (disabled) * 6995 MHz [209] (disabled) * 7015 MHz [213] (disabled) * 7035 MHz [217] (disabled) * 7055 MHz [221] (disabled) * 7075 MHz [225] (disabled)
[Kernel-packages] [Bug 2046985] [NEW] Add ODM driver rtc-pcf85263
Public bug reported: [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/2046985 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046985/+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 2046985] Re: Add ODM driver rtc-pcf85263
*** This bug is a duplicate of bug 2045385 *** https://bugs.launchpad.net/bugs/2045385 ** This bug has been marked a duplicate of private bug 2045385 -- 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/2046985 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046985/+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 2045385] Re: Add ODM driver rtc-pcf85263
** Information type changed from Private to Public ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress -- 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385/+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 2045387] Re: Add ODM driver f81604 usb-can
** Information type changed from Private to Public ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Tags added: erlin oem-priority originate-from-2039779 -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 2045386] Re: Add ODM driver gpio-m058ssan
** Information type changed from Private to Public ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Tags added: erlin oem-priority originate-from-2039779 -- 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/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+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 2045385] Re: Add ODM driver rtc-pcf85263
** Tags added: erlin oem-priority originate-from-2039779 -- 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@ivuser today I made a new install, deleting the old directoryes and files. Many messages are in italian, but as you can see The driver was created and installed correctly... (base) giuliano@Astra2A:~$ ./uvc_quanta.sh [sudo] password di giuliano: I seguenti pacchetti sono stati mantenuti alla versione attuale: gjs libgjs0g python3-update-manager update-manager update-manager-core 0 aggiornati, 0 installati, 0 da rimuovere e 5 non aggiornati. Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze... Fatto Lettura informazioni sullo stato... Fatto build-essential è già alla versione più recente (12.9ubuntu3). I seguenti pacchetti sono stati installati automaticamente e non sono più richiesti: libaccinj64-11.5 libcub-dev libcublas11 libcublaslt11 libcudart11.0 libcufft10 libcufftw10 libcupti-dev libcupti-doc libcupti11.5 libcurand10 libcusolver11 libcusolvermg11 libcusparse11 libgl1-mesa-dev libllvm13 libllvm13:i386 libnppc11 libnppial11 libnppicc11 libnppidei11 libnppif11 libnppig11 libnppim11 libnppist11 libnppisu11 libnppitc11 libnpps11 libnvblas11 libnvjpeg11 libnvrtc-builtins11.5 libnvrtc11.2 libnvtoolsext1 libnvvm4 liborcus-0.17-0 liborcus-parser-0.17-0 libtbb-dev libthrust-dev libvdpau-dev libwmf0.2-7 libxmlsec1 libxmlsec1-nss node-html5shiv nsight-compute nsight-compute-target nvidia-cuda-gdb nvidia-cuda-toolkit-doc nvidia-opencl-dev ocl-icd-opencl-dev opencl-c-headers opencl-clhpp-headers Usare "sudo apt autoremove" per rimuoverli. 0 aggiornati, 0 installati, 0 da rimuovere e 5 non aggiornati. Lettura elenco dei pacchetti... Fatto Scelto "linux-hwe-6.2" come pacchetto sorgente al posto di "linux-modules-extra-6.2.0-39-generic" Nota: il processo di pacchettizzazione di "linux-hwe-6.2" è mantenuto all'interno del sistema di controllo della versione "Git" presso: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy Utilizzare: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy per recuperare gli ultimi (forse non rilasciati) aggiornamenti del pacchetto. È necessario scaricare 229 MB di sorgenti. Scaricamento di:1 http://it.archive.ubuntu.com/ubuntu jammy-updates/main linux-hwe-6.2 6.2.0-39.40~22.04.1 (dsc) [8.838 B] Scaricamento di:2 http://it.archive.ubuntu.com/ubuntu jammy-updates/main linux-hwe-6.2 6.2.0-39.40~22.04.1 (tar) [219 MB] Scaricamento di:3 http://it.archive.ubuntu.com/ubuntu jammy-updates/main linux-hwe-6.2 6.2.0-39.40~22.04.1 (diff) [10,5 MB] Recuperati 229 MB in 13s (17,8 MB/s) dpkg-source: Informazioni: extracting linux-hwe-6.2 in linux-hwe-6.2-6.2.0 dpkg-source: Informazioni: unpacking linux-hwe-6.2_6.2.0.orig.tar.gz dpkg-source: Informazioni: applying linux-hwe-6.2_6.2.0-39.40~22.04.1.diff.gz patching file Documentation/ABI/testing/configfs-usb-gadget-uvc patching file Documentation/ABI/testing/ima_policy patching file Documentation/ABI/testing/sysfs-devices-system-cpu patching file Documentation/ABI/testing/sysfs-driver-eud patching file Documentation/ABI/testing/sysfs-module patching file Documentation/Makefile patching file Documentation/accounting/psi.rst patching file Documentation/admin-guide/cgroup-v1/memory.rst patching file Documentation/admin-guide/hw-vuln/gather_data_sampling.rst patching file Documentation/admin-guide/hw-vuln/index.rst patching file Documentation/admin-guide/hw-vuln/spectre.rst patching file Documentation/admin-guide/hw-vuln/srso.rst patching file Documentation/admin-guide/kdump/gdbmacros.txt patching file Documentation/admin-guide/kernel-parameters.rst patching file Documentation/admin-guide/kernel-parameters.txt patching file Documentation/admin-guide/security-bugs.rst patching file Documentation/admin-guide/sysctl/kernel.rst patching file Documentation/arm64/silicon-errata.rst patching file Documentation/bpf/instruction-set.rst patching file Documentation/cgroups/namespace.txt patching file Documentation/dev-tools/gdb-kernel-debugging.rst patching file Documentation/devicetree/bindings/ata/ceva,ahci-1v84.yaml patching file Documentation/devicetree/bindings/display/mediatek/mediatek,ccorr.yaml patching file Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml patching file Documentation/devicetree/bindings/iio/adc/renesas,rcar-gyroadc.yaml patching file Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml patching file Documentation/devicetree/bindings/power/reset/qcom,pon.yaml patching file Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt patching file Documentation/devicetree/bindings/serial/renesas,scif.yaml patching file Documentation/devicetree/bindings/sound/amlogic,gx-sound-card.yaml patching file Documentation/devicetree/bindings/sound/cirrus,cs35l41.yaml patching file
[Kernel-packages] [Bug 896646] Re: package b43-fwcutter (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug is no longer a duplicate of bug 881028 package initramfs-tools 0.99ubuntu8 failed to install/upgrade: due to a full filesystem ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/896646 Title: package b43-fwcutter (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in b43-fwcutter package in Ubuntu: New Bug description: Trying to intall 10.04 LTS on Apple Mac G5 that has OS X already on it. I wanted the OS X to be deleted and all the disk reserved for Ubuntu ProblemType: Package DistroRelease: Ubuntu 10.04 Package: b43-fwcutter (not installed) ProcVersionSignature: Ubuntu 2.6.32-21.32-powerpc64-smp 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-powerpc64-smp ppc64 AptOrdering: b43-fwcutter: Install b43-fwcutter: Configure Architecture: powerpc Date: Sat Nov 26 17:58:25 2011 ErrorMessage: subprocess new pre-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release powerpc (20100428) SourcePackage: b43-fwcutter Title: package b43-fwcutter (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/896646/+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 889552] Re: package linux-image-2.6.38-12-generic 2.6.38-12.51 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de err
*** This bug is a duplicate of bug 798414 ***
https://bugs.launchpad.net/bugs/798414
** This bug is no longer a duplicate of bug 881028
package initramfs-tools 0.99ubuntu8 failed to install/upgrade: due to a full
filesystem
** This bug has been marked a duplicate of bug 798414
update-initramfs should produce a more helpful error message when there
isn't enough free space--or provide an automatic tool for removal of old files
--
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/889552
Title:
package linux-image-2.6.38-12-generic 2.6.38-12.51 failed to
install/upgrade: el subproceso instalado el script post-installation
devolvió el código de salida de error 2
Status in linux package in Ubuntu:
Confirmed
Bug description:
none
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-12-generic 2.6.38-12.51
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC861-VD Analog [ALC861-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC861-VD Analog [ALC861-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
CRDA: Error: [Errno 2] No existe el fichero o el directorio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xde30 irq 46'
Mixer name : 'Realtek ALC861-VD'
Components : 'HDA:10ec0862,1179010c,0011
HDA:11c11040,11790001,00100200'
Controls : 16
Simple ctrls : 10
Date: Sat Nov 12 13:47:05 2011
ErrorMessage: el subproceso instalado el script post-installation devolvió el
código de salida de error 2
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: TOSHIBA Satellite A200
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/hostname.seed
boot=casper quiet splash -- persistent BOOT_IMAGE=/ubnkern
RelatedPackageVersions:
linux-restricted-modules-2.6.38-8-generic N/A
linux-backports-modules-2.6.38-8-generic N/A
linux-firmware1.52
SourcePackage: linux
Title: package linux-image-2.6.38-12-generic 2.6.38-12.51 failed to
install/upgrade: el subproceso instalado el script post-installation devolvió
el código de salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2007
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.80
dmi.board.name: ISKAE
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnTOSHIBA:bvrV1.80:bd08/21/2007:svnTOSHIBA:pnSatelliteA200:pvrPSAECE-01100KSP:rvnTOSHIBA:rnISKAE:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite A200
dmi.product.version: PSAECE-01100KSP
dmi.sys.vendor: TOSHIBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889552/+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 825000] Re: package linux-image-2.6.32-33-generic 2.6.32-33.72 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 798414 ***
https://bugs.launchpad.net/bugs/798414
** This bug is no longer a duplicate of bug 881028
package initramfs-tools 0.99ubuntu8 failed to install/upgrade: due to a full
filesystem
** This bug has been marked a duplicate of bug 798414
update-initramfs should produce a more helpful error message when there
isn't enough free space--or provide an automatic tool for removal of old files
--
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/825000
Title:
package linux-image-2.6.32-33-generic 2.6.32-33.72 failed to
install/upgrade: subprocess installed post-installation script
returned error exit status 2
Status in linux package in Ubuntu:
Confirmed
Bug description:
Ubuntu version 10.04.3
Installed on Flash drive using software from pendrivelinux.com
After installation, performing an update from
System>Administration>Update Manager, led to this error message.
Problem can be reproduced when running "sudo apt-get upgrade" in
terminal. Please refer below for full error information in terminal:
ubuntu@ubuntu:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Setting up linux-image-2.6.32-33-generic (2.6.32-33.72) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.32-33-generic
lzma: Encoder error: -2147467259
Failed to create initrd image.
dpkg: error processing linux-image-2.6.32-33-generic (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
linux-image-2.6.32-33-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
ubuntu@ubuntu:~$
result of running "cat /proc/version_signature" :
Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
please find attached result of running "sudo lspci -vnvn"
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-33-generic 2.6.32-33.72
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 3833 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfeaf8000 irq 22'
Mixer name : 'Intel G45 DEVCTG'
Components : 'HDA:10ec0888,10ec0888,0011
HDA:80862802,80860101,0010'
Controls : 20
Simple ctrls : 11
Date: Fri Aug 12 14:14:03 2011
ErrorMessage: subprocess installed post-installation script returned error
exit status 2
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
eth1 no wireless extensions.
LiveMediaBuild: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: noprompt cdrom-detect/try-usb=true persistent
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz splash
-- BOOT_IMAGE=/casper/vmlinuz
RelatedPackageVersions: linux-firmware 1.34.7
RfKill:
SourcePackage: linux
Title: package linux-image-2.6.32-33-generic 2.6.32-33.72 failed to
install/upgrade: subprocess installed post-installation script returned error
exit status 2
dmi.bios.date: 05/27/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd05/27/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/825000/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 2046941] [NEW] [24.04]: mpt3sas: Critical Bug Fixes
Public bug reported: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 24.04 kernel. Below are the upstream commit IDs: 3c978492c333 : scsi: mpt3sas: Fix loop logic 0854065092a7 : scsi: mpt3sas: Remove volatile qualifier 4ca10f3e3174 : scsi: mpt3sas: Perform additional retries if doorbell read returns 0 ** Affects: linux (Ubuntu) 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/2046941 Title: [24.04]: mpt3sas: Critical Bug Fixes Status in linux package in Ubuntu: New Bug description: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 24.04 kernel. Below are the upstream commit IDs: 3c978492c333 : scsi: mpt3sas: Fix loop logic 0854065092a7 : scsi: mpt3sas: Remove volatile qualifier 4ca10f3e3174 : scsi: mpt3sas: Perform additional retries if doorbell read returns 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046941/+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 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: High Assignee: Hui Wang (hui.wang) Status: Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: Invalid => Triaged ** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: Triaged => New ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Description changed: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking + This PR is just a workaround, the upstream bug is here: + https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 + + After the upstream fixe this bug with a real fix, I will revert the + workaround and backport the real fix to Noble and Jammy oem-kernel. + [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. - [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. ** Description changed: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 - After the upstream fixe this bug with a real fix, I will revert the + After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Triaged Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Triaged Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2
** Description changed: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly + + This PR is just a workaround, the upstream bug is here: + https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 + + After the upstream fix this bug with a real fix, I will revert the + workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 1913809] Re: internal webcams of HP Elite X2 G2 not supported
Is there any progress on this? Haven't found a workable solution elsewhere, either. -- 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/1913809 Title: internal webcams of HP Elite X2 G2 not supported Status in libcamera package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Both internal webcams of my HP Elite X2 G2 work well in Windows, but don't work in Ubuntu 20.10 or Manjaro. The driver seems to be missing or misconfigured. According to linux-hardware.org, it's a "Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Imaging Unit". Guvcview recognises the Cameras as "Intel IPU3 CIO2", but doesn't show an image. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elis 6420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-01-28 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 004: ID 044e:1216 Alps Electric Co., Ltd Bus 001 Device 002: ID 0424:2422 Microchip Technology, Inc. (formerly SMSC) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Elite x2 1012 G2 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=8e01b873-3dab-4fbf-86ce-04c4932b3c0a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 10/20/2020 dmi.bios.release: 1.37 dmi.bios.vendor: HP dmi.bios.version: P87 Ver. 01.37 dmi.board.name: 82CA dmi.board.vendor: HP dmi.board.version: KBC Version 50.72 dmi.chassis.asset.tag: 5CG7272QT5 dmi.chassis.type: 32 dmi.chassis.vendor: HP dmi.ec.firmware.release: 80.114 dmi.modalias: dmi:bvnHP:bvrP87Ver.01.37:bd10/20/2020:br1.37:efr80.114:svnHP:pnHPElitex21012G2:pvr:rvnHP:rn82CA:rvrKBCVersion50.72:cvnHP:ct32:cvr: dmi.product.family: 103C_5336AN HP Elite x2 dmi.product.name: HP Elite x2 1012 G2 dmi.product.sku: Y5E21AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/1913809/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Changed in: linux (Ubuntu Noble) Status: Invalid => Triaged ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: Invalid => Triaged ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Triaged Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Triaged Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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
