[Kernel-packages] [Bug 2050083] Re: generate and ship vmlinux.h to allow packages to build BPF CO-RE
I have sent a patch to kernel-team adding this new package, tested a local build on oracular amd64 and it seems to work: https://lists.ubuntu.com/archives/kernel-team/2024-July/152477.html -- 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/2050083 Title: generate and ship vmlinux.h to allow packages to build BPF CO-RE Status in linux package in Ubuntu: New Bug description: A vmlinux.h header generated from a kernel build with bpftool is needed to build and ship BPF CO-RE programs. We are looking to ship these in the next version of systemd. vmlinux.h being generated depends on the kernel version, architecture and kconfig. There are some vague promises of backward compatibility, but it is hard to gauge. We definitely do not want this file to be generated from the kernel running the build machine when building a package though, as very often these are very old and stable kernels building packages for the bleeding edge. In Fedora and now Debian we generate vmlinux.h at kernel package build time, and ship it with the other kernel headers (_not_ UAPI, the internal headers): https://salsa.debian.org/kernel- team/linux/-/commit/ac6f7eda4c3e8b0d0db20ad4bb8236371cf8d38e Please consider doing the same in Ubuntu's linux-headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050083/+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 2038777] Re: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
Github Actions enabled KVM for all open source repositories for free in January: https://github.blog/2024-01-17-github-hosted-runners-double-the-power- for-open-source/ We started using it in systemd, and we hit this bug: https://paste.centos.org/view/411107c8 This will start quickly affecting everybody who tries to use KVM in their CI jobs on Github. Could you please arrange for this fix to be backported to the azure kernel for jammy? ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-meta-azure-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-meta-azure-6.5 (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-azure-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038777 Title: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c) Status in linux package in Ubuntu: Expired Status in linux-meta-azure-6.5 package in Ubuntu: Confirmed Status in linux source package in Jammy: New Status in linux-meta-azure-6.5 source package in Jammy: Confirmed Bug description: HiperV VM network problems [ 19.259297] [ 19.259536] UBSAN: array-index-out-of-bounds in /build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41 [ 19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]' [ 19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 6.5.0-7-generic #7-Ubuntu [ 19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022 [ 19.259899] Call Trace: [ 19.259901] [ 19.259902] dump_stack_lvl+0x48/0x70 [ 19.259908] dump_stack+0x10/0x20 [ 19.259909] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 19.259912] netvsc_receive+0x437/0x490 [hv_netvsc] [ 19.259917] netvsc_poll+0x176/0x4b0 [hv_netvsc] [ 19.259921] __napi_poll+0x30/0x1f0 [ 19.259924] net_rx_action+0x181/0x2e0 [ 19.259925] __do_softirq+0xd6/0x346 [ 19.259927] ? _raw_spin_unlock+0xe/0x40 [ 19.259929] __irq_exit_rcu+0x75/0xa0 [ 19.259932] irq_exit_rcu+0xe/0x20 [ 19.259933] sysvec_hyperv_callback+0x92/0xd0 [ 19.259935] [ 19.259935] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.8 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CrashDB: ubuntu Date: Sun Oct 8 23:09:45 2023 InstallationDate: Installed on 2021-03-07 (945 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) PackageArchitecture: all ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago) VarLogDistupgradeLspcitxt: VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 oct 9 20:46 seq crw-rw 1 root audio 116, 33 oct 9 20:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.27.0-0ubuntu5 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: CRDA: N/A CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-03-07 (948 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 hyperv_drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or
[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263
** Tags removed: verification-needed-jammy-linux-intel-iotg ** Tags added: verification-done-jammy-linux-intel-iotg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
** Tags removed: verification-needed-jammy-linux-intel-iotg ** Tags added: verification-done-jammy-linux-intel-iotg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can
** Tags removed: verification-needed-jammy-linux-intel-iotg ** Tags added: verification-done-jammy-linux-intel-iotg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263
As per previous communication, since we are using the generic kernel we will ignore this message -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263
As per previous communication, since we are using the generic kernel we will ignore this message -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
As per previous communication, since we are using the generic kernel we will ignore this message -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
As per previous communication, since we are using the generic kernel we will ignore this message -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can
As per previous communication, since we are using the generic kernel we will ignore this message -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can
As per previous communication, since we are using the generic kernel we will ignore this message -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263
Hi, we are using the generic kernel. Are linux-bluefield/5.15.0-1035.37 linux-raspi/5.15.0-1046.49 linux-azure/5.15.0-1056.64 relevant in our case? ** Changed in: linux (Ubuntu) Status: Confirmed => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
Hi, we are using the generic kernel. Are linux-bluefield/5.15.0-1035.37 linux-raspi/5.15.0-1046.49 linux-azure/5.15.0-1056.64 relevant in our case? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can
Hi, we are using the generic kernel. Are linux-bluefield/5.15.0-1035.37 linux-raspi/5.15.0-1046.49 linux-azure/5.15.0-1056.64 relevant in our case? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
Hfor https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386/comments/8 we have already performed the validation and changed the tag to verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can
@anthonywang, what about linux-intel-iotg? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
Hi, we are using the generic kernel - we recently tested the 5.15.0.94-generic. Is it the linux-ibm-gt-fips relevant in our case? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can
Hi, we are using the generic kernel - we recently tested the 5.15.0.94-generic. Is it the linux-ibm-gt-fips relevant in our case? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263
Hi, we are using the generic kernel - we recently tested the 5.15.0.94-generic. Is it the linux-ibm-gt-fips relevant in our case? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
Hi, we are using the generic kernel - we recently tested the 5.15.0.94-generic. Is it the linux-intel-iotg relevant in our case? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can
Hi, we are using the generic kernel - we recently tested the 5.15.0.94-generic. Is it the linux-intel-iotg relevant in our case? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263
Hi, we are using the generic kernel - we recently tested the 5.15.0.94-generic. Is it the linux-intel-iotg relevant in our case? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2050083] [NEW] generate and ship vmlinux.h to allow packages to build BPF CO-RE
Public bug reported: A vmlinux.h header generated from a kernel build with bpftool is needed to build and ship BPF CO-RE programs. We are looking to ship these in the next version of systemd. vmlinux.h being generated depends on the kernel version, architecture and kconfig. There are some vague promises of backward compatibility, but it is hard to gauge. We definitely do not want this file to be generated from the kernel running the build machine when building a package though, as very often these are very old and stable kernels building packages for the bleeding edge. In Fedora and now Debian we generate vmlinux.h at kernel package build time, and ship it with the other kernel headers (_not_ UAPI, the internal headers): https://salsa.debian.org/kernel- team/linux/-/commit/ac6f7eda4c3e8b0d0db20ad4bb8236371cf8d38e Please consider doing the same in Ubuntu's linux-headers. ** 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/2050083 Title: generate and ship vmlinux.h to allow packages to build BPF CO-RE Status in linux package in Ubuntu: New Bug description: A vmlinux.h header generated from a kernel build with bpftool is needed to build and ship BPF CO-RE programs. We are looking to ship these in the next version of systemd. vmlinux.h being generated depends on the kernel version, architecture and kconfig. There are some vague promises of backward compatibility, but it is hard to gauge. We definitely do not want this file to be generated from the kernel running the build machine when building a package though, as very often these are very old and stable kernels building packages for the bleeding edge. In Fedora and now Debian we generate vmlinux.h at kernel package build time, and ship it with the other kernel headers (_not_ UAPI, the internal headers): https://salsa.debian.org/kernel- team/linux/-/commit/ac6f7eda4c3e8b0d0db20ad4bb8236371cf8d38e Please consider doing the same in Ubuntu's linux-headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050083/+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 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
Gentle ping. Would love to see this fix in time for Noble's release. Thanks! ** Description changed: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Regression Potential] Moving a module from a less-common to a more-common package should not - have any negative side effects. + have any negative side effects. The main effect will be a little more + disk space used by the more common package, whether the module is in use + or not. There will also be more functionality available in the default + installation, which means a slightly increased surface and possibility + of new bugs in case it gets used. -- 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/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this
[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263
Hi, test with proposed 5.15.0-94.104 kernel was successfully performed ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
Hi, test with proposed 5.15.0-94.104 kernel was successfully performed ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can
Hi, test with proposed 5.15.0-94.104 kernel was successfully performed ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
** Description changed: SRU Justification [Impact] - The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops - VMs using these kernels from being configurable using qemu or cloud- - hypervisor's SMBIOS type 11 strings. This feature is supported and used - widely by systemd: + The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in + linux-modules-extra. This makes it hard to pull in via the linux-virtual + package, it can only come from the linux-generic one that also pulls in + the firmware and everything else needed for baremetal, and that serves + no purpose in a qemu VM. This stops VMs using these kernels from being + configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. + This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, - which uses Jammy, so it would be great to have this kconfig enabled and - backported. + which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ - -machine type=q35,accel=kvm,smm=on \ - -smp 2 \ - -m 1G \ - -cpu host \ - -nographic \ - -nodefaults \ - -serial mon:stdio \ - -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ - -device virtio-scsi-pci,id=scsi \ - -device scsi-hd,drive=hd,bootindex=1 \ - -smbios type=11,value=io.systemd.credential:mycred=supersecret + -machine type=q35,accel=kvm,smm=on \ + -smp 2 \ + -m 1G \ + -cpu host \ + -nographic \ + -nodefaults \ + -serial mon:stdio \ + -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ + -device virtio-scsi-pci,id=scsi \ + -device scsi-hd,drive=hd,bootindex=1 \ + -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] - Please consider enabling the following kconfigs: - - CONFIG_DMI_SYSFS + Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other - distros. + distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is + a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 - Without this kconfig, the directory won't be there. Once enabled, it - will be there. + Without this module installed and loaded, the directory won't be there. + Once enabled, it will be there. [Regression Potential] - Enabling a new DMI option could affect the DMI subsystem in unforeseen - ways. + Moving a module from a less-common to a more-common package should not + have any negative side effects. -- 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/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is
[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
Given this module doesn't really depend on firmware or anything, it would be a good candidate to be in linux-modules instead of linux- modules-extra. That way it will be pulled in without having to use the virtual package that depends on the firmware too. On Debian, Fedora and Archlinux it is a built-in. On OpenSUSE, it is a module installed by default. ** Summary changed: - linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support + linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-kvm (Ubuntu) ** No longer affects: linux-kvm (Ubuntu Jammy) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) 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/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+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 2045561] Re: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support
So it's a module: CONFIG_DMI_SYSFS=m and it's part of the modules-extra package. That means there's no way, without knowing the exact kernel version in advance, to pull that package in using linux-virtual. You'd have to use linux-generic, but that also pulls in all the firmware stuff. Can a solution be implemented to make this easier? Other distros have it as built-in. It could also be moved to the core package. Or linux- virtual could depend on the appropriate modules-extra package. -- 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/2045561 Title: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Jammy: Won't Fix Bug description: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2045561/+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 2045561] Re: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support
Got it, thank you -- 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/2045561 Title: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Jammy: Won't Fix Bug description: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2045561/+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 2045561] Re: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support
Thanks - what about Jammy? ** Changed in: linux-kvm (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: linux-kvm (Ubuntu Noble) Status: New => Won't Fix -- 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/2045561 Title: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Jammy: New Status in linux-kvm source package in Mantic: Won't Fix Status in linux-kvm source package in Noble: Won't Fix Bug description: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2045561/+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 2045561] Re: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support
** Description changed: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. + + For example: + + qemu-system-x86_64 \ + -machine type=q35,accel=kvm,smm=on \ + -smp 2 \ + -m 1G \ + -cpu host \ + -nographic \ + -nodefaults \ + -serial mon:stdio \ + -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ + -device virtio-scsi-pci,id=scsi \ + -device scsi-hd,drive=hd,bootindex=1 \ + -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. -- 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/2045561 Title: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Jammy: New Status in linux-kvm source package in Mantic: New Status in linux-kvm source package in Noble: New Bug description: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2045561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 2045561] [NEW] linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support
Public bug reported: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2045561 Title: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Jammy: New Status in linux-kvm source package in Mantic: New Status in linux-kvm source package in Noble: New Bug description: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2045561/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I don't think if that is the same issue, but I tried setting the automatic screen sleep to 1 minute and not always but most of the times I can't login back to the system since it does not wake up. The system is still functional, having nomachine installing and configured trying to login from another computer, I get a successfull connection with no video, since then, the system takes like 4/5 minutes to show a black screen with a cursor first, then the lockscreen and everything works again Ryzen 5 5600 and an AMD RX 7800 XT -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: Â Â MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
** Tags removed: verification-needed-focal-linux-aws-5.15 -- 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/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: In Progress Status in linux-kvm package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in linux-kvm source package in Kinetic: In Progress Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-kvm source package in Mantic: In Progress Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_INTEGRITY_MACHINE_KEYRING CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring implementation is patched to skip the check enabled by this kconfig) (The latter two are needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To verify whether this works, add a certificate to MOK, boot and check the content of the secondary keyring. The machine keyring should show up under it, and it should show the certificates loaded in MOK. E.g.: $ sudo keyctl show %:.secondary_trusted_keys Keyring  159454604 ---lswrv 0 0 keyring: .secondary_trusted_keys   88754641 ---lswrv 0 0 \_ keyring: .builtin_trusted_keys  889010778 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1  799434660 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f  541326986 ---lswrv 0 0 \_ keyring: .machine  188508854 ---lswrv 0 0 \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1  475039424 ---lswrv 0 0 \_ asymmetric: sb-bluca: Secure Boot Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479 [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: In Progress Status in linux-kvm package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-kvm source package in Jammy: In Progress Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in linux-kvm source package in Kinetic: In Progress Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: Fix Committed Status in linux-kvm source package in Lunar: In Progress Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-kvm source package in Mantic: In Progress Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
linux-generic looks good, thanks. Will the changes to linux-kvm and linux-azure be merged separately later? ** Tags removed: verification-needed-jammy verification-needed-lunar ** Tags added: verification-done-jammy verification-done-lunar -- 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/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: In Progress Status in linux-kvm package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-kvm source package in Jammy: In Progress Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in linux-kvm source package in Kinetic: In Progress Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: Fix Committed Status in linux-kvm source package in Lunar: In Progress Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-kvm source package in Mantic: In Progress Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
Hi, any update on these configs changes? Have they been queued? -- 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/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: In Progress Status in linux-kvm package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-kvm source package in Jammy: In Progress Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: In Progress Status in linux-kvm source package in Kinetic: In Progress Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-kvm source package in Lunar: In Progress Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-kvm source package in Mantic: In Progress Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
Thank you! Do you have details about the performance impact of IMA_ARCH? -- 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/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: In Progress Status in linux-kvm package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-kvm source package in Jammy: In Progress Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: In Progress Status in linux-kvm source package in Kinetic: In Progress Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-kvm source package in Lunar: In Progress Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-kvm source package in Mantic: In Progress Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
There's no specific log to share, I've downloaded the kconfig for the kvm flavour from the linux- buildinfo-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb package, extracted usr/lib/linux/6.2.0-1003-kvm/config and checked for these kconfigs, and they are not present: $ grep DM_VERITY config # CONFIG_DM_VERITY is not set $ grep IMA_ARCH config $ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-meta-azure source package in Jammy: New Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: New Status in linux-meta-azure source package in Kinetic: New Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: New Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
** Summary changed: - linux-kvm: please enable dm-verity kconfigs + linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images ** Also affects: linux-meta-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-kvm package in Ubuntu: New Bug description: The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-azure/+bug/2019040/+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 2019040] Re: linux-kvm: please enable dm-verity kconfigs
Also, please enable CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING on the cloud kernels - especially I am interested in the Azure one. Same reason as above - the other options are already enabled there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-kvm: please enable dm-verity kconfigs Status in linux-meta-kvm package in Ubuntu: New Bug description: The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-kvm/+bug/2019040/+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 2019040] [NEW] linux-kvm: please enable dm-verity kconfigs
Public bug reported: The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm- verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. ** Affects: linux-meta-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-kvm: please enable dm-verity kconfigs Status in linux-meta-kvm package in Ubuntu: New Bug description: The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-kvm/+bug/2019040/+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 2008111] Re: mt9m114 webcam sensor power-up failed
I can confirm that kernel 6.3-rc5 does load correctly the driver for mt9m114, however that's still not enough to use the webcam as /dev/video* devices do not get created at boot. Modules seem to load correctly. Maybe some more userspace work is needed in addition to the kernel driver? I have no idea on how to troubleshoot this further. Good news, audio is fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008111 Title: mt9m114 webcam sensor power-up failed Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: On my ASUS T100TAM (old Bay Trail 2-in-1 laptop) the webcam is the last non-working piece of hardware. The following dmesg snippet seems to suggest that the kernel needs a special config flag: [ 25.478178] atomisp_gmin_platform: module is from the staging directory, the quality is unknown, you have been warned. [ 25.478274] atomisp_gmin_platform: module verification failed: signature and/or required key missing - tainting kernel [ 25.508617] atomisp_mt9m114: module is from the staging directory, the quality is unknown, you have been warned. [ 25.649601] mt9m114 i2c-INT33F0:00: gmin: power management provided via Crystal Cove PMIC (i2c addr 0x6e) [ 25.649614] mt9m114 i2c-INT33F0:00: gmin_subdev_add: ACPI path is \_SB.I2C4.CAM0 [ 25.650170] mt9m114 i2c-INT33F0:00: Failed to find EFI variable INT33F0:00_ClkSrc [ 25.650176] mt9m114 i2c-INT33F0:00: ClkSrc: using default (1) [ 25.650508] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiPort' [ 25.650812] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiLanes' [ 25.650961] mt9m114 i2c-INT33F0:00: will handle gpio0 via ACPI [ 25.651048] mt9m114 i2c-INT33F0:00: will handle gpio1 via ACPI [ 25.651241] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable gmin_V1P8GPIO [ 25.651247] mt9m114 i2c-INT33F0:00: V1P8GPIO: using default (-1) [ 25.651440] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable gmin_V2P8GPIO [ 25.651445] mt9m114 i2c-INT33F0:00: V2P8GPIO: using default (-1) [ 25.651457] mt9m114 i2c-INT33F0:00: Will use CLK1 (pmc_plt_clk_1) [ 25.651472] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented [ 25.651475] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e reg-addr 0x5d value 0x63 mask 0xff [ 25.651480] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed to access I2C address 0x6e. Need to compile the kernel using CONFIG_*_PMIC_OPREGION settings [ 25.651572] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented [ 25.651575] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e reg-addr 0x5d value 0x62 mask 0xff [ 25.651579] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed to access I2C address 0x6e. Need to compile the kernel using CONFIG_*_PMIC_OPREGION settings [ 25.651659] mt9m114 i2c-INT33F0:00: sensor power-up failed [ 25.651691] INT33F0:00: mt9m114 power-up err Is this something that could be considered for the next kernels? Can I preview test it somehow? Keep in mind that this laptop is pretty slow... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 10:56:28 2023 InstallationDate: Installed on 2023-02-12 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008111/+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 2008111] Re: mt9m114 webcam sensor power-up failed
After further investigation, it seems the message is partially misleading. Power management for mt9m114 on ASUS T100 is indeed not implemented yet, but not because of a missing define - the necessary define is actually active in the kernel config. It is a kernel issue instead - apparently fixed by commit https://github.com/torvalds/linux/commit/73d15a7c13bfe1292db85ed3de8dfa711291819d which is not yet present in any mainline kernel (should be present in the next 6.3 release). As a cautionary warning though audio is broken in mainline kernel 6.2.1 so the whack-a-mole game for Bay Trail devices may continue even with the next kernel :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008111 Title: mt9m114 webcam sensor power-up failed Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: On my ASUS T100TAM (old Bay Trail 2-in-1 laptop) the webcam is the last non-working piece of hardware. The following dmesg snippet seems to suggest that the kernel needs a special config flag: [ 25.478178] atomisp_gmin_platform: module is from the staging directory, the quality is unknown, you have been warned. [ 25.478274] atomisp_gmin_platform: module verification failed: signature and/or required key missing - tainting kernel [ 25.508617] atomisp_mt9m114: module is from the staging directory, the quality is unknown, you have been warned. [ 25.649601] mt9m114 i2c-INT33F0:00: gmin: power management provided via Crystal Cove PMIC (i2c addr 0x6e) [ 25.649614] mt9m114 i2c-INT33F0:00: gmin_subdev_add: ACPI path is \_SB.I2C4.CAM0 [ 25.650170] mt9m114 i2c-INT33F0:00: Failed to find EFI variable INT33F0:00_ClkSrc [ 25.650176] mt9m114 i2c-INT33F0:00: ClkSrc: using default (1) [ 25.650508] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiPort' [ 25.650812] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiLanes' [ 25.650961] mt9m114 i2c-INT33F0:00: will handle gpio0 via ACPI [ 25.651048] mt9m114 i2c-INT33F0:00: will handle gpio1 via ACPI [ 25.651241] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable gmin_V1P8GPIO [ 25.651247] mt9m114 i2c-INT33F0:00: V1P8GPIO: using default (-1) [ 25.651440] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable gmin_V2P8GPIO [ 25.651445] mt9m114 i2c-INT33F0:00: V2P8GPIO: using default (-1) [ 25.651457] mt9m114 i2c-INT33F0:00: Will use CLK1 (pmc_plt_clk_1) [ 25.651472] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented [ 25.651475] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e reg-addr 0x5d value 0x63 mask 0xff [ 25.651480] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed to access I2C address 0x6e. Need to compile the kernel using CONFIG_*_PMIC_OPREGION settings [ 25.651572] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented [ 25.651575] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e reg-addr 0x5d value 0x62 mask 0xff [ 25.651579] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed to access I2C address 0x6e. Need to compile the kernel using CONFIG_*_PMIC_OPREGION settings [ 25.651659] mt9m114 i2c-INT33F0:00: sensor power-up failed [ 25.651691] INT33F0:00: mt9m114 power-up err Is this something that could be considered for the next kernels? Can I preview test it somehow? Keep in mind that this laptop is pretty slow... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 10:56:28 2023 InstallationDate: Installed on 2023-02-12 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008111/+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 2008111] [NEW] mt9m114 webcam sensor power-up failed
Public bug reported: On my ASUS T100TAM (old Bay Trail 2-in-1 laptop) the webcam is the last non-working piece of hardware. The following dmesg snippet seems to suggest that the kernel needs a special config flag: [ 25.478178] atomisp_gmin_platform: module is from the staging directory, the quality is unknown, you have been warned. [ 25.478274] atomisp_gmin_platform: module verification failed: signature and/or required key missing - tainting kernel [ 25.508617] atomisp_mt9m114: module is from the staging directory, the quality is unknown, you have been warned. [ 25.649601] mt9m114 i2c-INT33F0:00: gmin: power management provided via Crystal Cove PMIC (i2c addr 0x6e) [ 25.649614] mt9m114 i2c-INT33F0:00: gmin_subdev_add: ACPI path is \_SB.I2C4.CAM0 [ 25.650170] mt9m114 i2c-INT33F0:00: Failed to find EFI variable INT33F0:00_ClkSrc [ 25.650176] mt9m114 i2c-INT33F0:00: ClkSrc: using default (1) [ 25.650508] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiPort' [ 25.650812] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiLanes' [ 25.650961] mt9m114 i2c-INT33F0:00: will handle gpio0 via ACPI [ 25.651048] mt9m114 i2c-INT33F0:00: will handle gpio1 via ACPI [ 25.651241] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable gmin_V1P8GPIO [ 25.651247] mt9m114 i2c-INT33F0:00: V1P8GPIO: using default (-1) [ 25.651440] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable gmin_V2P8GPIO [ 25.651445] mt9m114 i2c-INT33F0:00: V2P8GPIO: using default (-1) [ 25.651457] mt9m114 i2c-INT33F0:00: Will use CLK1 (pmc_plt_clk_1) [ 25.651472] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented [ 25.651475] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e reg-addr 0x5d value 0x63 mask 0xff [ 25.651480] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed to access I2C address 0x6e. Need to compile the kernel using CONFIG_*_PMIC_OPREGION settings [ 25.651572] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented [ 25.651575] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e reg-addr 0x5d value 0x62 mask 0xff [ 25.651579] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed to access I2C address 0x6e. Need to compile the kernel using CONFIG_*_PMIC_OPREGION settings [ 25.651659] mt9m114 i2c-INT33F0:00: sensor power-up failed [ 25.651691] INT33F0:00: mt9m114 power-up err Is this something that could be considered for the next kernels? Can I preview test it somehow? Keep in mind that this laptop is pretty slow... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 10:56:28 2023 InstallationDate: Installed on 2023-02-12 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Dmesg log" https://bugs.launchpad.net/bugs/2008111/+attachment/5649152/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008111 Title: mt9m114 webcam sensor power-up failed Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: On my ASUS T100TAM (old Bay Trail 2-in-1 laptop) the webcam is the last non-working piece of hardware. The following dmesg snippet seems to suggest that the kernel needs a special config flag: [ 25.478178] atomisp_gmin_platform: module is from the staging directory, the quality is unknown, you have been warned. [ 25.478274] atomisp_gmin_platform: module verification failed: signature and/or required key missing - tainting kernel [ 25.508617] atomisp_mt9m114: module is from the staging directory, the quality is unknown, you have been warned. [ 25.649601] mt9m114 i2c-INT33F0:00: gmin: power management provided via Crystal Cove PMIC (i2c addr 0x6e) [ 25.649614] mt9m114 i2c-INT33F0:00: gmin_subdev_add: ACPI path is \_SB.I2C4.CAM0 [ 25.650170] mt9m114 i2c-INT33F0:00: Failed to find EFI variable INT33F0:00_ClkSrc [ 25.650176] mt9m114 i2c-INT33F0:00: ClkSrc: using default (1) [ 25.650508] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiPort' [ 25.650812] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiLanes' [ 25.650961] mt9m114 i2c-INT33F0:00: will handle gpio0 via ACPI [ 25.651048] mt9m114 i2c-INT33F0:00: will handle gpio1 via ACPI [ 25.651241] mt9m114
[Kernel-packages] [Bug 1788928] Re: psmouse: after sleep/suspend thinkpad touchpad not functional
*** This bug is a duplicate of bug 1786574 *** https://bugs.launchpad.net/bugs/1786574 Same issue with my Thinkpad X240 with Ubuntu 22.04.1 Workaround `sudo modprobe -r psmouse; sudo modprobe psmouse` still work -- 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/1788928 Title: psmouse: after sleep/suspend thinkpad touchpad not functional Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Summary: The touchpad after sleep/suspend of my ThinkPad X1 will not function correctly. Expected Behavior: After sleep/suspend scroll works correctly. Actual Behavior: Unable to scroll or correctly click on a window and move it without reloading the driver Steps to reproduce: 1. Install Bionic on Thinkpad X1 (4.15.0-32-generic) 2. Open something to scroll (e.g. browser, terminal, etc.) 3. Close lid 4. Re-open lid once sleeping/suspended 5. Try to scroll and note that it does not work Workaround: Run the following after re-opening the lid $ sudo modprobe psmouse -r; sudo modprobe psmouse dmesg on reload: [12753.847050] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [12753.879362] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [12753.879375] psmouse serio1: synaptics: Trying to set up SMBus access [12753.882246] psmouse serio1: synaptics: SMbus companion is not ready yet [12753.944774] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 1795685 [12753.944791] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [12753.985102] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24 [12754.619594] psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [12754.823238] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio5/input/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2506 F pulseaudio /dev/snd/controlC0: powersj2506 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (185 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788928/+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 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)
I have the same problem: thermal thermal_zone6: failed to read out thermal zone (-61) lenovo Thinkpad X1 Carbon 9th Gen Ubuntu 20.04 Kernel 5.14.0-1032-oem Firmware 1.187.29 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1803881 Title: thermal thermal_zone4: failed to read out thermal zone (-61) Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Bug description: Thermald can't read zone4. It's making my fan go crazy, this issue seems to be a bit more controlled in 18.10. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic sudo apt-cache policy thermald thermald: Installed: 1.7.0-5ubuntu1 Candidate: 1.7.0-5ubuntu1 Version table: *** 1.7.0-5ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status cat /sys/class/thermal/thermal_zone4/type iwlwifi find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \; /sys/class/thermal/thermal_zone4/uevent /sys/class/thermal/thermal_zone4/trip_point_5_temp -32768000 /sys/class/thermal/thermal_zone4/trip_point_3_type passive /sys/class/thermal/thermal_zone4/trip_point_4_temp -32768000 /sys/class/thermal/thermal_zone4/trip_point_2_type passive /sys/class/thermal/thermal_zone4/power/runtime_active_time 0 /sys/class/thermal/thermal_zone4/power/runtime_active_kids 0 /sys/class/thermal/thermal_zone4/power/runtime_usage 0 /sys/class/thermal/thermal_zone4/power/runtime_status unsupported /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms: Input/output error /sys/class/thermal/thermal_zone4/power/async disabled /sys/class/thermal/thermal_zone4/power/runtime_suspended_time 0 /sys/class/thermal/thermal_zone4/power/runtime_enabled disabled /sys/class/thermal/thermal_zone4/power/control auto /sys/class/thermal/thermal_zone4/available_policies power_allocator user_space bang_bang fair_share step_wise /sys/class/thermal/thermal_zone4/policy step_wise /sys/class/thermal/thermal_zone4/trip_point_3_temp -32768000 /sys/class/thermal/thermal_zone4/trip_point_1_type passive /sys/class/thermal/thermal_zone4/k_d cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error /sys/class/thermal/thermal_zone4/sustainable_power cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error /sys/class/thermal/thermal_zone4/type iwlwifi /sys/class/thermal/thermal_zone4/trip_point_7_type passive /sys/class/thermal/thermal_zone4/offset cat: /sys/class/thermal/thermal_zone4/offset: Input/output error /sys/class/thermal/thermal_zone4/slope cat: /sys/class/thermal/thermal_zone4/slope: Input/output error /sys/class/thermal/thermal_zone4/trip_point_2_temp -32768000 /sys/class/thermal/thermal_zone4/trip_point_0_type passive /sys/class/thermal/thermal_zone4/trip_point_6_type passive /sys/class/thermal/thermal_zone4/emul_temp cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied /sys/class/thermal/thermal_zone4/k_po cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error /sys/class/thermal/thermal_zone4/integral_cutoff cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error /sys/class/thermal/thermal_zone4/k_i cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error /sys/class/thermal/thermal_zone4/trip_point_1_temp -32768000 /sys/class/thermal/thermal_zone4/k_pu cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error /sys/class/thermal/thermal_zone4/temp 46000 /sys/class/thermal/thermal_zone4/trip_point_7_temp -32768000 /sys/class/thermal/thermal_zone4/trip_point_5_type passive /sys/class/thermal/thermal_zone4/trip_point_0_temp -32768000 /sys/class/thermal/thermal_zone4/trip_point_6_temp -32768000 /sys/class/thermal/thermal_zone4/trip_point_4_type passive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803881/+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 1966989] [NEW] Suspend mode drains battery activating fan
Public bug reported: I have a new thinkpad carbion x1 9th Gen with ubuntu 20.04. Everything works excellently a part suspend. If I suspend either using the command or closing the lid, after a while fan starts spinning and battery is draining fast. I have seen that other people have found the same problem. I do not know if there is a bug fix or a viable workaround. lsb_release -rd Description:Ubuntu 20.04.4 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34 ProcVersionSignature: Ubuntu 5.14.0-1031.34-oem 5.14.21 Uname: Linux 5.14.0-1031-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 19:29:41 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-20 (9 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal lenovo third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966989 Title: Suspend mode drains battery activating fan Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: I have a new thinkpad carbion x1 9th Gen with ubuntu 20.04. Everything works excellently a part suspend. If I suspend either using the command or closing the lid, after a while fan starts spinning and battery is draining fast. I have seen that other people have found the same problem. I do not know if there is a bug fix or a viable workaround. lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34 ProcVersionSignature: Ubuntu 5.14.0-1031.34-oem 5.14.21 Uname: Linux 5.14.0-1031-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 19:29:41 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-03-20 (9 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1966989/+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 1965286] Re: hp stream 13 doesn't resume after suspend to ram (regression)
After filing the bug report, I tried to remove the input_leds module (the only one that had a resemblance to the reported "input" in /sys/powear/pm_trace_dev_match), still it doesn't resume. -- 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/1965286 Title: hp stream 13 doesn't resume after suspend to ram (regression) Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded from 18.04 lts to 20.04 lts then to 21.10. On 18.04 resume after suspend worked, with 21.10 it doesn't (after pressing the power button the power led turns on but the screen stays black, no matter if before suspend it was in X, wayland or a console). I didn't test with 20.04 (but I tried booting its kernel, same result). I tried to follow the steps in https://wiki.ubuntu.com/DebuggingKernel/Suspend but I cannot find any "hash matches" in dmesg and /sys/powear/pm_trace_dev_match says "input". I tried with the mainline kernel (5.16) same result. I also tried to install the kernel from 18.04 (4.15.0-172) but it panics saying it cannot find the root partition. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-35-generic 5.13.0-35.40 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1005 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 11:15:00 2022 HibernationDevice: RESUME=UUID=d2a3724a-3233-4081-a1e2-542ee08c68f2 InstallationDate: Installed on 2016-03-06 (2201 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216c Broadcom Corp. BCM43142A0 Bluetooth Device Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. HP Truevision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream Notebook PC 13 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=f8b20c7d-bd75-42eb-8a39-4cb262d6e1e4 ro RelatedPackageVersions: linux-restricted-modules-5.13.0-35-generic N/A linux-backports-modules-5.13.0-35-generic N/A linux-firmware 1.201.5 SourcePackage: linux StagingDrivers: atomisp_gmin_platform atomisp_lm3554 UpgradeStatus: Upgraded to impish on 2022-03-16 (0 days ago) dmi.bios.date: 09/25/2015 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 802A dmi.board.vendor: HP dmi.board.version: 56.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 56.33 dmi.modalias: dmi:bvnInsyde:bvrF.17:bd09/25/2015:br15.23:efr56.33:svnHP:pnHPStreamNotebookPC13:pvrType1-ProductConfigId:rvnHP:rn802A:rvr56.21:cvnHP:ct10:cvrChassisVersion:skuP3Y01EA#ABE: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=STR X=Null dmi.product.name: HP Stream Notebook PC 13 dmi.product.sku: P3Y01EA#ABE dmi.product.version: Type1 - ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965286/+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 1965286] [NEW] hp stream 13 doesn't resume after suspend to ram (regression)
Public bug reported: I just upgraded from 18.04 lts to 20.04 lts then to 21.10. On 18.04 resume after suspend worked, with 21.10 it doesn't (after pressing the power button the power led turns on but the screen stays black, no matter if before suspend it was in X, wayland or a console). I didn't test with 20.04 (but I tried booting its kernel, same result). I tried to follow the steps in https://wiki.ubuntu.com/DebuggingKernel/Suspend but I cannot find any "hash matches" in dmesg and /sys/powear/pm_trace_dev_match says "input". I tried with the mainline kernel (5.16) same result. I also tried to install the kernel from 18.04 (4.15.0-172) but it panics saying it cannot find the root partition. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-35-generic 5.13.0-35.40 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1005 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 11:15:00 2022 HibernationDevice: RESUME=UUID=d2a3724a-3233-4081-a1e2-542ee08c68f2 InstallationDate: Installed on 2016-03-06 (2201 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216c Broadcom Corp. BCM43142A0 Bluetooth Device Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. HP Truevision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream Notebook PC 13 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=f8b20c7d-bd75-42eb-8a39-4cb262d6e1e4 ro RelatedPackageVersions: linux-restricted-modules-5.13.0-35-generic N/A linux-backports-modules-5.13.0-35-generic N/A linux-firmware 1.201.5 SourcePackage: linux StagingDrivers: atomisp_gmin_platform atomisp_lm3554 UpgradeStatus: Upgraded to impish on 2022-03-16 (0 days ago) dmi.bios.date: 09/25/2015 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 802A dmi.board.vendor: HP dmi.board.version: 56.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 56.33 dmi.modalias: dmi:bvnInsyde:bvrF.17:bd09/25/2015:br15.23:efr56.33:svnHP:pnHPStreamNotebookPC13:pvrType1-ProductConfigId:rvnHP:rn802A:rvr56.21:cvnHP:ct10:cvrChassisVersion:skuP3Y01EA#ABE: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=STR X=Null dmi.product.name: HP Stream Notebook PC 13 dmi.product.sku: P3Y01EA#ABE dmi.product.version: Type1 - ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish staging -- 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/1965286 Title: hp stream 13 doesn't resume after suspend to ram (regression) Status in linux package in Ubuntu: New Bug description: I just upgraded from 18.04 lts to 20.04 lts then to 21.10. On 18.04 resume after suspend worked, with 21.10 it doesn't (after pressing the power button the power led turns on but the screen stays black, no matter if before suspend it was in X, wayland or a console). I didn't test with 20.04 (but I tried booting its kernel, same result). I tried to follow the steps in https://wiki.ubuntu.com/DebuggingKernel/Suspend but I cannot find any "hash matches" in dmesg and /sys/powear/pm_trace_dev_match says "input". I tried with the mainline kernel (5.16) same result. I also tried to install the kernel from 18.04 (4.15.0-172) but it panics saying it cannot find the root partition. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-35-generic 5.13.0-35.40 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: luca 1005 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 11:15:00 2022 HibernationDevice: RESUME=UUID=d2a3724a-3233-4081-a1e2-542ee08c68f2 InstallationDate: Installed on 2016-03-06 (2201 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216c Broadcom Corp. BCM43142A0 Bluetooth Device Bus 001 Device 003: ID 05e3
[Kernel-packages] [Bug 1875015] Re: Displaylink is extremely slow
I just updated my ubuntu 21.10 with normal apt software updates and the issues is here again. It used to work well since beginning of December 2021 Linux 5.13.0-35-generic #40-Ubuntu SMP Mon Mar 7 08:03:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1961771] Re: Enable CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in Jammy
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961771 Title: Enable CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in Jammy Status in linux package in Ubuntu: Confirmed Bug description: [Impact] The CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT option allows to support pretimeout actions on device drivers without the hardware capability to support it. It was introduced in Linux 5.14: https://github.com/torvalds/linux/commit/7b7d2fdc8c3e3f9fdb3558d674e1eeddc16c7d9e It is now enabled in Debian: https://salsa.debian.org/kernel- team/linux/-/commit/d09d223632f0505c3a82dc77d6f70e120002a221 More information about watchdog pretimeouts: https://elinux.org/Tests:Watchdog-Pretimeout We are adding support for this feature in systemd: https://github.com/systemd/systemd/pull/19970 More specifically, if it was enabled in Jammy, we could add an upstream autopkgtest case using qemu to cover this functionality, which is not tested at all currently, when we rebase our autopkgtest image from Focal to Jammy. [Test Plan] To verify that this is working, simply boot Qemu with '-device i6300esb,id=watchdog0 -watchdog-action reset' then check the available governors: modprobe pretimeout_noop cat /sys/class/watchdog/watchdog0/pretimeout_available_governors [Where problems could occur] The feature is disabled by default, as the modules have to be manually loaded, so chance of side effects for general users is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961771/+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 1961771] [NEW] Enable CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in Jammy
Public bug reported: [Impact] The CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT option allows to support pretimeout actions on device drivers without the hardware capability to support it. It was introduced in Linux 5.14: https://github.com/torvalds/linux/commit/7b7d2fdc8c3e3f9fdb3558d674e1eeddc16c7d9e It is now enabled in Debian: https://salsa.debian.org/kernel- team/linux/-/commit/d09d223632f0505c3a82dc77d6f70e120002a221 More information about watchdog pretimeouts: https://elinux.org/Tests:Watchdog-Pretimeout We are adding support for this feature in systemd: https://github.com/systemd/systemd/pull/19970 More specifically, if it was enabled in Jammy, we could add an upstream autopkgtest case using qemu to cover this functionality, which is not tested at all currently, when we rebase our autopkgtest image from Focal to Jammy. [Test Plan] To verify that this is working, simply boot Qemu with '-device i6300esb,id=watchdog0 -watchdog-action reset' then check the available governors: modprobe pretimeout_noop cat /sys/class/watchdog/watchdog0/pretimeout_available_governors [Where problems could occur] The feature is disabled by default, as the modules have to be manually loaded, so chance of side effects for general users is very low. ** 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/1961771 Title: Enable CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in Jammy Status in linux package in Ubuntu: New Bug description: [Impact] The CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT option allows to support pretimeout actions on device drivers without the hardware capability to support it. It was introduced in Linux 5.14: https://github.com/torvalds/linux/commit/7b7d2fdc8c3e3f9fdb3558d674e1eeddc16c7d9e It is now enabled in Debian: https://salsa.debian.org/kernel- team/linux/-/commit/d09d223632f0505c3a82dc77d6f70e120002a221 More information about watchdog pretimeouts: https://elinux.org/Tests:Watchdog-Pretimeout We are adding support for this feature in systemd: https://github.com/systemd/systemd/pull/19970 More specifically, if it was enabled in Jammy, we could add an upstream autopkgtest case using qemu to cover this functionality, which is not tested at all currently, when we rebase our autopkgtest image from Focal to Jammy. [Test Plan] To verify that this is working, simply boot Qemu with '-device i6300esb,id=watchdog0 -watchdog-action reset' then check the available governors: modprobe pretimeout_noop cat /sys/class/watchdog/watchdog0/pretimeout_available_governors [Where problems could occur] The feature is disabled by default, as the modules have to be manually loaded, so chance of side effects for general users is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961771/+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 1957005] Re: keyboard and touchpad stopped working
it was an hardware issue ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Assignee: (unassigned) => Luca Bianchi (luca.bianchi.91) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1957005 Title: keyboard and touchpad stopped working Status in linux-signed-hwe-5.11 package in Ubuntu: Invalid Bug description: Onboard Keyboard and touchpad stopped working, but I notice that the Brightness controls (FN+F2/F3) still work. External USB keyboard and mouse work properly. luca@luca-SATELLITE-L850-1PD:~$ uname -a Linux luca-SATELLITE-L850-1PD 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 10 21:27:14 2022 InstallationDate: Installed on 2020-05-26 (594 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1957005/+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 1957005] [NEW] keyboard and touchpad stopped working
Public bug reported: Onboard Keyboard and touchpad stopped working, but I notice that the Brightness controls (FN+F2/F3) still work. External USB keyboard and mouse work properly. luca@luca-SATELLITE-L850-1PD:~$ uname -a Linux luca-SATELLITE-L850-1PD 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 10 21:27:14 2022 InstallationDate: Installed on 2020-05-26 (594 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "/proc/bus/input/devices" https://bugs.launchpad.net/bugs/1957005/+attachment/5553150/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1957005 Title: keyboard and touchpad stopped working Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Onboard Keyboard and touchpad stopped working, but I notice that the Brightness controls (FN+F2/F3) still work. External USB keyboard and mouse work properly. luca@luca-SATELLITE-L850-1PD:~$ uname -a Linux luca-SATELLITE-L850-1PD 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 10 21:27:14 2022 InstallationDate: Installed on 2020-05-26 (594 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1957005/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Nice write up, I am back to my evdi device from a week and is working flawless now. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Hi, I am on 21.10 with intel driver and latest displaylink from their website. Everything used to work decently until a couple of day ago when I started seeing the external monitor very slow. I was on 21.04 and after an update it has started being slow. 1. It is slower when more things change on the screen, only the mouse works slow a full screen rendering is unusably slow. 2. on the login screen the screen works very well, as I was used to. 3. Audio work fine, rendering is very slow About my pc 1. Linux vin 5.13.0-20-generic #20-Ubuntu SMP Fri Oct 15 14:21:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 2. Driver from display link displaylink-driver-5.4.1-55.174 3. Tried X11 and Wayland from GDM with Gnome I tried to troubleshoot as described here https://wiki.archlinux.org/title/DisplayLink and setting LIBGL_DRI3_DISABLE=true as said here but it does not change Any hint is appreciated! Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
if anyone have a problem with oserror, as advice by HÃ¥kon VÃ¥gsether (haakov) check 1 sec wait solution, another way that worked for me, i have edit .service before start the install and changed the line 7 from Type=simple to Type=idle, in fact man define: Behavior of idle is very similar to simple; however, actual execution of the service program is delayed until all active jobs are dispatched. This may be used to avoid interleaving of output of shell services with the status output on the console. Note that this type is useful only to improve console output, it is not useful as a general unit ordering tool, and the effect of this service type is subject to a 5s timeout, after which the service program is invoked anyway. Thank you Badaoui Mohamed (mohamed-badaoui),Logix (logix2) and HÃ¥kon VÃ¥gsether (haakov) -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Thank you to all, with this instructions here https://www.linuxuprising.com/2021/05/how-to-get-numpad-embedded-into.html work perfectly on fresh arch. one little bug, tray icon numpad (plasma) will be removed only after a double on-off Thank you -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1909005] Re: Ubuntu does not resume (wake up) from suspend
Same problem on Dell Inspiron 5558 with - latest bios - Ubuntu 5.8.0-53-generic #60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- 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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux-image-5.0.0-1070 -oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
No anyone can help me. -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Sorry but every times that i restart pc numpad not work, there are any error in startup phase: File "/usr/bin/asus_touchpad_numpad.py", line147, in for e in d_t.events(): File "usr/lib/python3.9/site-packages/libevdev/device.py", line 536, in events ev=self._libevdev.next_event(flags) File "usr/lib/python3.9/site-packages/libevdev/_clib.py", line 893, in next_event raise OSError(-rc, os.strerror(-rc)) OSError:[Errno19] No such device Can you help me? -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
i forget after install python pip i send command: sudo pip3 install libevdev after i reinstalled install.sh and now work very good. -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Solved i installed python-pip too. after relaunch install.sh and now work very good. Thank you to all -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
sudo ./install.sh Testing interface i2c-1 : sucess Does your numpad has % and = symbols [N/y] Your numpad has no extra symbols. Copy asus python driver to /usr/bin/asus_touchpad_numpad.py Add asus touchpad service in /lib/systemd/system/ Asus touchpad service enabled Asus touchpad service started -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
and this is grep command : [spix@spix ux433-touchpad-numpad]$ grep -B1 -A5 -i -E "(elan|asu)" /proc/bus/input/devices I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input10 U: Uniq= H: Handlers=kbd event10 rfkill B: PROP=0 B: EV=100013 B: KEY=10008 0 0 0 0 181606f0090 8280027801701000 e 0 -- I: Bus=0018 Vendor=04f3 Product=30dc Version=0100 N: Name="ELAN1401:00 04F3:30DC Mouse" P: Phys=i2c-ELAN1401:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1401:00/0018:04F3:30DC.0001/input/input13 U: Uniq= H: Handlers=event7 mouse0 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 -- I: Bus=0018 Vendor=04f3 Product=30dc Version=0100 N: Name="ELAN1401:00 04F3:30DC Touchpad" P: Phys=i2c-ELAN1401:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1401:00/0018:04F3:30DC.0001/input/input14 U: Uniq= H: Handlers=event11 mouse1 B: PROP=5 B: EV=1b B: KEY=e520 1 0 0 0 0 -- I: Bus=0018 Vendor=04f3 Product=30dc Version=0100 N: Name="ELAN1401:00 04F3:30DC Keyboard" P: Phys=i2c-ELAN1401:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1401:00/0018:04F3:30DC.0001/input/input15 U: Uniq= H: Handlers=sysrq kbd leds event12 B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdfffef fffe -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Hi Sirs, I have a ux433fn not work for me can you help me? there is an error in service, i have a fresh install of Archlinux. [spix@spix ux433-touchpad-numpad]$ systemctl status asus_touchpad_numpad.service × asus_touchpad_numpad.service - Asus Touchpad to Numpad Handler Loaded: loaded (/usr/lib/systemd/system/asus_touchpad_numpad.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2021-04-22 23:39:44 CEST; 9min ago Process: 2505 ExecStart=/usr/bin/python3 /usr/bin/asus_touchpad_numpad.py (code=exited, status=1/FAILURE) Main PID: 2505 (code=exited, status=1/FAILURE) CPU: 24ms apr 22 23:39:44 spix systemd[1]: Started Asus Touchpad to Numpad Handler. apr 22 23:39:44 spix systemd[1]: asus_touchpad_numpad.service: Main process exited, code=exited, status=1/FAILURE apr 22 23:39:44 spix systemd[1]: asus_touchpad_numpad.service: Failed with result 'exit-code'. Installation of the script work perfectly, with no error -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1905975] Re: kernel: Enable CONFIG_BPF_LSM on Ubuntu
FYI, Debian 11 will ship with BPF_LSM built in, but disabled by default (by explicitly setting CONFIG_LSM to the desired list) -- 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/1905975 Title: kernel: Enable CONFIG_BPF_LSM on Ubuntu Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: == Impact == Enabling CONFIG_BPF_LSM in the KConfig of Ubuntu Kernels, allowing users to use BPF LSM programs. == Background == The BPF LSM was merged into the Linux kernel 5.7 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=641cd7b06c911c5935c34f24850ea18690649917 https://outflux.net/blog/archives/2020/09/21/security-things-in- linux-v5-7 It allows users to implement MAC and Audit Policies using BPF programs. As a follow-up from the interest generated by the LSM on BPF/Linux conferences and on request from users, we’d like to request the enabling of CONFIG_BPF_LSM on Ubuntu starting with H. The LSM won't be added to the list of active LSMs by default (in CONFIG_LSM or lsm= on the boot parameters) yet, as it adds an indirect function call overhead by registering an empty LSM hook for all hooks. However enabling it in the kernel config will support users who wish to use BPF LSM programs without needing to replace their kernel image. The LSM can be made "active" by default when our work on getting rid of this overhead is merged in the kernel: https://lore.kernel.org/bpf/20200820164753.3256899-1-jackm...@chromium.org == Regression Potential == None. The LSM is not active by default, so it does not have any performance or functional regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905975/+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 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
This has effected me as well. I have a Lenovo X1 Carbon with Nvidia GTX 1650. New Ubuntu 20.04 install. When I boot up, the built-in screen does not work and it hangs with the Lenovo and Ubuntu logo. When I boot up with an external monitor via HDMI, it boots up BUT build- in screen does not work. If I use the Inter Drivers (radio button in the NVIDIA X Server app) it will boot with the built-in screen working BUT not HDMI / DP working. -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1872375] [NEW] AMDGPU driver crashes when resuming from sleep if a ffmpeg-vaapi encoding backend is being used
Public bug reported: Good morning, I'm writing this because is pretty much easily reproduceable in this hardware I discovered this when I set up an automatic permanent replay-recording in OBS, using FFMPEG VAAPI backend I usually put the system to sleep, and pretty much 100% of the times so far when OBS is recording something AND is using the ffmpeg-vaapi backend, putting the system to sleep and then waking it back, causes the amdgpu driver to crash no matter what Any other sleep/standby test made without recording using ffmpeg-vaapi (even using default ffmpeg software x264 backend) has not made the driver crash so far My setup: CPU: AMD Ryzen 5 1600 GPU: AMD Sapphire RX 580 8GB RAM: 12GB DDR4 (3x4GB) System: Ubuntu 20.04 Focal Fossa Desktop: GNOME 3.36.1 Kernel: 5.4.0-21-generic #25-Ubuntu Display server: X.org Here is the system crashing logs dmesg (Don't mind the hostname, it's a desktop PC not a thinkpad) Apr 13 01:49:02 haru-ThinkPad-T440s kernel: [ 64.100393] PM: suspend entry (deep) Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.108441] Filesystems sync: 0.008 seconds Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.108716] Freezing user space processes ... (elapsed 0.002 seconds) done. Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.111290] OOM killer disabled. Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.111291] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.112125] printk: Suspending console(s) (use no_console_suspend to debug) Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.113085] serial 00:04: disabled Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.113317] parport_pc 00:03: disabled Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151545] sd 0:0:0:0: [sda] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151713] sd 1:0:0:0: [sdc] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151720] sd 10:0:0:0: [sdd] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151724] sd 11:0:0:0: [sdb] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151807] sd 0:0:0:0: [sda] Stopping disk Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.152043] sd 1:0:0:0: [sdc] Stopping disk Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.157544] sd 10:0:0:0: [sdd] Stopping disk Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.612461] ACPI: Preparing to enter system sleep state S3 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.925094] PM: Saving platform NVS memory Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.925117] Disabling non-boot CPUs ... Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.927049] smpboot: CPU 1 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.931788] smpboot: CPU 2 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.934941] IRQ 37: no longer affine to CPU3 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.935968] smpboot: CPU 3 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.940098] smpboot: CPU 4 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.943503] IRQ 27: no longer affine to CPU5 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.943510] IRQ 28: no longer affine to CPU5 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.944533] smpboot: CPU 5 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.947662] IRQ 44: no longer affine to CPU6 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.948697] smpboot: CPU 6 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.952180] IRQ 30: no longer affine to CPU7 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.953216] smpboot: CPU 7 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.957820] smpboot: CPU 8 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.961177] IRQ 39: no longer affine to CPU9 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.961187] IRQ 63: no longer affine to CPU9 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.962201] smpboot: CPU 9 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.965160] IRQ 40: no longer affine to CPU10 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.966184] smpboot: CPU 10 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.970189] smpboot: CPU 11 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.973487] ACPI: Low-level resume complete Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.973535] PM: Restoring platform NVS memory Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.974097] Enabling non-boot CPUs ... Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.974142] x86: Booting SMP configuration: Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.974143] smpboot: Booting Node 0 Processor 1 APIC 0x1 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.974267] microcode: CPU1:
[Kernel-packages] [Bug 1868169] Re: Cannot build nvidia driver via dkms because compiler doesn't match kernel
solved with latest version ubuntu@ip-172-31-5-176:~$ uname -a Linux ip-172-31-5-176 4.15.0-1065-aws #69-Ubuntu SMP Thu Mar 26 02:17:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-172-31-5-176:~$ cat /proc/version Linux version 4.15.0-1065-aws (buildd@lgw01-amd64-035) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #69-Ubuntu SMP Thu Mar 26 02:17:29 UTC 2020 ubuntu@ip-172-31-5-176:~$ gcc --version gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- 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/1868169 Title: Cannot build nvidia driver via dkms because compiler doesn't match kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The same as this issue https://bugs.launchpad.net/ubuntu/+source/gcc- defaults/+bug/1608753 but on 18.04 relevant output from /var/lib/dkms/nvidia/440.33.01/build/make.log: Compiler version check failed: The major and minor number of the compiler used to compile the kernel: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) does not match the compiler used here: cc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. It is recommended to set the CC environment variable to the compiler that was used to compile the kernel. The compiler version check can be disabled by setting the IGNORE_CC_MISMATCH environment variable to "1". However, mixing compiler versions between the kernel and kernel modules can result in subtle bugs that are difficult to diagnose. *** Failed CC version check. Bailing out! *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868169/+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 1827428] Re: Mouse cursor left frozen copy of itself
This also occurs in Fedora 32 and Xfce 4.14 for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+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 1846016]
*** Bug 204153 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1846016 Title: Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD GEO_TX_POWER_LIMIT Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since yesterday. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.182 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 30 20:57:08 2019 Dependencies: InstallationDate: Installed on 2019-07-23 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago) -- Also found on Ubuntu-certified HP EliteDesk 800 G3 DM. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+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 1846016]
*** Bug 205163 has been marked as a duplicate of this bug. *** -- 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/1846016 Title: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Bug description: I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since yesterday. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.182 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 30 20:57:08 2019 Dependencies: InstallationDate: Installed on 2019-07-23 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago) -- Also found on Ubuntu-certified HP EliteDesk 800 G3 DM. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+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 1846016]
Here's the patch that was sent upstream: https://lore.kernel.org/linux-wireless/20191009094853.PfIm3J8o7DN_Femup- OXkJdtmKE7rftk1ODkm7cx-vk@z/ -- 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/1846016 Title: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Bug description: I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since yesterday. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.182 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 30 20:57:08 2019 Dependencies: InstallationDate: Installed on 2019-07-23 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago) -- Also found on Ubuntu-certified HP EliteDesk 800 G3 DM. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+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 1846016]
Thanks for confirming, You-Sheng! -- 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/1846016 Title: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Bug description: I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since yesterday. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.182 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 30 20:57:08 2019 Dependencies: InstallationDate: Installed on 2019-07-23 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago) -- Also found on Ubuntu-certified HP EliteDesk 800 G3 DM. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+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 1846016]
Thanks for the patch you sent You-Sheng! As I replied in the list, the 7265D devices do implement this command, so a better fix would be this: diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/fw.c b/drivers/net/wireless/intel/iwlwifi/mvm/fw.c index 0d2229319261..38d89ee9bd28 100644 --- a/drivers/net/wireless/intel/iwlwifi/mvm/fw.c +++ b/drivers/net/wireless/intel/iwlwifi/mvm/fw.c @@ -906,8 +906,10 @@ static bool iwl_mvm_sar_geo_support(struct iwl_mvm *mvm) * entirely. */ return IWL_UCODE_SERIAL(mvm->fw->ucode_ver) >= 38 || - IWL_UCODE_SERIAL(mvm->fw->ucode_ver) == 29 || - IWL_UCODE_SERIAL(mvm->fw->ucode_ver) == 17; + IWL_UCODE_SERIAL(mvm->fw->ucode_ver) == 17 || + (IWL_UCODE_SERIAL(mvm->fw->ucode_ver) == 29 && + (mvm->trans->hw_rev & +CSR_HW_REV_TYPE_MSK) == CSR_HW_REV_TYPE_7265D); } int iwl_mvm_get_sar_geo_profile(struct iwl_mvm *mvm) Can someone try it? -- 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/1846016 Title: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Bug description: I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since yesterday. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.182 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 30 20:57:08 2019 Dependencies: InstallationDate: Installed on 2019-07-23 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago) -- Also found on Ubuntu-certified HP EliteDesk 800 G3 DM. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+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 1846016]
Okay, I think this patch is good and I have applied it internally. I'll push it you as soon as I get confirmation that the patch I posted in the previous comment works. -- 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/1846016 Title: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Bug description: I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since yesterday. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.182 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 30 20:57:08 2019 Dependencies: InstallationDate: Installed on 2019-07-23 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago) -- Also found on Ubuntu-certified HP EliteDesk 800 G3 DM. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+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 1833281] Re: System freeze when memory is put on SWAP in Linux >4.10.x
As insane as it seems... Reverting back to EXT4 from BTRFS fixed the problem... So for me, it is an issue when BTRFS is used as root partition. I wasn't even using swap files -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1833281] Re: Complete system freeze even when swapping small amounts of memory
Update on this. Looks like it's an old upstream bug. https://bugzilla.kernel.org/show_bug.cgi?id=196729 But now I noticed this also happens on my laptop, but it's more "recoverable" after something like 25/30 minutes. Still, this problem is NOT present in older kernels than 4.10 ** Bug watch added: Linux Kernel Bug Tracker #196729 https://bugzilla.kernel.org/show_bug.cgi?id=196729 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=196729 Importance: Unknown Status: Unknown ** Summary changed: - Complete system freeze even when swapping small amounts of memory + System freeze when memory is put on SWAP in Linux >4.10.x -- 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/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0
[Kernel-packages] [Bug 1833281] Re: Complete system freeze even when swapping small amounts of memory
I tried on FreeBSD today, and this behavior is not present -- 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/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37
[Kernel-packages] [Bug 1833281] Re: Complete system freeze even when swapping small amounts of memory
Are you on a Ryzen platform too? -- 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/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.sku: To be filled by O.E.M.
[Kernel-packages] [Bug 1833281] Re: Complete system freeze even when swapping small amounts of memory
Not necessarly, I can reproduce this sometimes with other stress tests -- 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/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37
[Kernel-packages] [Bug 1833281] Re: Complete system freeze even when swapping small amounts of memory
A small update on this. I tried another distribution with the same kernel version, and this does not happen... I don't really know why. 0 times out of 10 this does not happen. Also, when this occurs, triggering the OOM with SYSRQ+F also fixes the issues, but shows that no swap memory was being used, like it couldn't swap properly...? To be correct, it swapped only 64MB in the last try I made, instead of 200MB -- 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/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International
[Kernel-packages] [Bug 1833281] Re: Complete system freeze even when swapping small amounts of memory
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37
[Kernel-packages] [Bug 1833281] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271425/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
[Kernel-packages] [Bug 1833281] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271428/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
[Kernel-packages] [Bug 1833281] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271426/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
[Kernel-packages] [Bug 1833281] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271434/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
[Kernel-packages] [Bug 1833281] Re: Complete system freeze even when swapping small amounts of memory
apport information ** Tags added: apport-collected bionic ** Description changed: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: haru 2076 F pulseaudio + /dev/snd/controlC2: haru 2076 F pulseaudio + /dev/snd/controlC0: haru 2076 F pulseaudio + CurrentDesktop: communitheme:ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + IwConfig: + enp24s0 no wireless extensions. + + lono wireless extensions. + MachineType: Micro-Star International Co., Ltd. MS-7A37 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-17-generic N/A + linux-backports-modules-5.0.0-17-generic N/A + linux-firmware1.173.6 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: bionic + Uname: Linux 5.0.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: sudo video + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 01/22/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.K0 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: B350M MORTAR (MS-7A37) + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 4 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: MS-7A37 + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: 1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271423/+files/AlsaInfo.txt -- You received
[Kernel-packages] [Bug 1833281] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271433/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
[Kernel-packages] [Bug 1833281] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271424/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
[Kernel-packages] [Bug 1833281] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271429/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1833281] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271430/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
[Kernel-packages] [Bug 1833281] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271427/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
[Kernel-packages] [Bug 1833281] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271431/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1833281] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1833281/+attachment/5271432/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
[Kernel-packages] [Bug 1833281] [NEW] Complete system freeze even when swapping small amounts of memory
Public bug reported: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected bionic ** Description changed: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH