[Kernel-packages] [Bug 1839144] Re: controller test from ubuntu_ltp will timeout B-KVM / B-gke
We can have ubuntu_ltp_controllers finish on B-kvm and I didn't see B-gke-4.15 in recent cycles. Considered that we don't have this issue in our hint database I will just close this. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid ** Changed in: linux-gke (Ubuntu) Status: New => Invalid ** 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-gke in Ubuntu. https://bugs.launchpad.net/bugs/1839144 Title: controller test from ubuntu_ltp will timeout B-KVM / B-gke Status in ubuntu-kernel-tests: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Bug description: Test timeout with 2hrs threshold. Steps to reproduce: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install sudo /opt/ltp/runltp -f /opt/ltp/runtest/controller This needs to be executed manually to see where is the culprit, and how long will it take. 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:55:48 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/1839144/+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 1848473] Re: cgroup_fj_stress_* in controllers from ubuntu_ltp failed with dir creation / fork on B-KVM
** 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-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 1837037] Re: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1837037 Title: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Won't Fix Bug description: Similar to bug 1837035 This memcg_move_charge_at_immigrate_test test failed on an i386 node "pepe" with Disco kernel. It failed with: memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up <<>> tag=memcg_move_charge_at_immigrate stime=1563448078 cmdline="memcg_move_charge_at_immigrate_test.sh" contacts="" analysis=exit <<>> memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 2162 memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm up: 2162 memcg_move_charge_at_immigrate_test 1 TPASS: rss is 0 as expected memcg_move_charge_at_immigrate_test 2 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 3 TPASS: rss is 135168 as expected memcg_move_charge_at_immigrate_test 4 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up memcg_move_charge_at_immigrate_test 6 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 6 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 6 TINFO: Warming up pid: 2207 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 6 TFAIL: Process 2207 exited with 1 after warm up memcg_move_charge_at_immigrate_test 7 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 7 TINFO: Running memcg_process --mmap-anon --shm -s 135168 memcg_move_charge_at_immigrate_test 7 TINFO: Warming up pid: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 7 TFAIL: Process exited with 1 after warm up <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=2 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_move_charge_at_immigrate memcg_move_charge_at_immigrate_test.sh" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 18 10:01 seq crw-rw 1 root audio 116, 33 Jul 18 10:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 18 11:16:36 2019 IwConfig: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1916046] Re: cve-2020-29373 in cve from ubuntu_ltp failed
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp0cve ** Tags removed: ubuntu-ltp0cve ** 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/1916046 Title: cve-2020-29373 in cve from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Not a regression, this is a new test added Feb 8, 2021: https://github.com/linux-test- project/ltp/commit/c4f669f13106862b6d8be38adf7825ae00ca7ac5 The log shows: 13260.02/08 21:37:31 DEBUG| utils:0153| [stdout] startup='Mon Feb 8 21:37:30 2021' 13261.02/08 21:37:31 DEBUG| utils:0153| [stdout] tst_test.c:1261: TINFO: Timeout per run is 0h 05m 00s 13262.02/08 21:37:31 DEBUG| utils:0153| [stdout] io_uring02.c:148: TFAIL: Write outside chroot succeeded. 13263.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13264.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 13265.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13266.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9392a27d88b9 13267.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff002b30181d 13268.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13269.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be vulnerable to CVE(s), see: 13270.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13271.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29373 13272.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13273.02/08 21:37:31 DEBUG| utils:0153| [stdout] Summary: 13274.02/08 21:37:31 DEBUG| utils:0153| [stdout] passed 0 13275.02/08 21:37:31 DEBUG| utils:0153| [stdout] failed 1 13276.02/08 21:37:31 DEBUG| utils:0153| [stdout] broken 0 13277.02/08 21:37:31 DEBUG| utils:0153| [stdout] skipped 0 13278.02/08 21:37:31 DEBUG| utils:0153| [stdout] warnings 0 13279.02/08 21:37:31 DEBUG| utils:0153| [stdout] tag=cve-2020-29373 stime=1612820250 dur=0 exit=exited stat=1 core=no cu=0 As of Feb 18, 2021, this CVE is not mitigated yet: https://ubuntu.com/security/CVE-2020-29373 Seen with linux-kvm 5.4.0-1033.34. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1916046/+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 1837005] Re: cve-2015-3290 in cve from ubuntu_ltp failed with B/D-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/1837005 Title: cve-2015-3290 in cve from ubuntu_ltp failed with B/D-i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Bug description: This issue was only spotted on an i386 node "pepe" with Disco kernel, passed with other arch with Disco. On B/C i386, the CVE test was not successfully executed, failed with Resource temporarily unavailable. Will need to verify this manually. Test report: <<>> tag=cve-2015-3290 stime=1563431630 cmdline="cve-2015-3290" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 03m 00s cve-2015-3290.c:407: INFO: attempting to corrupt nested NMI stack state cve-2015-3290.c:460: FAIL: corrupted NMI stack Summary: passed 0 failed 1 skipped 0 warnings 0 syslog output: 06:33:50 pepe kernel: [ 6042.144077] LTP: starting cve-2015-3290 06:33:50 pepe kernel: [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79250 06:33:50 pepe kernel: [ 6042.159531] show_signal: 16 callbacks suppressed 06:33:50 pepe kernel: [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef sp:b7d43280 error:800 06:33:50 pepe AutotestCrashHandler: Application cve-2015-3290, PID 7760 crashed 06:33:50 pepe AutotestCrashHandler: Writing core files to ['/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760'] 06:33:50 pepe AutotestCrashHandler: Could not determine from which application core file /home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760/core is from ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-20-generic 5.0.0-20.21 ProcVersionSignature: User Name 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 18 04:53 seq crw-rw 1 root audio 116, 33 Jul 18 04:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [ 6042.144077] LTP: starting cve-2015-3290 [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79250 [ 6042.159531] show_signal: 16 callbacks suppressed [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef sp:b7d43280 error:800 Date: Thu Jul 18 06:36:51 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837005/+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 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed (shmget() failed: Invalid argument, Process ### exited with 1 after warm up)
** 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1837035 Title: memcg_stat_rss from controllers in ubuntu_ltp failed (shmget() failed: Invalid argument, Process ### exited with 1 after warm up) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Bug description: This issue was spotted on an i386 node "pepe" with Disco kernel, it failed with: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up <<>> tag=memcg_stat_rss stime=1563448062 cmdline="memcg_stat_rss.sh" contacts="" analysis=exit <<>> memcg_stat_rss 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 1 TINFO: Warming up pid: 1784 memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784 memcg_stat_rss 1 TPASS: rss is 135168 as expected memcg_stat_rss 2 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 2 TINFO: Warming up pid: 1804 memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804 memcg_stat_rss 2 TPASS: rss is 0 as expected memcg_stat_rss 3 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096 memcg_stat_rss 3 TINFO: Warming up pid: 1825 memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825 memcg_stat_rss 3 TPASS: rss is 0 as expected memcg_stat_rss 4 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 4 TINFO: Warming up pid: 1845 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up memcg_stat_rss 5 TINFO: Starting test 5 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168 memcg_stat_rss 5 TINFO: Warming up pid: 1858 memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858 memcg_stat_rss 5 TPASS: rss is 135168 as expected memcg_stat_rss 6 TINFO: Starting test 6 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 6 TINFO: Warming up pid: 1878 memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878 memcg_stat_rss 6 TPASS: rss is 135168 as expected memcg_stat_rss 7 TPASS: rss is 0 as expected memcg_stat_rss 8 TINFO: Starting test 7 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 8 TINFO: Warming up pid: 1901 memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901 memcg_stat_rss 8 TPASS: rss is 0 as expected memcg_stat_rss 9 TPASS: rss is 0 as expected memcg_stat_rss 10 TINFO: Starting test 8 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096 memcg_stat_rss 10 TINFO: Warming up pid: 1925 memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925 memcg_stat_rss 10 TPASS: rss is 0 as expected memcg_stat_rss 11 TPASS: rss is 0 as expected memcg_stat_rss 12 TINFO: Starting test 9 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 12 TINFO: Warming up pid: 1948 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 12
[Kernel-packages] [Bug 1830360] Re: cpuset_load_balance from controller test suite in LTP failed
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1830360 Title: cpuset_load_balance from controller test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:24:55 2019' cpuset_load_balance 1 TINFO: general group load balance test cpuset_load_balance 1 TINFO: root group info: cpuset_load_balance 1 TINFO: sched load balance: 0 cpuset_load_balance 1 TINFO: general group info: cpuset_load_balance 1 TINFO: cpus: - cpuset_load_balance 1 TINFO: sched load balance: 1 cpuset_load_balance 1 TFAIL: load balance test failed. cpuset_load_balance 3 TINFO: general group load balance test cpuset_load_balance 3 TINFO: root group info: cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TINFO: general group info: cpuset_load_balance 3 TINFO: cpus: 1 cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TFAIL: load balance test failed. cpuset_load_balance 5 TINFO: general group load balance test cpuset_load_balance 5 TINFO: root group info: cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TINFO: general group info: cpuset_load_balance 5 TINFO: cpus: - cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TFAIL: load balance test failed. cpuset_load_balance 7 TINFO: general group load balance test cpuset_load_balance 7 TINFO: root group info: cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TINFO: general group info: cpuset_load_balance 7 TINFO: cpus: 1 cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TFAIL: load balance test failed. cpuset_load_balance 9 TINFO: general group load balance test cpuset_load_balance 9 TINFO: root group info: cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TINFO: general group info: cpuset_load_balance 9 TINFO: cpus: 1,2 cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TFAIL: load balance test failed. cpuset_load_balance 11 TINFO: general group load balance test cpuset_load_balance 11 TINFO: root group info: cpuset_load_balance 11 TINFO: sched load balance: 0 cpuset_load_balance 11 TINFO: general group info: cpuset_load_balance 11 TINFO: cpus: 1,2 cpuset_load_balance 11 TINFO: sched load balance: 1 cpuset_load_balance 11 TFAIL: load balance test failed. cpuset_load_balance 13 TINFO: general group load balance test cpuset_load_balance 13 TINFO: root group info: cpuset_load_balance 13 TINFO: sched load balance: 0 cpuset_load_balance 13 TINFO: general group info: cpuset_load_balance 13 TINFO: cpus: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39 cpuset_load_balance 13 TINFO: sched load balance: 1 cpuset_load_balance 13 TFAIL: load balance test failed. cpuset_load_balance 15 TINFO: general group load balance test cpuset_load_balance 15 TINFO: root group info: cpuset_load_balance 15 TINFO: sched load balance: 0 cpuset_load_balance 15 TINFO: general group1 info: cpuset_load_balance 15 TINFO: cpus: 1 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: general group2 info: cpuset_load_balance 15 TINFO: cpus: 0 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: CPU hotplug: none cpuset_load_balance 15 TFAIL: load balance test failed. cpuset_load_balance 17 TINFO: general group load balance test cpuset_load_balance 17 TINFO: root group info: cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: general group1 info: cpuset_load_balance 17 TINFO: cpus: 1,2 cpuset_load_balance 17 TINFO: sched load balance: 1 cpuset_load_balance 17 TINFO: general group2 info: cpuset_load_balance 17 TINFO: cpus: 0-3 cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: CPU hotplug: none cpuset_load_balance 17 TFAIL: load balance test failed. cpuset_load_balance 19 TINFO: general group load balance test cpuset_load_balance 19 TINFO: root group info: cpuset_load_balance 19 TINFO: sched load balance: 0 cpuset_load_balance 19 TINFO: general group1 info: cpuset_load_balance 19 TINFO: cpus: 1,2 cpuset_load_balance 19 TINFO: sched load balance: 1 cpuset_load_balance 19
[Kernel-packages] [Bug 1830361] Re: cpuset_sched_domains from controller test suite in LTP failed
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1830361 Title: cpuset_sched_domains from controller test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:24:26 2019' cpuset_sched_domains 1 TINFO: root group load balance test cpuset_sched_domains 1 TINFO: sched load balance: 0 cpuset_sched_domains 1 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 1 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 1 TFAIL: partition sched domains failed. cpuset_sched_domains 3 TINFO: root group load balance test cpuset_sched_domains 3 TINFO: sched load balance: 1 cpuset_sched_domains 3 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 3 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 3 TFAIL: partition sched domains failed. cpuset_sched_domains 5 TINFO: root group load balance test cpuset_sched_domains 5 TINFO: sched load balance: 0 cpuset_sched_domains 5 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 5 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 5 TFAIL: partition sched domains failed. cpuset_sched_domains 7 TINFO: root group load balance test cpuset_sched_domains 7 TINFO: sched load balance: 0 cpuset_sched_domains 7 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 7 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 7 TFAIL: partition sched domains failed. cpuset_sched_domains 9 TINFO: root group load balance test cpuset_sched_domains 9 TINFO: sched load balance: 1 cpuset_sched_domains 9 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 9 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 9 TFAIL: partition sched domains failed. cpuset_sched_domains 11 TINFO: root group load balance test cpuset_sched_domains 11 TINFO: sched load balance: 1 cpuset_sched_domains 11 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 11 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 11 TFAIL: partition sched domains failed. cpuset_sched_domains 13 TINFO: general group load balance test cpuset_sched_domains 13 TINFO: root group info: cpuset_sched_domains 13 TINFO: sched load balance: 0 cpuset_sched_domains 13 TINFO: general group info: cpuset_sched_domains 13 TINFO: cpus: - cpuset_sched_domains 13 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 13 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 13 TFAIL: partition sched domains failed. cpuset_sched_domains 15 TINFO: general group load balance test cpuset_sched_domains 15 TINFO: root group info: cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_sched_domains 15 TINFO: general group info: cpuset_sched_domains 15 TINFO: cpus: 1 cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 15 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 15 TFAIL: partition sched domains failed. cpuset_sched_domains 17 TINFO: general group load balance test cpuset_sched_domains 17 TINFO: root group info: cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_sched_domains 17 TINFO: general group info: cpuset_sched_domains 17 TINFO: cpus: - cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 17 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 17 TFAIL: partition sched domains failed. cpuset_sched_domains 19 TINFO: general group load balance test
[Kernel-packages] [Bug 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node)
** 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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830585 Title: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Focal: New Status in linux-azure source package in Focal: New Status in linux source package in Hirsute: Won't Fix Status in linux-azure source package in Hirsute: Won't Fix Bug description: Test failed with: cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). <<>> tag=cpuset_memory_spread stime=1558937747 cmdline=" cpuset_memory_spread_testset.sh" contacts="" analysis=exit <<>> 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 0.0993112 s, 1.1 GB/s cpuset_memory_spread 1 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 3 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 5 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). cpuset_memory_spread 9 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 11 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 13 TPASS: Cpuset memory spread page test succeeded. <<>> initiation_status="ok" duration=10 termination_type=exited termination_id=1 corefile=no cutime=364 cstime=383 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 05:39 seq crw-rw 1 root audio 116, 33 May 27 05:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon May 27 06:16:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830585/+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 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64)
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64) Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+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 1830678] Re: netns_sysfs from containers test suite in LTP failed with KVM kernel
We have config_dummy enabled for newer KVM kernels. And the test is capable of detecting missing config now. https://github.com/linux-test- project/ltp/commit/5059889abdb61a53d2598cd0e52147af22e3d2c3 ** Changed in: ubuntu-kernel-tests Status: Confirmed => Fix Released ** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-stable -- 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/1830678 Title: netns_sysfs from containers test suite in LTP failed with KVM kernel Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Invalid Bug description: <<>> tag=netns_sysfs stime=1559024934 cmdline="netns_sysfs.sh" contacts="" analysis=exit <<>> incrementing stop RTNETLINK answers: Operation not supported netns_sysfs 1 TBROK: failed to add a new (host) dummy device <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=1 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35 ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18 Uname: Linux 4.15.0-1035-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 28 06:22:51 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/1830678/+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 2046875] [NEW] [22.04.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 22.04.04 point 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/2046875 Title: [22.04.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 22.04.04 point 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/2046875/+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 2046085] Re: Problem with driver for Realtek 8852be Wi-Fi pci card
Close this as per reporter's comment in #5. ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Invalid -- 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/2046085 Title: Problem with driver for Realtek 8852be Wi-Fi pci card Status in linux-firmware package in Ubuntu: Invalid Bug description: I am not sure that this shall come into Ubuntu bug tracker, but correct me if I am wrong. I have a fan-less media pc that has PCI WI-FI adapter rtl8852be. I know this chipset has support in HWE Ubuntu kernel but for some reason, firmware for it still not being recognized. First I tried to make it work with 6.2 generic HWE kernel and the only strings I have in dmesg: [ 15.034783] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 15.061504] rtw89_8852be :03:00.0: no suitable firmware found [ 15.061543] rtw89_8852be :03:00.0: failed to recognize firmware [ 15.061557] rtw89_8852be :03:00.0: failed to setup chip information [ 15.075283] rtw89_8852be: probe of :03:00.0 failed with error -2 Then I tried to use linux-image-6.5.0-1009-oem kernel and get a little bit more info: [ 16.501540] rtw89_8852be :03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 16.503083] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 16.567443] rtw89_8852be :03:00.0: xtal si not ready(R): offset=41 [ 16.567470] rtw89_8852be :03:00.0: no suitable firmware found [ 16.567494] rtw89_8852be :03:00.0: failed to recognize firmware [ 16.567509] rtw89_8852be :03:00.0: failed to setup chip information [ 16.572860] rtw89_8852be: probe of :03:00.0 failed with error -2 I suspect my PCI WIFI card has different subvendor ID and subdevice ID compare to the popular ones: Lenovo laptops have 8852be has PCI 10ec:b852:17aa:4853 HP laptops have 8852be has PCI 10ec:b852:103c:88e3 Mine is: PCI 10ec:b852:10ec:b852 Any suggestions are welcomed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.23 ProcVersionSignature: Ubuntu 6.5.0-1009.10-oem 6.5.3 Uname: Linux 6.5.0-1009-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Dec 10 21:46:40 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.4 InstallationDate: Installed on 2023-09-15 (86 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SDZ X133 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1009-oem root=UUID=cd870d97-e484-43d5-aafa-2ba1ec68a7a8 ro cpufreq.default_governor=powersave RelatedPackageVersions: linux-restricted-modules-6.5.0-1009-oem N/A linux-backports-modules-6.5.0-1009-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2023 dmi.bios.release: 1.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: PC_STICK_8G_D8R2 dmi.board.asset.tag: Default string dmi.board.name: X133 dmi.board.vendor: SDZ dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: SDZ dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrPC_STICK_8G_D8R2:bd05/12/2023:br1.20:svnSDZ:pnX133:pvrDefaultstring:rvnSDZ:rnX133:rvrDefaultstring:cvnSDZ:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Notebook dmi.product.name: X133 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SDZ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2046085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1830316] Re: ksm06* from mm test suite in LTP failed on D
Kernel EOL and this does not exist in our hint database. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830316 Title: ksm06* from mm test suite in LTP failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: Issue found on node "grumman". Test failed with: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY startup='Thu May 23 14:41:43 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s safe_file_ops.c:301: BROK: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ksm06 stime=1558622503 dur=0 exit=exited stat=2 core=no cu=0 cs=0 startup='Thu May 23 14:41:44 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s safe_file_ops.c:301: BROK: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ksm06_1 stime=1558622504 dur=0 exit=exited stat=2 core=no cu=0 cs=1 startup='Thu May 23 14:41:44 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s safe_file_ops.c:301: BROK: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ksm06_2 stime=1558622504 dur=1 exit=exited stat=2 core=no cu=0 cs=25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830316/+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 1830359] Re: cpuset_base_ops from controller test suite in LTP failed
** 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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830359 Title: cpuset_base_ops from controller test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:23:44 2019' cpuset_base_ops 1 TPASS: cpuset.cpus(READONLY): Get the expected string cpuset_base_ops 3 TPASS: cpuset.mems(READONLY): Get the expected string cpuset_base_ops 5 TPASS: cpuset.memory_pressure(READONLY): Get the expected string cpuset_base_ops 7 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 9 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 11 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 13 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 15 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 17 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 19 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 21 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 23 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 25 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 27 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 29 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 31 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 33 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 35 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result - Expected string - "0" cpuset_base_ops 39 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 41 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 43 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 45 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 47 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 49 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 51 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 53 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 55 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 57 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 59 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 61 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 63 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 65 TFAIL: cpuset.mems: Test result - Expected string - "0" cpuset_base_ops 67 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 69 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 71 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 73 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 75 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 77 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 79 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 81 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 83 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 85 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 87 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 89 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 91 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 93 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 95 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 97 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 99 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 101 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 103 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 105 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 107 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 109 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 111 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 113 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 115 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 117 TPASS: cpuset.memory_spread_slab: Get the expected string
[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
Since a years ago I know that there is a firmware fix for this issue, but it was not public. I know firmwares are leaked in station-drivers and finally I decided to give it a try following the excellent guide by this guy: https://forum-en.msi.com/index.php?threads/asmedia-usb-3-1-controller-firmware-update-for-ge62-72-xxx.380024/ Instead of editing the INI I think you can modify the svid and ssid in the update tool directly by unlocking it with the password - asmedia. First make a backup with the DOS tool. And gather information about your device like svid and ssid before flashing. Since I updated I haven't got TRB errors. Good luck. -- 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/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in Linux: Confirmed Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1749961/+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 1933112] Re: fallocate05 from ltp-syscalls fails on H-azure
This issue does not exist in our database. And the kernels are EOL. ** Changed in: ubuntu-kernel-tests Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Impish) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933112 Title: fallocate05 from ltp-syscalls fails on H-azure Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: Found on hirsute/azure 5.11.0-1007.7 and 5.11.0-1006.6. might be re- appearance of lp:1783880, btrfs file system, only on Azure instance Standard_F32s_v2: tst_test.c:1379: TINFO: Testing on btrfs tst_test.c:888: TINFO: Formatting /dev/loop3 with btrfs opts='' extra opts='' tst_test.c:1311: TINFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:32: TINFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) fallocate05.c:81: TPASS: write() wrote 65536 bytes fallocate05.c:102: TINFO: fallocate()d 0 extra blocks on full FS fallocate05.c:114: TPASS: fallocate() on full FS fallocate05.c:130: TPASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) fallocate05.c:134: TFAIL: write(): ENOSPC (28) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1933112/+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
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: High Assignee: Hui Wang (hui.wang) Status: Invalid -- 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: Invalid 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 Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid 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
[Kernel-packages] [Bug 1851653] Re: copy_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3
Kernel EOL, and this issue does not exist in our hinting database. ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851653 Title: copy_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: copy_file_range02 from ubuntu_ltp_syscalls failed on i386 node pepe with B-hwe-edge 5.3 kernel Test failed with: copy_file_range02.c:141: FAIL: copy_file_range failed unexpectedly; expected EOVERFLOW, but got: EFBIG (27) Test output: startup='Thu Nov 7 09:22:16 2019' tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s copy_file_range.h:36: INFO: Testing libc copy_file_range() tst_device.c:87: INFO: Found free device 1 '/dev/loop1' Setting up swapspace version 1, size = 36 KiB (36864 bytes) no label, UUID=d68e7005-a932-41eb-a444-3aff47d5cf84 copy_file_range02.c:108: INFO: Test #0: readonly file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #1: directory copy_file_range02.c:137: PASS: copy_file_range failed as expected: EISDIR (21) copy_file_range02.c:108: INFO: Test #2: append to file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #3: closed file descriptor copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #4: invalid flags copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #5: immutable file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EPERM (1) copy_file_range02.c:108: INFO: Test #6: swap file copy_file_range02.c:137: PASS: copy_file_range failed as expected: ETXTBSY (26) copy_file_range02.c:108: INFO: Test #7: overlaping range copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #8: block device copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #9: char device copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #10: fifo copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #11: pipe copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #12: max length lenght copy_file_range02.c:141: FAIL: copy_file_range failed unexpectedly; expected EOVERFLOW, but got: EFBIG (27) copy_file_range02.c:108: INFO: Test #13: max file size copy_file_range02.c:137: PASS: copy_file_range failed as expected: EFBIG (27) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s copy_file_range.h:39: INFO: Testing __NR_copy_file_range syscall tst_device.c:87: INFO: Found free device 1 '/dev/loop1' Setting up swapspace version 1, size = 36 KiB (36864 bytes) no label, UUID=7ef630e1-d0f3-4072-91ec-ae49ab13c6dc copy_file_range02.c:108: INFO: Test #0: readonly file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #1: directory copy_file_range02.c:137: PASS: copy_file_range failed as expected: EISDIR (21) copy_file_range02.c:108: INFO: Test #2: append to file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #3: closed file descriptor copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #4: invalid flags copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #5: immutable file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EPERM (1) copy_file_range02.c:108: INFO: Test #6: swap file copy_file_range02.c:137: PASS: copy_file_range failed as expected: ETXTBSY (26) copy_file_range02.c:108: INFO: Test #7: overlaping range copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #8: block device copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #9: char device copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
[Kernel-packages] [Bug 1855841] Re: syslog10 from ubuntu_ltp_syscalls failed on Standard_B1ms with E-Azure 5.3
Kernel EOL, and this issue does not exist in our hinting database. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux-azure (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1855841 Title: syslog10 from ubuntu_ltp_syscalls failed on Standard_B1ms with E-Azure 5.3 Status in ubuntu-kernel-tests: Won't Fix Status in linux-azure package in Ubuntu: Won't Fix Bug description: syslog10 failed on Standard_B1ms instance with Eoan Azure 5.3.0-1009.10 Fail rate 2 out of 2, this is the only failing instance among all the other instances. startup='Sat Dec 7 03:00:58 2019' syslog100 TINFO : Test setlogmask() with LOG_MASK macro. syslog100 TINFO : o Use setlogmask() with LOG_MASK macro to set an syslog100 TINFO : individual priority level. syslog100 TINFO : o Send the message of above prority and expect it to be syslog100 TINFO : logged. syslog100 TINFO : o Send message which is at other priority level to syslog100 TINFO : the one set above, which should not be logged. syslog100 TINFO : syslog: Testing setlogmask() with LOG_MASK macro... syslog100 TINFO : restarting syslog daemon syslog101 TFAIL : ltpapicmd.c:188: Expected message was not logged syslog100 TINFO : restarting syslog daemon tag=syslog10 stime=1575687658 dur=17 exit=exited stat=1 core=no cu=2 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855841/+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 1896616] Re: set correct device size of loopback devices
https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/groovy/commit/?id=05fa16bade61432bc7858d7316e4480938aa0cb8 ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- 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/1896616 Title: set correct device size of loopback devices Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] SRU test ubuntu_ltp_syscalls is reporting the following message: 11:52:03 DEBUG| [stdout] ioctl_loop07.c:62: FAIL: /sys/block/loop4/size != 1024 got 2048 11:52:03 DEBUG| [stdout] ioctl_loop07.c:63: PASS: /sys/block/loop4/loop/sizelimit = 524288 11:52:03 DEBUG| [stdout] ioctl_loop07.c:66: PASS: LOOP_GET_STATUS64 gets correct lo_sizelimit(524288) 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79e5dc59e297 [Test case] $ sudo autotest/client/autotest-local -v autotest/client/tests/ubuntu_ltp_syscalls/control [Fix] Apply upstream commit 79e5dc59e297. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896616/+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 1902473] Re: select03 from ubuntu_ltp_syscalls failed on G / F-oem-5.10
Kernel EOL, I didn't see this among other kernels. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902473 Title: select03 from ubuntu_ltp_syscalls failed on G / F-oem-5.10 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Won't Fix Bug description: This is a new test case, test failed with: <<>> tag=select03 stime=1604290335 cmdline="select03" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:107: TINFO: Testing libc select() select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22) select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0 select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14) tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:110: TINFO: Testing SYS_select syscall select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22) select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0 select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14) tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:113: TINFO: Testing SYS_pselect6 syscall select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22) select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0 select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14) tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:116: TINFO: Testing SYS_pselect6 time64 syscall select_var.h:81: TCONF: __NR_pselect6 time64 variant not supported tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:119: TINFO: Testing SYS__newselect syscall select_var.h:87: TCONF: syscall(-1) __NR__newselect not supported Summary: passed 15 failed 9 skipped 2 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=1 <<>> ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 28 09:30 seq crw-rw 1 root audio 116, 33 Oct 28 09:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Mon Nov 2 04:10:52 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: 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=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=f06509c5-4a0a-4cae-be3c-e5d21c1687c9 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 2046681] Re: jammy-oem-6.5: one more pannel needs to disable psr2
** Tags added: somerville ** Summary changed: - jammy-oem-6.5: one more pannel needs to disable psr2 + jammy-oem-6.5: one more panel needs to disable psr2 -- 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-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress 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 2046841] [NEW] Unable to access UART2and UART4
Public bug reported: Ubuntu 23.10 6.5.0-1008-raspi I've summarized the problem here, and asked for help: https://askubuntu.com/questions/1496927/raspberry-pi-5-uart2-and- uart4-problem This question hasn't elicited a response. I'm assuming this is a problem with 6.5.0 kernel on Pi 5 hardware. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-1008-raspi 6.5.0-1008.11 ProcVersionSignature: Ubuntu 6.5.0-1008.11-raspi 6.5.3 Uname: Linux 6.5.0-1008-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Tue Dec 19 09:54:18 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2046841 Title: Unable to access UART2and UART4 Status in linux-raspi package in Ubuntu: New Bug description: Ubuntu 23.10 6.5.0-1008-raspi I've summarized the problem here, and asked for help: https://askubuntu.com/questions/1496927/raspberry-pi-5-uart2-and- uart4-problem This question hasn't elicited a response. I'm assuming this is a problem with 6.5.0 kernel on Pi 5 hardware. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-1008-raspi 6.5.0-1008.11 ProcVersionSignature: Ubuntu 6.5.0-1008.11-raspi 6.5.3 Uname: Linux 6.5.0-1008-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Tue Dec 19 09:54:18 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2046841/+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 2032538] Re: Boot hangs after kernel upgrade to 6.2.0-26-generic
Version 6.2.0-39-generic is able to boot, though with one caveat. I have three monitors: one belonging to the laptop, one connected to the laptop via HDMI, and another connected via HDMI to a D6000S docking station which is connecting to the laptop via USB-C. The latter two monitors display the splash/login screen to decrypt a drive while the laptop's native screen does not. So I think the original issue has been solved and this particular bug can be closed out. -- 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/2032538 Title: Boot hangs after kernel upgrade to 6.2.0-26-generic Status in linux package in Ubuntu: Confirmed Bug description: This could be a bug in the linux-image package, but it might also be an issue with missing firmware (ref: https://ubuntuforums.org/showthread.php?t=2489771=2=565081c5663bac1bf6994963b20e9f83). 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Broken Linux kernel version: 6.2.0-26-generic Working Linux kernel version: 5.19.0-50-generic 3) What you expected to happen Successful boot 4) What happened instead Hangs indefinitely (at least more than two minutes) From the "DebuggingKernelBoot" Wiki page: >The appropriate log(s) in their entirety from /var/log uncompressed. No boots logs are generated; the boot hangs before the root filesystem is decrypted. >An unedited video of the entire bad boot from start to finish via cellphone or camera recording. Will try and upload as second attachment; may run into space constraints. >A picture of the bad boot via cellphone or camera. See: IMG20230814161928.jpg >For example, if you notice ACPI errors, try booting with the acpi=off boot option. For a full description of these options, refer to the kernel parameters document. This successfully boots the kernel, but neither the secondary HDMI-attached monitor nor the tertiary docking-station attached monitor then work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: i3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-08 (293 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP ZBook Fury 16 G9 Mobile Workstation PC Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-50-generic N/A linux-backports-modules-5.19.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: jammy Uname: Linux 5.19.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/26/2023 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: U96 Ver. 01.08.00 dmi.board.name: 89C6 dmi.board.vendor: HP dmi.board.version: KBC Version 15.63.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 21.99 dmi.modalias: dmi:bvnHP:bvrU96Ver.01.08.00:bd06/26/2023:br8.0:efr21.99:svnHP:pnHPZBookFury16G9MobileWorkstationPC:pvr:rvnHP:rn89C6:rvrKBCVersion15.63.00:cvnHP:ct10:cvr:sku78K31UP#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Fury 16 G9 Mobile Workstation PC dmi.product.sku: 78K31UP#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032538/+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 2030978] Re: kernel 6.5 changes cause UBSAN errors (patch included)
I build me own kernel now and removed all UBSAN-stuff. This helped.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2030978
Title:
kernel 6.5 changes cause UBSAN errors (patch included)
Status in broadcom-sta package in Ubuntu:
Confirmed
Bug description:
"On Linux 6.5, due to commit 2d47c6956ab3 ("ubsan: Tighten UBSAN_BOUNDS
on GCC"), flexible trailing arrays declared like `whatever_t foo[1];`
will generate warnings when CONFIG_UBSAN & co. is enabled."
Due to changes in kernel 6.5, we get this error in dmesg:
[ 28.818756]
[ 28.822952] UBSAN: array-index-out-of-bounds in
/var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
[ 28.82] index 2 is out of range for type 'ether_addr [1]'
[ 28.832900] CPU: 1 PID: 1232 Comm: avahi-daemon Tainted: P OE
6.5.0-rc4 #1
[ 28.836452] Hardware name: Apple Inc. MacBookPro11,3/Mac-2BD1B31983FE1663,
BIOS 432.60.3.0.0 10/27/2021
[ 28.839806] Call Trace:
[ 28.843091]
[ 28.846387] dump_stack_lvl+0x48/0x60
[ 28.849692] dump_stack+0x10/0x20
[ 28.852965] __ubsan_handle_out_of_bounds+0xc6/0x100
[ 28.856251] _wl_set_multicast_list+0x1fd/0x220 [wl]
[ 28.859191] wl_set_multicast_list+0x3a/0x80 [wl]
[ 28.861879] __dev_set_rx_mode+0x6a/0xc0
[ 28.864237] __dev_mc_add+0x82/0x90
[ 28.866587] dev_mc_add+0x10/0x20
[ 28.868920] igmp_group_added+0x198/0x1d0
[ 28.871102] ip_mc_inc_group+0x185/0x2b0
[ 28.873231] __ip_mc_join_group+0x108/0x170
[ 28.875170] ip_mc_join_group+0x10/0x20
[ 28.877111] do_ip_setsockopt+0x104d/0x1160
[ 28.878894] ? __sys_setsockopt+0xeb/0x1c0
[ 28.880657] ip_setsockopt+0x30/0xb0
[ 28.882326] udp_setsockopt+0x22/0x40
[ 28.883949] sock_common_setsockopt+0x14/0x20
[ 28.885554] __sys_setsockopt+0xde/0x1c0
[ 28.887063] __x64_sys_setsockopt+0x1f/0x30
[ 28.888564] do_syscall_64+0x55/0x80
[ 28.889952] ? syscall_exit_to_user_mode+0x26/0x40
[ 28.891226] ? __x64_sys_recvmsg+0x1d/0x20
[ 28.892450] ? do_syscall_64+0x61/0x80
[ 28.893651] ? do_syscall_64+0x61/0x80
[ 28.894796] entry_SYSCALL_64_after_hwframe+0x46/0xb0
[ 28.895942] RIP: 0033:0x7f0a97a7ddae
[ 28.897100] Code: 0f 1f 40 00 48 8b 15 69 60 0d 00 f7 d8 64 89 02 48 c7 c0
ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 49 89 ca b8 36 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 0a c3 66 0f 1f 84 00 00 00 00 00 48 8b 15 31
[ 28.898270] RSP: 002b:7fffb7b1b3f8 EFLAGS: 0246 ORIG_RAX:
0036
[ 28.899449] RAX: ffda RBX: 000c RCX:
7f0a97a7ddae
[ 28.900623] RDX: 0023 RSI: RDI:
000c
[ 28.901784] RBP: 0001 R08: 000c R09:
0004
[ 28.902895] R10: 7fffb7b1b404 R11: 0246 R12:
7fffb7b1b404
[ 28.904011] R13: 0014 R14: 55cc506ee078 R15:
55cc506eaf60
[ 28.905149]
[ 28.906228]
A patch is however available for this issue:
https://gist.github.com/joanbm/9cd5fda1dcfab9a67b42cc6195b7b269
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: bcmwl-kernel-source (not installed)
Uname: Linux 6.5.0-rc4 x86_64
NonfreeKernelModules: wl zfs
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Aug 10 10:40:27 2023
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: broadcom-sta
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2030978/+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 2029010]
(In reply to Tommaso from comment #52) > With kernel 6.7 there will finally be support for Everest sound cards also > for AMD CPUs thanks to the AWESOME work of Marian Postevca (aka codepayne). > More info here: https://patchwork.kernel.org/comment/25504908/ > > You can already try it by installing the release candidates but pay > attention: > - There is currently a regression in the PM handling of the AMD ACP sound > controller, discussed here > https://lore.kernel.org/alsa-devel/87a5v8szhc@mutex.one/ > - On Fedora the necessary kernel module is not currently enabled > - You need to make some adjustments from alsamixer > > Here you will find further information: > > https://github.com/codepayne/linux-sound-huawei/issues/26 is a backport to the lts core expected? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2029010 Title: dummy sound on huawei mate d15 laptop Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried different options, but I couldn't raise the sound. saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd03c irq 80 1 [acp]: acp - acp HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2 saber716rus@saber716rus-BOM-WXX9 ~> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2029010/+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 2029010] Re: dummy sound on huawei mate d15 laptop
hello. Will there be a backport to the lts core? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2029010 Title: dummy sound on huawei mate d15 laptop Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried different options, but I couldn't raise the sound. saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd03c irq 80 1 [acp]: acp - acp HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2 saber716rus@saber716rus-BOM-WXX9 ~> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2029010/+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 2029010] Re: dummy sound on huawei mate d15 laptop
hello. Will there be a backport to the lts core? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2029010 Title: dummy sound on huawei mate d15 laptop Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried different options, but I couldn't raise the sound. saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd03c irq 80 1 [acp]: acp - acp HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2 saber716rus@saber716rus-BOM-WXX9 ~> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2029010/+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 2029010] Re: dummy sound on huawei mate d15 laptop
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2029010 Title: dummy sound on huawei mate d15 laptop Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried different options, but I couldn't raise the sound. saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd03c irq 80 1 [acp]: acp - acp HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2 saber716rus@saber716rus-BOM-WXX9 ~> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2029010/+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 2042713] Re: Pale Green blank screen after login
Mario, I would I do that, please? (aka "Please add kernel log from both your old kernel and new kernel.") -- 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/2042713 Title: Pale Green blank screen after login Status in linux package in Ubuntu: Incomplete Bug description: Since linux Kernel 5.15.0-86, when I only get a pale green blank screen after login Linux Mint 21.2 Victoria / Cinnamon so I got to use 5.15.0-84. N.B. I'm using a Graphic AMD processor with unconventional screens resolutions (1280x1025 (5/4) & 1360x768 (16:9)) inxi : CPU: dual core AMD A6-9500 RADEON R5 8 COMPUTE CORES 2C+6G (-MT MCP-) speed/min/max: 3594/1400/3500 MHz Kernel: 5.15.0-84-generic x86_64 Up: 12h 9m Mem: 1946.1/15413.6 MiB (12.6%) Storage: 7.04 TiB (38.5% used) Procs: 256 Shell: Bash inxi: 3.3.13 inxi -S : System: Host: linuxmint Kernel: 5.15.0-84-generic x86_64 bits: 64 Desktop: Cinnamon 5.8.4 Distro: Linux Mint 21.2 Victoria To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042713/+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 2046793] [NEW] vlan: unable to rmmod 8021q due to netdevice reference leak
Public bug reported:
[Impact]
In some conditions, is not possible to remove the vlan module due to a
netdevice reference leak.
The problem has been fixed in linux v5.17 with commit d6ff94afd90b ("vlan: move
dev_put into vlan_dev_uninit").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d6ff94afd90b
This commit has been backported in linux 5.15.142:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=02caa78cbc22
To avoid conflict, the following commit was also backported right before:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=842801181864
[Test Case]
As described in the commit, it is simple to reproduce the issue. Simply
create a dummy, a vlan on top of it, and a vlan on top of the previously
created vlan, then try to remove the 8021q module.
ip link add dummy0 type dummy
ip link add link dummy0 name dummy0.1 type vlan id 1
ip link add link dummy0.1 name dummy0.1.2 type vlan id 2
rmmod 8021q
[freeze]
unregister_netdevice: waiting for dummy0.1 to become free. Usage count = 1
[Regression Potential]
These 2 patches are quite simple. They have been backported in the
official 5.15 stable. The risk of regression should be contained.
** 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/2046793
Title:
vlan: unable to rmmod 8021q due to netdevice reference leak
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
In some conditions, is not possible to remove the vlan module due to a
netdevice reference leak.
The problem has been fixed in linux v5.17 with commit d6ff94afd90b ("vlan:
move dev_put into vlan_dev_uninit").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d6ff94afd90b
This commit has been backported in linux 5.15.142:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=02caa78cbc22
To avoid conflict, the following commit was also backported right before:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=842801181864
[Test Case]
As described in the commit, it is simple to reproduce the issue.
Simply create a dummy, a vlan on top of it, and a vlan on top of the
previously created vlan, then try to remove the 8021q module.
ip link add dummy0 type dummy
ip link add link dummy0 name dummy0.1 type vlan id 1
ip link add link dummy0.1 name dummy0.1.2 type vlan id 2
rmmod 8021q
[freeze]
unregister_netdevice: waiting for dummy0.1 to become free. Usage count = 1
[Regression Potential]
These 2 patches are quite simple. They have been backported in the
official 5.15 stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046793/+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 2046726] [NEW] [24.04 LTS]: megaraid_sas driver update
Public bug reported: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [24.04 LTS]: megaraid_sas Driver Update + [24.04 LTS]: megaraid_sas driver update -- 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: New Bug description: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046726/+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 2046722] [NEW] [22.04.04]: megaraid_sas: Critical Bug Fixes
Public bug reported: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [22.04.04]: megaraid_sas: Critical fixes + [22.04.04]: megaraid_sas: Critical Bug Fixes -- 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/2046722 Title: [22.04.04]: megaraid_sas: 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 22.04.04 point kernel. Below are the upstream commit IDs: 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
>From the linked page: However, that doesn't mean people don't accept the risks. There are many corporations and individuals using PPTP with full knowledge of these risks. Some use mitigating controls, and some don't. No one has ever run pptp on Linux, as either a client or server, because they thought it was a good protocol. It was used because compatibility was required with the other end. > IPSec OpenVPN Strongswan are much better alternatives. What is the compatibility story for these on Windows? The page you link also says: > Microsoft promote something else. What, specifically, and what is the Linux compatibility story with that "something else"? It should be clear in this removal bug what users should be using instead of pptp as a Windows-compatible VPN. ** Changed in: pptpd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Incomplete Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. IPSec OpenVPN Strongswan are much better alternatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+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
