[Kernel-packages] [Bug 1940731] [NEW] I installed Ubuntu 20.04 LTS today and my laptop touchpad is suddenly not working. But it seems to be fine while I use windows on the same laptop.
Public bug reported: cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=c542 Version=0111 N: Name="Logitech Wireless Receiver Mouse" P: Phys=usb-:00:14.0-9/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0/0003:046D:C542.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=174f Product=1176 Version=0028 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=11" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=12" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event16 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 21 10:56:31 2021 InstallationDate: Installed on 2021-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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 -- You received this bug notification because you are a member of
[Kernel-packages] [Bug 1940730] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build
Public bug reported: Sorry. I have got no idea what is this bug is about. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-27-generic Date: Sat Aug 21 13:22:34 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7~20.04.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 6.30.223.271+bdcom-0ubuntu7~20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1940730 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Sorry. I have got no idea what is this bug is about. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-27-generic Date: Sat Aug 21 13:22:34 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7~20.04.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 6.30.223.271+bdcom-0ubuntu7~20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1940730/+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 1940730] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1940730 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Sorry. I have got no idea what is this bug is about. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-27-generic Date: Sat Aug 21 13:22:34 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7~20.04.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 6.30.223.271+bdcom-0ubuntu7~20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1940730/+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 1937004] Re: Add additional Mediatek MT7921 WiFi/BT device IDs
** Changed in: linux (Ubuntu Impish) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1937004 Title: Add additional Mediatek MT7921 WiFi/BT device IDs Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Some Mediatek MT7921 Bluetooth doesn't work out of box. [Fix] One ID for Lite-On was included in upstream, but we need two additional more from different vendors. [Test Case] With firmware from bug 1936452, this will bring up MT7921 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. == original bug description == Mediatek MT7921 has been added to mainline kernel & firmware. Firmware part is being handled by bug 1936452, and WiFi fw loading failure in bug 1936790. This issue will focus on backport/add device IDs for MT7921: * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device * Bus 002 Device 003: ID 13d3:3567 IMC Networks linux$ git log --graph --oneline korg/master -- \ drivers/bluetooth/ \ drivers/net/wireless/mediatek/mt76/mt7921/ linux-firmware$ git log --graph --oneline korg/master -- \ mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \ mediatek/WIFI_RAM_CODE_MT7961_1.bin \ mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin * a7882719 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * 2fd5139f linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 * 42a66e5b linux-firmware: update firmware for MT7921 WiFi device * 58fb90a0 linux-firmware: add frimware for mediatek bluetooth chip (MT7921) * 391fd50d linux-firmware: add firmware for MT7921 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1278 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X135 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-05 (16 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 192f:0616 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (5-button) Bus 001 Device 002: ID 03f0:344a HP, Inc HP USB Slim Keyboard Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3910 Package: linux-firmware 1.187.15+staging.9 [origin: LP-PPA-vicamo-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9009-oem root=UUID=6ae05750-3063-48a4-92af-626f62ff75fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9009.10+staging.2-oem 5.13.0 RelatedPackageVersions: linux-restricted-modules-5.13.0-9009-oem N/A linux-backports-modules-5.13.0-9009-oem N/A linux-firmware 1.187.15+staging.9 Tags: third-party-packages focal Uname: Linux 5.13.0-9009-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2021 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.8.22 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.8.22:bd07/12/2021:br0.8:svnDellInc.:pnInspiron3910:pvr:sku0AD3:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: Inspiron 3910 dmi.product.sku: 0AD3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1882623] Re: VM enter into hung status after triggering a crash
** Changed in: linux-azure (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1882623 Title: VM enter into hung status after triggering a crash Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Bionic: Fix Committed Bug description: [Impact] * When kdumping on trusty/4.15 in an Azure instance, we observe quite frequently a stall on the kdump kernel, it gets blocked and soon we see a stack like the following: [ 65.452007] INFO: rcu_sched detected stalls on CPUs/tasks: [ 65.456004] 1-...!: (0 ticks this GP) idle=488/0/0 softirq=1/1 fqs=0 [ 65.456004] (detected by 0, t=15002 jiffies, g=707, c=706, q=8457) [ 65.456004] rcu_sched kthread starved for 15002 jiffies! g707 c706 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1 * By using the Azure serial console, we collected a sysrq-w when the issue happens: [ 529.515013] sysrq: Show Blocked State [ 529.517730] taskPC stack pid father [ 529.519006] kworker/u4:2D094 2 0x8000 [ 529.519006] Workqueue: events_unbound fsnotify_mark_destroy_workfn [ 529.519006] Call Trace: [ 529.519006] __schedule+0x292/0x880 [ 529.519006] schedule+0x36/0x80 [ 529.519006] schedule_timeout+0x1d5/0x2f0 [ 529.519006] ? check_preempt_wakeup+0x162/0x260 [ 529.519006] wait_for_completion+0xa5/0x110 [ 529.519006] ? wake_up_q+0x80/0x80 [ 529.519006] __synchronize_srcu.part.14+0x67/0x80 [ 529.519006] ? trace_raw_output_rcu_utilization+0x50/0x50 [ 529.519006] ? __switch_to_asm+0x41/0x70 [ 529.519006] synchronize_srcu+0xd1/0xd6 [ 529.519006] fsnotify_mark_destroy_workfn+0x6d/0xc0 [ 529.519006] process_one_work+0x14e/0x390 [ 529.519006] worker_thread+0x1cc/0x3d0 [ 529.519006] kthread+0x105/0x140 [ 529.519006] ? max_active_store+0x60/0x60 [ 529.519006] ? kthread_bind+0x20/0x20 [ 529.519006] ret_from_fork+0x35/0x40 [ 529.519006] udevadm D0 544 1 0x [ 529.519006] Call Trace: [ 529.519006] __schedule+0x292/0x880 [ 529.519006] schedule+0x36/0x80 [ 529.519006] schedule_timeout+0x1d5/0x2f0 [ 529.519006] ? try_to_wake_up+0x4a/0x460 [ 529.519006] ? try_to_wake_up+0x4a/0x460 [ 529.519006] wait_for_completion+0xa5/0x110 [ 529.519006] ? wake_up_q+0x80/0x80 [ 529.519006] __flush_work.isra.29+0x119/0x1b0 [ 529.519006] ? destroy_worker+0x90/0x90 [ 529.519006] flush_delayed_work+0x3f/0x50 [ 529.519006] fsnotify_wait_marks_destroyed+0x15/0x20 [ 529.519006] fsnotify_destroy_group+0x4e/0xc0 [ 529.519006] inotify_release+0x1e/0x50 [ 529.519006] __fput+0xea/0x220 [ 529.519006] fput+0xe/0x10 [ 529.519006] task_work_run+0x8c/0xb0 [ 529.519006] exit_to_usermode_loop+0x70/0xa9 [ 529.519006] do_syscall_64+0x1b5/0x1e0 [ 529.519006] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 529.519006] dhclientD0 573572 0x [ 529.519006] Call Trace: [ 529.519006] __schedule+0x292/0x880 [ 529.519006] schedule+0x36/0x80 [ 529.519006] schedule_timeout+0x1d5/0x2f0 [ 529.519006] ? aa_profile_af_perm+0xb4/0xf0 [ 529.519006] wait_for_completion+0xa5/0x110 [ 529.519006] ? wake_up_q+0x80/0x80 [ 529.519006] __wait_rcu_gp+0x123/0x150 [ 529.519006] synchronize_sched+0x4e/0x60 [ 529.519006] ? __call_rcu+0x2f0/0x2f0 [ 529.519006] ? trace_raw_output_rcu_utilization+0x50/0x50 [ 529.519006] synchronize_net+0x1c/0x30 [ 529.519006] __unregister_prot_hook+0xcd/0xf0 [ 529.519006] packet_do_bind+0x1bd/0x250 [ 529.519006] packet_bind+0x2f/0x50 [ 529.519006] SYSC_bind+0xd8/0x110 [ 529.519006] ? sock_alloc_file+0x91/0x130 [ 529.519006] SyS_bind+0xe/0x10 [ 529.519006] do_syscall_64+0x80/0x1e0 [ 529.519006] entry_SYSCALL_64_after_hwframe+0x41/0xa6 * Bisecting mainline kernels, we found that v4.17-rc1 didn't reproduce the issue, whereas v4.16 reproduced. Then, a fine-grained git bisect led us to the fix - the following patch, when backported to a problematic version, fixes the issue: d8e462e19305 ("Drivers: hv: vmbus: Implement Direct Mode for stimer0") * In Azure/Hyper-V, before the aforementioned commit, timer interrupts were passed to the hypervisor through a vmbus message, a mechanism of communication of hyper-v guests/hypervisor. With the patch, a check is made (through MSR-like mechanism) and if the hypervisor supports, a direct timer IRQ mechanism is put in-place instead of the vmbus channel. * Our theory is that on kdump kernel, specially due to the single cpu nature, the vmbus-messaged timer IRQ could interfere with scheduling and create a dead-lock condition, which is what we observe from the stack traces. Hence, we hereby propose to backport
[Kernel-packages] [Bug 1934923] Re: Sync up mlxbf-gige driver with upstreamed version
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934923 Title: Sync up mlxbf-gige driver with upstreamed version Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf-gige driver has just been upstreamed so linux-bluefield needs to be synced up with what we have upstreamed. IMPORTANT: during testing, make sure the latest UEFI (bootloader) is loaded on top of these changes, otherwise both the gpio driver and mlxbf-gige driver will fail to load. [Fix] * reverted 20 commits related to the mlxbf-gige driver and 1 commit related to gpio-mlxbf2 driver since there are dependencies between them. * Cherry-picked f92e1869d74e1acc6551256eb084a1c14a054e19 from net-next branch. The upstreamed version of the GPIO driver removed the dependency between the mlxbf-gige driver and gpio-mlxbf2 driver. * added code that was left out of the upstreamed version. and added code that got reverted in gpio-mlxbf2.c * updated the UEFI ACPI table to reflect the above changes (so the bootloader and the linux drivers need to be in sync) [Test Case] * oob_net0 coming up after several SW_RESET or reboot * oob_net0 coming up after several powercycles * oob_net0 coming up after pushing a new Ubuntu/CentOS/Yocto * rmmod/modprove mlxbf_gige several times * OOB PXE boot multiple times from UEFI menu * automate OOB PXE boot and do reboot * automate OOB PXE boot and do powercycle * Test that GPIO7 reset still works on BlueSphere like boards [Regression Potential] Any of the test cases above could be impacted due to these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934923/+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 1938818] Re: Add support for packet-per-second policing
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1938818 Title: Add support for packet-per-second policing Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) It’s a missing feature in current kernel. * brief explanation of fixes Cherry-pick and backport the related patches from upstream kernel. * How to test Add tc filter rule with police action, and check it is offloaded. For example: tc filter add dev enp8s0f0_0 ingress protocol ip flower \ dst_mac b8:ce:f6:7b:d9:24 \ action police pkts_rate 1000 pkts_burst 100 conform-exceed drop/pipe \ action mirred egress redirect dev enp8s0f0 * What it could break. New feature, doesn't break existing features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1938818/+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 1940718] Re: package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1940718 Title: package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: system update failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.12 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 20 16:56:14 2021 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2021-07-05T13:03:06.049681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1940718/+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 1939221] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1939221/+attachment/5519598/+files/ProcEnviron.txt ** Description changed: It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking at first i watch video then put it on full screen (especially in browser chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" or try "Ctrl+alt+F2" to text mode. then I search google and install amd's opencl driver to replace intel. but, it just better then previous. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.9-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 5.4.41 Uname: Linux 5.4.0-7634-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 13:48:50 2021 InstallationDate: Installed on 2019-11-23 (623 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-23 (636 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: focal Uname: Linux 5.8.0-050800-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 ** 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/1939221 Title: [amdgpu] Screen freeze then system without response Status in linux package in Ubuntu: Confirmed Bug description: It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking at first i watch video then put it on full screen (especially in browser chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" or try "Ctrl+alt+F2" to text mode. then I search google and install amd's opencl driver to replace intel. but, it just better then previous. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.9-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 5.4.41 Uname: Linux 5.4.0-7634-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 13:48:50 2021 InstallationDate: Installed on 2019-11-23 (623 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-23 (636 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: focal Uname: Linux 5.8.0-050800-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/ubuntu/+source/linux/+bug/1939221/+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 1939221] Re: [amdgpu] Screen freeze then system without response
apport information ** Tags added: apport-collected ** Description changed: It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking at first i watch video then put it on full screen (especially in browser chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" or try "Ctrl+alt+F2" to text mode. then I search google and install amd's opencl driver to replace intel. but, it just better then previous. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.9-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 5.4.41 Uname: Linux 5.4.0-7634-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 13:48:50 2021 InstallationDate: Installed on 2019-11-23 (623 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-11-23 (636 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + Package: linux (not installed) + Tags: focal + Uname: Linux 5.8.0-050800-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 ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1939221/+attachment/5519597/+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/1939221 Title: [amdgpu] Screen freeze then system without response Status in linux package in Ubuntu: Confirmed Bug description: It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking at first i watch video then put it on full screen (especially in browser chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" or try "Ctrl+alt+F2" to text mode. then I search google and install amd's opencl driver to replace intel. but, it just better then previous. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.9-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 5.4.41 Uname: Linux 5.4.0-7634-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 13:48:50 2021 InstallationDate: Installed on 2019-11-23 (623 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-23 (636 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: focal Uname: Linux 5.8.0-050800-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/ubuntu/+source/linux/+bug/1939221/+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 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
Hello,Po-Hsu Lin $ uname -r 5.11.0-27-generic $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal $ sudo vi /etc/modules vfio vfio_iommu_type1 vfio_pci vfio_virqfd kvm kvm_intel :wq $ lsmod | grep vfio empty... $ lsmod | grep kvm kvm_intel 294912 0 kvm 819200 1 kvm_intel $ modinfo vfio name: vfio filename: (builtin) softdep:post: vfio_iommu_type1 vfio_iommu_spapr_tce alias: devname:vfio/vfio alias: char-major-10-196 description:VFIO - User Level meta-driver author: Alex Williamson license:GPL v2 file: drivers/vfio/vfio version:0.3 parm: enable_unsafe_noiommu_mode:Enable UNSAFE, no-IOMMU mode. This mode provides no device isolation, no DMA translation, no host kernel protection, cannot be used for device assignment to virtual machines, requires RAWIO permissions, and will taint the kernel. If you do not know what this is for, step away. (default: false) (bool) $ modinfo vfio_iommu_type1 name: vfio_iommu_type1 filename: (builtin) description:Type1 IOMMU driver for VFIO author: Alex Williamson license:GPL v2 file: drivers/vfio/vfio_iommu_type1 version:0.2 parm: allow_unsafe_interrupts:Enable VFIO IOMMU support for on platforms without interrupt remapping support. (bool) parm: disable_hugepages:Disable VFIO IOMMU support for IOMMU hugepages. (bool) parm: dma_entry_limit:Maximum number of user DMA mappings per container (65535). (uint) $ modinfo vfio_pci name: vfio_pci filename: (builtin) description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 file: drivers/vfio/pci/vfio-pci version:0.2 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) parm: enable_sriov:Enable support for SR-IOV configuration. Enabling SR-IOV on a PF typically requires support of the userspace PF driver, enabling VFs without such support may result in non-functional VFs or PF. (bool) parm: disable_denylist:Disable use of device denylist. Disabling the denylist allows binding to devices with known errata that may lead to exploitable stability or security issues when accessed by untrusted users. (bool) $ modinfo vfio_virqfd name: vfio_virqfd filename: (builtin) description:IRQFD support for VFIO bus drivers author: Alex Williamson license:GPL v2 file: drivers/vfio/vfio_virqfd version:0.1 Po-Hsu Lin Would you please fix this bug as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in kmod package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in kmod source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for
[Kernel-packages] [Bug 1933274] Re: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)"
Hey, it says bug status is "Incomplete", but shouldn't it be moved from this status? I think that there is a very specific information in description and attachments so maybe logs are not needed? -- 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/1933274 Title: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)" Status in linux package in Ubuntu: Incomplete Bug description: Tracing this back, I found the current Ubuntu 5.11 kernel has incorrect offsets for some platforms (TGL-H and ADL). I created an upstream bug at https://gitlab.freedesktop.org/drm/intel/-/issues/3662 and was directed to a commit, 5d0c938ec9cc, that ought to fix this issue. See the attached patch file for this commit applied to the current Ubuntu 5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933274/+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 1940722] [NEW] Package bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 is not installed because apt thinks it’s a downgrade
Public bug reported: 1) Ubuntu release: 20.04 2) Installed package version: 6.30.223.271+bdcom-0ubuntu7 3) Expectation: bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 was released to focal-updates to fix LP: #1932159 (building the kernel module with HWE kernel 5.11 on Ubuntu 20.04). The bcmwl-kernel-source package should be updated to the version in focal-updates. 4) Actual result: apt considers the package from focal-updates a downgrade, leaving the system with broken WiFi after updating to the HWE kernel. $ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu7 Candidate: 6.30.223.271+bdcom-0ubuntu7 Version table: *** 6.30.223.271+bdcom-0ubuntu7 100 100 /var/lib/dpkg/status 6.30.223.271+bdcom-0ubuntu7~20.04.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 6.30.223.271+bdcom-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages $ sudo apt install bcmwl-kernel-source=6.30.223.271+bdcom-0ubuntu7~20.04.3 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libllvm11 libllvm11:i386 shim Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: bcmwl-kernel-source 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 1,546 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue? [Y/n] ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Description changed: 1) Ubuntu release: 20.04 2) Installed package version: 6.30.223.271+bdcom-0ubuntu7 - 3) Expectation: bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 was released to focal-updates to fix #1932159 (building the kernel module with HWE kernel 5.11 on Ubuntu 20.04). The bcmwl-kernel-source package should be updated to the version in focal-updates. + 3) Expectation: bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 was released to focal-updates to fix LP: #1932159 (building the kernel module with HWE kernel 5.11 on Ubuntu 20.04). The bcmwl-kernel-source package should be updated to the version in focal-updates. 4) Actual result: apt considers the package from focal-updates a downgrade, leaving the system with broken WiFi after updating to the HWE kernel. $ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: - Installed: 6.30.223.271+bdcom-0ubuntu7 - Candidate: 6.30.223.271+bdcom-0ubuntu7 - Version table: - *** 6.30.223.271+bdcom-0ubuntu7 100 - 100 /var/lib/dpkg/status - 6.30.223.271+bdcom-0ubuntu7~20.04.3 500 - 500 http://de.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages - 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages - 6.30.223.271+bdcom-0ubuntu5 500 - 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages + Installed: 6.30.223.271+bdcom-0ubuntu7 + Candidate: 6.30.223.271+bdcom-0ubuntu7 + Version table: + *** 6.30.223.271+bdcom-0ubuntu7 100 + 100 /var/lib/dpkg/status + 6.30.223.271+bdcom-0ubuntu7~20.04.3 500 + 500 http://de.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages + 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages + 6.30.223.271+bdcom-0ubuntu5 500 + 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages $ sudo apt install bcmwl-kernel-source=6.30.223.271+bdcom-0ubuntu7~20.04.3 Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: - libllvm11 libllvm11:i386 shim + libllvm11 libllvm11:i386 shim Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: - bcmwl-kernel-source + bcmwl-kernel-source 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 1,546 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue? [Y/n] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1940722 Title: Package bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 is not installed because apt thinks it’s a downgrade Status in bcmwl package in Ubuntu: New Bug description: 1) Ubuntu release: 20.04 2) Installed package version: 6.30.223.271+bdcom-0ubuntu7 3) Expectation: bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 was
[Kernel-packages] [Bug 1940722] Re: Package bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 is not installed because apt thinks it’s a downgrade
This seems to have hit multiple users, see e.g. a post on Ask Ubuntu: https://askubuntu.com/q/1356061 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1940722 Title: Package bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 is not installed because apt thinks it’s a downgrade Status in bcmwl package in Ubuntu: New Bug description: 1) Ubuntu release: 20.04 2) Installed package version: 6.30.223.271+bdcom-0ubuntu7 3) Expectation: bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu7~20.04.3 was released to focal-updates to fix LP: #1932159 (building the kernel module with HWE kernel 5.11 on Ubuntu 20.04). The bcmwl-kernel-source package should be updated to the version in focal-updates. 4) Actual result: apt considers the package from focal-updates a downgrade, leaving the system with broken WiFi after updating to the HWE kernel. $ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu7 Candidate: 6.30.223.271+bdcom-0ubuntu7 Version table: *** 6.30.223.271+bdcom-0ubuntu7 100 100 /var/lib/dpkg/status 6.30.223.271+bdcom-0ubuntu7~20.04.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 6.30.223.271+bdcom-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages $ sudo apt install bcmwl-kernel-source=6.30.223.271+bdcom-0ubuntu7~20.04.3 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libllvm11 libllvm11:i386 shim Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: bcmwl-kernel-source 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 1,546 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue? [Y/n] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1940722/+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 1932159] Re: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Unfortunately, it seems that this update is not actually arriving on systems because apt considers package version 6.30.223.271+bdcom-0ubuntu7~20.04.3 from focal-updates a downgrade compared to version 6.30.223.271+bdcom-0ubuntu7, see LP: #1940722. Not sure why that is, maybe the version should be named differently? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1932159 Title: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in bcmwl package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in bcmwl source package in Focal: Fix Released Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running bcmwl tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz [Test Plan] sudo apt-get install bcmwl-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11 [Other Info] Please migrate this package update to -security as well in order not to break users when the default hwe kernel in Focal upgrades to 5.11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+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 1939855] Re: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
I am seeing this on 20.04.2. $ uname -a Linux 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:09:17 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/1939855 Title: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in dellserver: Incomplete Status in focal package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1939855/+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 1940718] Re: package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1940718 Title: package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: system update failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.12 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 20 16:56:14 2021 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2021-07-05T13:03:06.049681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1940718/+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 1940718] [NEW] package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit stat
Public bug reported: system update failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.12 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 20 16:56:14 2021 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2021-07-05T13:03:06.049681 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1940718 Title: package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: system update failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.12 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 20 16:56:14 2021 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.12 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2021-07-05T13:03:06.049681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1940718/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I am seeing the same problem on a Dell Precision 7750. Ubuntu 20.04LTS kernel: 5.11.0-27-generic #29~20.04.1-Ubuntu SMP graphics: VGA compatible controller: NVIDIA Corporation TU106GLM [Quadro RTX 3000 Mobile / Max-Q] (rev a1) plus Intel i915 processor: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz With nvidia-prime installed, running nvidia-settings presents three options: NVIDIA (Performance Mode), NVIDIA On-Demand, Power Save In Performance Mode, only the external HDMI port is active. Booting with no external monitor produces a blank laptop LCD display, but the external monitor is active. Using System Settings / Display, only the external monitor is detected. The keyboard secondary function key Fn F8 has no effect. Laptop screen is blank if booted without an external monitor connected. In On-Demand mode, only the laptop display is active and the external monitor has no output. System Settings / Display detects both monitors. The Fn F8 key pops up a display mode selection tool to select how the screens will be configured, if the external-monitor-only mode is selected, the laptop screen is blank, and there is no display on the external monitor. All other selections have no effect. In Power Save mode, only the laptop display is active and the external monitor has no output. System Settings / Display detects only the laptop monitor. The keyboard secondary function key Fn F8 has no effect. -- 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/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00
[Kernel-packages] [Bug 1939417] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519537/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature
[Kernel-packages] [Bug 1939417] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519525/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX
[Kernel-packages] [Bug 1939417] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519536/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE
[Kernel-packages] [Bug 1939417] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519529/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004:
[Kernel-packages] [Bug 1939417] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519538/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004:
[Kernel-packages] [Bug 1939417] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519535/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting
[Kernel-packages] [Bug 1939417] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519530/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature
[Kernel-packages] [Bug 1939417] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519528/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature
[Kernel-packages] [Bug 1939417] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519532/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE
[Kernel-packages] [Bug 1939417] modified.conffile..etc.apport.crashdb.conf.txt
apport information ** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519541/+files/modified.conffile..etc.apport.crashdb.conf.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
[Kernel-packages] [Bug 1939417] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519539/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE
[Kernel-packages] [Bug 1939417] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519526/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE
[Kernel-packages] [Bug 1939417] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519534/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE
[Kernel-packages] [Bug 1939417] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519540/+files/acpidump.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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature
[Kernel-packages] [Bug 1939417] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519533/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu:
[Kernel-packages] [Bug 1939417] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519531/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature
[Kernel-packages] [Bug 1939417] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519527/+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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004:
[Kernel-packages] [Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
apport information ** Tags added: apport-collected ** Description changed: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d3ff] usable [0.00] BIOS-e820: [mem
[Kernel-packages] [Bug 1940713] [NEW] llvm-9, llvm-11 and llvm-12 contain a zero-byte manpage
Public bug reported: The llvm-mcmarkup manpage is empty for llvm-9 (1:9.0.1-16.1ubuntu1), llvm-11 (1:11.0.1-2ubuntu5) and llvm-12 (1:12.0.1-1): llvm-9: /usr/share/man/man1/llvm-mcmarkup-9.1.gz llvm-11: /usr/share/man/man1/llvm-mcmarkup-11.1.gz llvm-12: /usr/share/man/man1/llvm-mcmarkup-12.1.gz These 20-byte .gz files are all compressed zero-byte manpages. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: llvm-12 1:12.0.1-1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Aug 20 21:21:54 2021 InstallationDate: Installed on 2016-11-26 (1728 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RebootRequiredPkgs: linux-image-5.13.0-14-generic linux-base SourcePackage: llvm-toolchain-12 UpgradeStatus: Upgraded to impish on 2021-08-08 (12 days ago) ** Affects: llvm-toolchain-12 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-12 in Ubuntu. https://bugs.launchpad.net/bugs/1940713 Title: llvm-9, llvm-11 and llvm-12 contain a zero-byte manpage Status in llvm-toolchain-12 package in Ubuntu: New Bug description: The llvm-mcmarkup manpage is empty for llvm-9 (1:9.0.1-16.1ubuntu1), llvm-11 (1:11.0.1-2ubuntu5) and llvm-12 (1:12.0.1-1): llvm-9: /usr/share/man/man1/llvm-mcmarkup-9.1.gz llvm-11: /usr/share/man/man1/llvm-mcmarkup-11.1.gz llvm-12: /usr/share/man/man1/llvm-mcmarkup-12.1.gz These 20-byte .gz files are all compressed zero-byte manpages. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: llvm-12 1:12.0.1-1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Aug 20 21:21:54 2021 InstallationDate: Installed on 2016-11-26 (1728 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RebootRequiredPkgs: linux-image-5.13.0-14-generic linux-base SourcePackage: llvm-toolchain-12 UpgradeStatus: Upgraded to impish on 2021-08-08 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1940713/+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 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Patch submitted: https://lists.ubuntu.com/archives/kernel- team/2021-August/123445.html ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1937078 Title: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: SRU Justification [Impact] Customers have degraded network performance on Hyper-V/Azure This is a request to pick up a patch from the upstream, the patch fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch need to get picked up for 20.04, 18.04. The link to the upstream patch follows: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=7c9ff3d61b253715dcf968a6307af148c9b2 Description of issue and solution: The vmbus module uses a rotational algorithm to assign target CPUs to a device's channels. Depending on the timing of different device's channel offers, different channels of a device may be assigned to the same CPU. For example on a VM with 2 CPUs, if NIC A and B's channels are offered in the following order, NIC A will have both channels on CPU0, and NIC B will have both channels on CPU1 -- see below. This kind of assignment causes RSS load that is spreading across different channels to end up on the same CPU. Timing of channel offers: NIC A channel 0 NIC B channel 0 NIC A channel 1 NIC B channel 1 VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic network adapter Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd} Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd Rel_ID=14, target_cpu=0 Rel_ID=17, target_cpu=0 VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic network adapter Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea} Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea Rel_ID=16, target_cpu=1 Rel_ID=18, target_cpu=1 Update the vmbus CPU assignment algorithm to avoid duplicate CPU assignments within a device. The new algorithm iterates num_online_cpus + 1 times. The existing rotational algorithm to find "next NUMA & CPU" is still here. But if the resulting CPU is already used by the same device, it will try the next CPU. In the last iteration, it assigns the channel to the next available CPU like the existing algorithm. This is not normally expected, because during device probe, we limit the number of channels of a device to be <= number of online CPUs. [Test Plan] This could be tough to test as the patch fixes a race condition. [Where problems could occur] Network performance issues could persist. [Other Info] SF:#00315347 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937078/+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 1940513] Re: Hang on Shutdown with AMD Ryzen 5700G
I'm not sure what do you mean? If you ask because Kernel 2.8., I tried because I would know, if it 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/1940513 Title: Hang on Shutdown with AMD Ryzen 5700G Status in linux package in Ubuntu: Confirmed Bug description: Hi, i upgraded my System. Before I had a Ryzen 3200G. Now I have an Ryzen 5700G. Both systems running on an Linux Mint 20.2, Kernel 5.11.0-27, ASUS B450N-A Mainboard. 8GB DDR4-3200. When I shutdown or reboot the System the Execution won't be finished. The Linux Logo is displayed on one of my to screens. Than nothing happens. Than the Drive-led will flash shortly after some seconds. This will also happen with Kernel 5.13 Thx n greez --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thorsten 1292 F pulseaudio /dev/snd/controlC0: thorsten 1292 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-04-17 (124 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: Tags: uma Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/13/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3205 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3205:bd07/13/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940513/+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 1940703] Re: Ubuntu cannot find module "l2arc_rebuild_enabled"
FYI, the 5.4 kernel ships with a ZFS module that predates the l2arc_rebuild_enabled parameter. You might want to switch to the HWE kernel (https://wiki.ubuntu.com/Kernel/LTSEnablementStack) that will provide this. As such, I will mark this bug as invalid. ** Changed in: zfs-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1940703 Title: Ubuntu cannot find module "l2arc_rebuild_enabled" Status in zfs-linux package in Ubuntu: Invalid Bug description: Good day. I tried to make l2arc cache persistent after reboot, add option to /etc/modprobe.d/zfs.conf options zfs zfs_arc_max=6294967296 but after reboot: dmesg [ +0,011105] zfs: unknown parameter 'l2arc_rebuild_enabled' ignored all modules? ls /sys/module/zfs/parameters/l2arc_ l2arc_feed_again l2arc_feed_min_ms l2arc_feed_secs l2arc_headrooml2arc_headroom_boost l2arc_noprefetch l2arc_norw l2arc_write_boost l2arc_write_max 5.4.0-81-generic, ubuntu 20.04 zfs-linux - are correct bugreport package? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.12 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Aug 20 20:39:14 2021 InstallationDate: Installed on 2019-12-28 (600 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-04-23 (483 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Отказано в доступе: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1940703/+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 1940706] [NEW] Hirsute update: upstream stable patchset 2021-08-20
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-08-20 Ported from the following upstream stable releases: v5.10.55, v5.13.7 v5.10.56, v5.13.8 from git://git.kernel.org/ tools: Allow proper CC/CXX/... override with LLVM=1 in Makefile.include io_uring: fix link timeout refs KVM: x86: determine if an exception has an error code only when injecting it. af_unix: fix garbage collect vs MSG_PEEK workqueue: fix UAF in pwq_unbound_release_workfn() cgroup1: fix leaked context root causing sporadic NULL deref in LTP net/802/mrp: fix memleak in mrp_request_join() net/802/garp: fix memleak in garp_request_join() net: annotate data race around sk_ll_usec sctp: move 198 addresses from unusable to private scope rcu-tasks: Don't delete holdouts within trc_inspect_reader() rcu-tasks: Don't delete holdouts within trc_wait_for_one_reader() ipv6: allocate enough headroom in ip6_finish_output2() drm/ttm: add a check against null pointer dereference hfs: add missing clean-up in hfs_fill_super hfs: fix high memory mapping in hfs_bnode_read hfs: add lock nesting notation to hfs_find_init firmware: arm_scmi: Fix possible scmi_linux_errmap buffer overflow firmware: arm_scmi: Fix range check for the maximum number of pending messages cifs: fix the out of range assignment to bit fields in parse_server_interfaces iomap: remove the length variable in iomap_seek_data iomap: remove the length variable in iomap_seek_hole ARM: dts: versatile: Fix up interrupt controller node names ipv6: ip6_finish_output2: set sk into newly allocated nskb nvme-pci: fix multiple races in nvme_setup_io_queues UBUNTU: upstream stable to v5.10.55, v5.13.7 selftest: fix build error in tools/testing/selftests/vm/userfaultfd.c io_uring: fix null-ptr-deref in io_sq_offload_start() x86/asm: Ensure asm/proto.h can be included stand-alone pipe: make pipe writes always wake up readers btrfs: fix rw device counting in __btrfs_free_extra_devids btrfs: mark compressed range uptodate only if all bio succeed Revert "ACPI: resources: Add checks for ACPI IRQ override" ACPI: DPTF: Fix reading of attributes x86/kvm: fix vcpu-id indexed array sizes KVM: add missing compat KVM_CLEAR_DIRTY_LOG ocfs2: fix zero out valid data ocfs2: issue zeroout to EOF blocks can: j1939: j1939_xtp_rx_dat_one(): fix rxtimer value between consecutive TP.DT to 750ms can: raw: raw_setsockopt(): fix raw_rcv panic for sock UAF can: peak_usb: pcan_usb_handle_bus_evt(): fix reading rxerr/txerr values can: mcba_usb_start(): add missing urb->transfer_dma initialization can: usb_8dev: fix memory leak can: ems_usb: fix memory leak can: esd_usb2: fix memory leak alpha: register early reserved memory in memblock HID: wacom: Re-enable touch by default for Cintiq 24HDT / 27QHDT NIU: fix incorrect error return, missed in previous revert drm/amd/display: ensure dentist display clock update finished in DCN20 drm/amdgpu: Avoid printing of stack contents on firmware load error drm/amdgpu: Fix resource leak on probe error path blk-iocost: fix operation ordering in iocg_wake_fn() nfc: nfcsim: fix use after free during module unload cfg80211: Fix possible memory leak in function cfg80211_bss_update RDMA/bnxt_re: Fix stats counters bpf: Fix OOB read when printing XDP link fdinfo mac80211: fix enabling 4-address mode on a sta vif after assoc netfilter: conntrack: adjust stop timestamp to real expiry value netfilter: nft_nat: allow to specify layer 4 protocol NAT only i40e: Fix logic of disabling queues i40e: Fix firmware LLDP agent related warning i40e: Fix queue-to-TC mapping on Tx i40e: Fix log TC creation failure when max num of queues is exceeded tipc: fix implicit-connect for SYN+ tipc: fix sleeping in tipc accept routine net: Set true network header for ECN decapsulation net: qrtr: fix memory leaks ionic: remove intr coalesce update from napi ionic: fix up dim accounting for tx and rx ionic: count csum_none when offload enabled tipc: do not write skb_shinfo frags when doing decrytion octeontx2-pf: Fix interface down flag on error mlx4: Fix missing error code in mlx4_load_one() KVM: x86: Check the right feature bit for MSR_KVM_ASYNC_PF_ACK access net: llc: fix skb_over_panic drm/msm/dpu: Fix sm8250_mdp register length drm/msm/dp: Initialize the INTF_CONFIG register skmsg: Make sk_psock_destroy() static net/mlx5: Fix flow table chaining net/mlx5e: Fix nullptr in mlx5e_hairpin_get_mdev() sctp: fix return value check in __sctp_rcv_asconf_lookup tulip: windbond-840: Fix missing pci_disable_device()
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.11.0.1017.18)
All autopkgtests for the newly accepted linux-meta-aws (5.11.0.1017.18) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle-5.11/5.11.0.1016.17~20.04.9)
All autopkgtests for the newly accepted linux-meta-oracle-5.11 (5.11.0.1016.17~20.04.9) for focal have finished running. The following regressions have been reported in tests triggered by the package: adv-17v35x/unknown (arm64) acpi-call/unknown (arm64) xtables-addons/unknown (arm64) zfs-linux/unknown (arm64) evdi/unknown (arm64) lxc/unknown (arm64) fwts/unknown (arm64) rtl8821ce/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oracle-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939618] Re: EP11 cards going offline => Fix backport to U20.04LTS
Sorry for coming back to this with a little delay, due to the 21.10 FF and the 20.04.3 RCs ... I'm not sure if I understood you correctly. Does that mean that the commits 27c4f6738bdc to 91ffc519c199 from comment #5 all needed to be touched and are backports? And that the remaining ones are all just plain exports - w/o any modification, hence can simply be cherry-picked? This distinction is very crucial and need to be added to each of the commits, so that the entire provenance of the commit/patch is traceable. So in other words all commits that had to be touches ('backported') need to have lines like this: " (backported from commit 5620ae29f1eabe655f44335231b580a78c8364ea) Signed-off-by: First-Name Last-Name " (like described here: https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat this is not unique to the Canonical kernel team procedure, but a kind of a de-facto standard ...) Here is an example LP bug with backports attached: https://bugs.launchpad.net/bugs/1925452 Generally the others would need lines like this: " (cherry picked from commit d4e0018e3e4dd685af25d300fd26a0d5a984482e) Signed-off-by: First-Name Last-Name " But the 'cherry-picked' lines do not need to be added manually, since git helps on doing this. (If you grep for 'backport' or 'cherry-picked' though the list of patches in your zip file I get no hits.) --- So what we need is: 1) separate 'backport' files of the modified commits only, that have a 'backported' AND an additional 'Signed-off-by' line included by the backporter (no files are needed for commits that can just be cherry picked) 2) a list / sequence of the backport files AND cherry pick commits, that allows to get the entire set of needed commits/patches (cherry-picks and backports) applied to the Ubuntu focal master-next git tree [git://kernel.ubuntu.com/ubuntu/ubuntu-focal --branch master-next --single-branch] (we need to be able to re-run and re-apply this again) The rest can( and is) usually done by us - means reapplying them, pushing then to a remote git branch on Launchpad and finally sending a pull request (incl. cover letter) to the Canonical kernel teams mailing 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/1939618 Title: EP11 cards going offline => Fix backport to U20.04LTS Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Here is the backport against current git for ubuntu 20.04. It is a zip file with a patches subdir and all the patches in there together with a series file. So just unpack it and apply with quilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1939618/+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 1940703] [NEW] Ubuntu cannot find module "l2arc_rebuild_enabled"
Public bug reported: Good day. I tried to make l2arc cache persistent after reboot, add option to /etc/modprobe.d/zfs.conf options zfs zfs_arc_max=6294967296 but after reboot: dmesg [ +0,011105] zfs: unknown parameter 'l2arc_rebuild_enabled' ignored all modules? ls /sys/module/zfs/parameters/l2arc_ l2arc_feed_again l2arc_feed_min_ms l2arc_feed_secs l2arc_headrooml2arc_headroom_boost l2arc_noprefetch l2arc_norw l2arc_write_boost l2arc_write_max 5.4.0-81-generic, ubuntu 20.04 zfs-linux - are correct bugreport package? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.12 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Aug 20 20:39:14 2021 InstallationDate: Installed on 2019-12-28 (600 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-04-23 (483 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Отказано в доступе: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1940703 Title: Ubuntu cannot find module "l2arc_rebuild_enabled" Status in zfs-linux package in Ubuntu: New Bug description: Good day. I tried to make l2arc cache persistent after reboot, add option to /etc/modprobe.d/zfs.conf options zfs zfs_arc_max=6294967296 but after reboot: dmesg [ +0,011105] zfs: unknown parameter 'l2arc_rebuild_enabled' ignored all modules? ls /sys/module/zfs/parameters/l2arc_ l2arc_feed_again l2arc_feed_min_ms l2arc_feed_secs l2arc_headrooml2arc_headroom_boost l2arc_noprefetch l2arc_norw l2arc_write_boost l2arc_write_max 5.4.0-81-generic, ubuntu 20.04 zfs-linux - are correct bugreport package? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.12 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Aug 20 20:39:14 2021 InstallationDate: Installed on 2019-12-28 (600 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-04-23 (483 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Отказано в доступе: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1940703/+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 1936452] Re: [SRU][F/H/I] Add MT7921 wifi fw
Lsusb output ** Attachment added: "lsusb_output.txt" https://bugs.launchpad.net/hwe-next/+bug/1936452/+attachment/5519474/+files/lsusb_output.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+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 1936452] Re: [SRU][F/H/I] Add MT7921 wifi fw
Lspci output ** Attachment added: "lspci_output.txt" https://bugs.launchpad.net/hwe-next/+bug/1936452/+attachment/5519473/+files/lspci_output.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+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 1936452] Re: [SRU][F/H/I] Add MT7921 wifi fw
I should probably mention that the card is working on Windows. I believe that I have done most of the things necessary for a proper dual boot, I have disabled hibernation entirely, I have disabled fast boot in the BIOS, and I always shut-down Windows with the command "shutdown /s /f /t 0" from an admin prompt. ** Attachment added: "Dmesg output" https://bugs.launchpad.net/hwe-next/+bug/1936452/+attachment/5519470/+files/dmesg_output.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+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 1939855] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1939855 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939855 Title: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in dellserver: Incomplete Status in focal package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1939855/+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 1939855] Re: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
Additionally, just for completeness, which cards are these (I know it's the E810 controller, but I'm wondering about specific card models) -- 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/1939855 Title: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in dellserver: Incomplete Status in focal package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1939855/+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 1939855] Re: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
This card is using firmware version 2.33 -- 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/1939855 Title: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in dellserver: Incomplete Status in focal package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1939855/+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 1939855] Re: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
Can you give us the firmware version for this failing controller? ** Changed in: dellserver Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939855 Title: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in dellserver: Incomplete Status in focal package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1939855/+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 1939855] Re: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
** Information type changed from Private to Public -- 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/1939855 Title: ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in dellserver: Incomplete Status in focal package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1939855/+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 1690085]
https://www.besanttechnologies.com/training-courses/amazon-web-services-training-in-bangalore https://www.besanttechnologies.com/training-courses/amazon-web-services-training-in-bangalore https://www.besanttechnologies.com/training-courses/amazon-web-services-training-in-bangalore -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/4.15.0.156.145)
All autopkgtests for the newly accepted linux-meta (4.15.0.156.145) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux/4.15.0-156.163 (ppc64el, amd64, i386) systemd/237-3ubuntu10.51 (ppc64el) lxc/3.0.3-0ubuntu1~18.04.1 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935846 Title: Sony Dualshock 4 usb dongle crashes the whole system Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Sony Dualshock 4 controller crashes systems. This is the result of a divide by zero when the driver processes requests from Steam and returns invalid data. More details are in the patch description. [Fix] Check whether data is valid and retry up to 3 times if needed. [Test Case] Tested by the bug reporter of LP:1935846. No more crashes after applying this patch. [Where problems could occur] None. The patch checks whether data is valid and retry 3 times before return -EILSEQ if it still fails. == Original descriptions == The hid-sony driver has custom DS4 connect/disconnect logic for the DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth connected DS4. The connect/disconnect logic works fine generally, however not in conjunction with Steam. Steam implements its own DS4 driver using hidraw. Both hid-sony and Steam are issuing their own HID requests and are racing each other during DS4 dongle connect/disconnect resulting in a kernel crash in hid-sony. The problem is that upon a DS4 connect to the dongle, hid-sony kicks of 'ds4_get_calibration_data' from within its dongle hotplug code. The calibration code issues raw HID feature report for reportID 0x02. When Steam is running, it issues a feature report for reportID 0x12 typically just prior to hid-sony requesting feature reportID 0x02. The result is that 'ds4_get_calibration_data' receives the data Steam requested as that's the HID report returing first. Currently this results in it processing invalid data, which ultimately results in a divide by zero upon a future 'dualshock4_parse_report'. The solution for now is to check within 'ds4_get_calibration_data' to check if we received data for the feature report we issued and if not retry. Please consider to add this patch to Ubuntu LTS kernels. Commit: https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935846/+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 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
"Acked-by: Tim Gardner I think for Hirsute this could wait until its at least in linux-next." I have looked into the Hirsute Linux firmware package linux-firmware_1.197_all.deb The header of the QCA9984 firmware file says: QCA-ATH10K 10.4-3.9.0.2-00131 This means that QCA9984 cards are not functional under Hirsute for the time being. so users have only the possibility to downgrade the firmware to 70 to 91 to get a working card With the packages from Hirsute alone, the cards are definitely not functional. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939937 Title: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support") in v5.11 fails firmware loading without IRAM recovery feature. However, the latest firmware from https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 doesn't support IRAM, it follows new official ath10k firmwares may no longer be loadable for kernel newer than v5.11. [Fix] A fix is proposed to http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that turns the lack/failure of IRAM recovery support a warning instead. [Test Case] With this fix, kernel gives errors about the IRAM supportness, but proceeds to remaining procedures as before. ath10k_pci :04:00.0: No hardware memory ath10k_pci :04:00.0: failed to copy target iram contents: -12 ath10k_pci :07:00.0: No hardware memory ath10k_pci :07:00.0: failed to copy target iram contents: -12 [Where problems could occur] So the IRAM recovery feature may or may not be supported in the officially released firmware, and people meet problems when using non-IRAM supported firmware may still have a fallback to use older, but IRAM recovery supported ones. == original bug report == Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [
[Kernel-packages] [Bug 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
Ok, so the commits are definitely _not_ in 81, but got introduced with 82 (which is not available as binary kernel, since it got superseded by 83): ~/ubuntu-focal-master-next$ git describe --abbrev=0 Ubuntu-5.4.0-83.93 ~/ubuntu-focal-master-next$ git log --oneline --grep "s390/uv: add prot virt guest/host indication files" 319423704db0 s390/uv: fix prot virt host indication compilation aee56e7b76eb s390/uv: add prot virt guest/host indication files ~/ubuntu-focal-master-next$ git tag --contains 319423704db0 | grep ^Ubuntu Ubuntu-5.4.0-82.92 Ubuntu-5.4.0-83.93 ~/ubuntu-focal-master-next$ git tag --contains aee56e7b76eb | grep ^Ubuntu Ubuntu-5.4.0-82.92 Ubuntu-5.4.0-83.93 Since the code obviously works if being integrated into the hirsute 5.11 kernel, I assume that some patches are missing that need to be picked for the 5.4 kernel on top of these two. Would you mind reaching out to Vikor and checking what might be missing for the 5.4 kernel? (see comment #2) -- 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/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.11.0.1017.18)
All autopkgtests for the newly accepted linux-meta-oracle (5.11.0.1017.18) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: jool/unknown (arm64) bbswitch/unknown (arm64) acpi-call/unknown (arm64) openrazer/unknown (arm64) libvpoll-eventfd/unknown (arm64) mali-midgard/unknown (arm64) west-chamber/unknown (arm64) ddcci-driver-linux/unknown (arm64) openafs/unknown (arm64) r8168/unknown (arm64) adv-17v35x/unknown (arm64) backport-iwlwifi-dkms/unknown (arm64) lime-forensics/unknown (arm64) digimend-dkms/unknown (arm64) v4l2loopback/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-oracle [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown
Can you please give this kernel a try: https://people.canonical.com/~khfeng/lp1912935-d3cold/ -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1940513] Re: Hang on Shutdown with AMD Ryzen 5700G
Is this a regression? -- 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/1940513 Title: Hang on Shutdown with AMD Ryzen 5700G Status in linux package in Ubuntu: Confirmed Bug description: Hi, i upgraded my System. Before I had a Ryzen 3200G. Now I have an Ryzen 5700G. Both systems running on an Linux Mint 20.2, Kernel 5.11.0-27, ASUS B450N-A Mainboard. 8GB DDR4-3200. When I shutdown or reboot the System the Execution won't be finished. The Linux Logo is displayed on one of my to screens. Than nothing happens. Than the Drive-led will flash shortly after some seconds. This will also happen with Kernel 5.13 Thx n greez --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thorsten 1292 F pulseaudio /dev/snd/controlC0: thorsten 1292 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-04-17 (124 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: Tags: uma Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/13/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3205 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3205:bd07/13/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940513/+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 1923335] Re: At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works)
plymouth have a rework of the shutdown handling in the git. https://cgit.freedesktop.org/plymouth/log/ Maybe that helps. -- 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/1923335 Title: At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works) Status in linux package in Ubuntu: In Progress Bug description: At shutdown the spinner logo disapear and a scond later it comes back and stay for 15sec. When I remove "splash" from the grub commandline the shutdown is fast (no extra 15 sec.). I can't find any hints in the log. It seem to happen after the log stopped. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-01-29 (71 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210129) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5580 Package: plymouth 0.9.5-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: wayland-session hirsute TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2020 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 00C013 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd09/25/2020:br1.18:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn00C013:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.product.sku: 07A8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923335/+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 1940629] Re: Support Jasper Lake
Thanks Andi for original patches and the bug report. -- 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/1940629 Title: Support Jasper Lake Status in OEM Priority Project: New Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: In Progress Status in thermald source package in Hirsute: In Progress Status in thermald source package in Impish: In Progress Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+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 1940629] Re: Support Jasper Lake
I've uploaded the fix for thermald_2.4.6-2 impish to debian, will get this sync'd over the next 24-36 hours into ubuntu. I've uploaded the fixed for hirsute and focal and renamed the patches so that they are in numerical order in the patch series. ** Changed in: thermald (Ubuntu Hirsute) Status: New => In Progress ** Changed in: thermald (Ubuntu Focal) Status: New => In Progress ** Changed in: thermald (Ubuntu Focal) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: thermald (Ubuntu Hirsute) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: thermald (Ubuntu Hirsute) Importance: Undecided => Critical ** Changed in: thermald (Ubuntu Focal) Importance: Undecided => Critical -- 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/1940629 Title: Support Jasper Lake Status in OEM Priority Project: New Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: In Progress Status in thermald source package in Hirsute: In Progress Status in thermald source package in Impish: In Progress Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+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 1933173] Comment bridged from LTC Bugzilla
--- Comment From fran...@de.ibm.com 2021-08-20 11:02 EDT--- Seems like I didn't state it obviously enough. I already tried 5.4.0-83-generic and since that wasn't working I then installed the -81 from the link but it also doesn't 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/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+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 1925261] Re: memory leak on AWS kernels when using docker
Paul - the commit you've referenced in #3 is a merge commit from the 5.9 kernel. None of the commits in that block appear to address a memory leak. Can you tell me how you came to the conclusion that this commit fixes your problem ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1925261 Title: memory leak on AWS kernels when using docker Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: New Bug description: Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu AMI was released which has the "5.3.0-1032-aws" kernel we have been hitting a 100% repro memory leak that causes our app that is running under docker to be OOM killed. The scenario is that we have an app running in a docker container and it occasionally catches a crash happening within itself and when that happens it creates another process which triggers a gdb dump of that parent app. Normally this works fine but under these specific kernels it causes the memory usage to grow and grow until it hits the maximum allowed memory for the container at which point the container is killed. I have tested using several of the latest available Ubuntu AMIs including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which has the "5.4.0-1045-aws" kernel and the bug still exists. I also tested a bunch of the mainline kernels and found the fix was introduced for this memory leak in the v5.9-rc4 kernel (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES). Do you all have any idea if or when that set of changes will be backported into a supported kernel for Ubuntu 18.04 or 20.04? Release we are running: root@:~# lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 Docker / containerd.io versions: - containerd.io: 1.4.4-1 - docker-ce: 5:20.10.5~3-0~ubuntu-bionic Latest supported kernel I tried which still sees the memory leak: root@hostname:~# apt-cache policy linux-aws linux-aws: Installed: 5.4.0.1045.27 Candidate: 5.4.0.1045.27 Version table: *** 5.4.0.1045.27 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1007.7 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Thanks, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1925261/+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 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
Thanks for sharing the output. Looks like the active kernel on your system is still 5.4.0-81, but the installed kernel is already 5.4.0.83. So just a reboot is needed to get the recently installed kernel 5.4.0-83 active and running. 5.4.0.83 should have the patches in (I'm pretty sure, just need to update my clone to be absolutely sure.) It should have been already in 5.4.0-82, but that got superseded by 83 on short notice due to security reasons (it incl. several CVE fixes). (But I'm still wondering why this is not referenced [with pointing to this LP bug number] in the changelog ...) -- 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/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+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 1940629] Re: Support Jasper Lake
** Also affects: thermald (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: thermald (Ubuntu Impish) Importance: Critical Assignee: Colin Ian King (colin-king) Status: In Progress ** Also affects: thermald (Ubuntu Hirsute) Importance: Undecided Status: New -- 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/1940629 Title: Support Jasper Lake Status in OEM Priority Project: New Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: New Status in thermald source package in Hirsute: New Status in thermald source package in Impish: In Progress Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+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 1940665] [NEW] Lenovo Carbon X1 9th gen no longer powers off
Public bug reported: Ubuntu 20.04.3 LTS linux-oem-5.10: 5.10.0-1044.46 Power off system, either through GUI or by shutdown -P now Expected result: System powers completely off What happens: System seems to be powering completely off. Screen goes black, but computer is still running, getting hot and using battery. Have to press power button for 4 seconds to power completely off. Solution so far: Use linux-generic-something ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1940665 Title: Lenovo Carbon X1 9th gen no longer powers off Status in linux-oem-5.10 package in Ubuntu: New Bug description: Ubuntu 20.04.3 LTS linux-oem-5.10: 5.10.0-1044.46 Power off system, either through GUI or by shutdown -P now Expected result: System powers completely off What happens: System seems to be powering completely off. Screen goes black, but computer is still running, getting hot and using battery. Have to press power button for 4 seconds to power completely off. Solution so far: Use linux-generic-something To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1940665/+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 1933173] changelog
--- Comment (attachment only) From fran...@de.ibm.com 2021-08-20 10:13 EDT--- ** Attachment added: "changelog" https://bugs.launchpad.net/bugs/1933173/+attachment/5519406/+files/changelog -- 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/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+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 1933173] Comment bridged from LTC Bugzilla
--- Comment From fran...@de.ibm.com 2021-08-20 10:13 EDT--- janosch@u2004:~$ uname -a Linux u2004 5.4.0-81-generic #91~lp1933173-Ubuntu SMP Wed Aug 4 09:35:44 UTC 2021 s390x s390x s390x GNU/Linux janosch@u2004:~$ apt-cache policy linux-generic linux-generic: Installed: 5.4.0.83.87 Candidate: 5.4.0.83.87 Version table: *** 5.4.0.83.87 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main s390x Packages 100 /var/lib/dpkg/status 5.4.0.81.85 500 500 http://us.ports.ubuntu.com/ubuntu-ports focal-updates/main s390x Packages 500 http://us.ports.ubuntu.com/ubuntu-ports focal-security/main s390x Packages 5.4.0.26.32 500 500 http://us.ports.ubuntu.com/ubuntu-ports focal/main s390x Packages -- 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/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+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 1890848] Re: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
Tested on bionic-proposed using the test binary that can be obtained in the old description and it worked as expected: root@ubuntu:~# gcc ./readlink-ns.c && sudo apparmor_parser -r ./readlink-ns.apparmor && sudo aa-exec -p test -- ./a.out -p 1 -n pid path: /proc/1/ns/pid rpath: pid:[4026531836] root@ubuntu:~# uname -a Linux ubuntu 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1890848 Title: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: [Impact] Permission 'ptrace trace' is required to readlink() /proc/*/ns/*, when only 'ptrace read' should be required according to 'man namespaces': "Permission to dereference or read (readlink(2)) these symbolic links is governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see ptrace(2)." [Fix] Upstream commit 338d0be437ef10e247a35aed83dbab182cf406a2 fixes ptrace read check. [Test Plan] BugLink contains the source of a binary that reproduces the issue. In summary, it executes readlink() on /proc/*/ns/*. There's also a policy that has only 'ptrace read' permission. When the bug is fixed, execution is allowed. [Where problems could occur] The regression can be considered as low, since it's lowering the number of permissions required. Existing policies that already contain the permission 'ptrace trace' and 'ptrace read' will have a broader policy than required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890848/+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 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
Hmm - looks like the patches weren't applied to that kernel (for whatever reason). Please could you share the out put of the following 3 commands here: uname -a apt-cache policy linux-generic apt changelog linux-generic -- 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/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.4.0.83.87)
All autopkgtests for the newly accepted linux-meta (5.4.0.83.87) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (ppc64el, arm64, amd64) lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933337] Re: bcmwl fails to build with 5.11 HWE-edge kernel on Ubuntu 20.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/197 Title: bcmwl fails to build with 5.11 HWE-edge kernel on Ubuntu 20.04 LTS Status in bcmwl package in Ubuntu: Confirmed Bug description: When trying to build bcmwl using the latest 5.11 HWE-edge kernel on Ubuntu 20.04 LTS, the kernel module will refuse to build: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] 461 | fs = get_fs(); | ^~ | get_ds /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: incompatible types when assigning to type ‘mm_segment_t’ from type ‘int’ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:2: error: implicit declaration of function ‘set_fs’; did you mean ‘sget_fc’? [-Werror=implicit-function-declaration] 462 | set_fs(get_ds()); | ^~ | sget_fc In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:26: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’? 600 | #define get_ds() (KERNEL_DS) | ^ I understand that a fix for this has been rolled out to Hirsuite (0029-Update-for-set_fs-removal-in-Linux-5.10.patch). Can this fix please be backported to Focal? Since it fixes the problem for people needing to run LTS and use the HWE-Edge kernel for any given reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/197/+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 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
attached please find a new log - set about the most recent crash. Trailing there is the result of "uname -a" in the log file. ** Attachment added: "dmesg_20aug2021_wilhelm_AMD-APU__VM_L2_PROTECTION_FAULT_STATUS.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+attachment/5519400/+files/dmesg_20aug2021_wilhelm_AMD-APU__VM_L2_PROTECTION_FAULT_STATUS.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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
Launchpad has imported 42 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=197683. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-11-02T10:20:39+00:00 kai.heng.feng wrote: Users reported [1] trackpad locked into scroll mode, I personally cannot reproduce the issue though. The issue happens because the trackpad think there's a finger still touched on the touchpad, hence move a single finger on the touchpad will be treated as two fingers scroll. Also, users reported this commit doesn't fully solve the issue for them: commit 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce Author: Benjamin Tissoires Date: Thu Jun 15 15:32:04 2017 +0200 HID: multitouch: fix rare Win 8 cases when the touch up event gets missing Reload driver (both hid-multitouch and i2c-hid) does not solve the issue. There's still a phantom finger on the touchpad. [1] https://bugs.launchpad.net/bugs/1651635 Reply at: https://bugs.launchpad.net/dell- sputnik/+bug/1651635/comments/128 On 2017-11-02T11:21:48+00:00 Esokrarkose wrote: Clicking releases from scroll lock, but most of the times only temporary, meaning a few seconds later it locks again. In the end its stops happening suddenly to return at a later point. This issue is NOT reproducible, it sometimes stays away from me for weeks and then it hits me and makes using the touchpad almost impossible. Sometimes it happends everyday. Please do not use the machine for a few hours and then say everything is fine because you did not see it. The issue is definitely there for all kernels <= 4.13, I have two machines, on both I experience this issue and there are other users who see the same issue, see [1]. [1] https://bugs.launchpad.net/bugs/1651635 Reply at: https://bugs.launchpad.net/dell- sputnik/+bug/1651635/comments/131 On 2017-11-03T10:17:45+00:00 benjamin.tissoires wrote: Thanks for raising this issue. I currently have a Dell XPS 9360 as a loaner so the timing is perfect. I haven't used it enough to trigger the issue on a vanilla kernel however. Given that the scroll lock happens even if the hid-multitouch and i2c-hid modules are removed and re-added, I would *think* the issue is in user space, not in kernel space. The reason is that the last data in comment #110 show that the kernel is behaving properly by rejecting the ghost touches on my system if I replay the data. Once the bug is triggered, could you ask the user who triggered it to rmmod i2c-hid and modprobe it back with debug=1, and attach the output of dmesg here? This should show the exact starting sequence of the bug, and we will be able to rule out if it is a kernel or a user space issue. Reply at: https://bugs.launchpad.net/dell- sputnik/+bug/1651635/comments/134 On 2017-11-06T23:01:42+00:00 Esokrarkose wrote: Created attachment 260527 Scroll lock that vanishes very fast My touchpad is in the state again that I can trigger the bug deliberately, but not a really nasty lock, only for a few seconds. I started to load the module with debug mode, started scrolling with two fingers, released one finger and it kept scrolling. I even removed the finger touched again to move the cursor but it still was in scroll mode. The issue resolved itself again without any click. Hope you can find something in there, at the moment the locks only last very shortly for me. Reply at: https://bugs.launchpad.net/dell- sputnik/+bug/1651635/comments/136 On 2017-11-07T19:54:40+00:00 Esokrarkose wrote: Created attachment 260545 kern.log from events in the video The touchpad started misbehaving again, but not as badly as it could be. I started to film the problem, see https://www.youtube.com/watch?v=HpAWC8imIcc In the video I first show off the scroll lock happening, then I run a script that reloads the i2c-hid module with debug info and shows a timestamp every second, for you to get a better understanding of what happened at which point in time in the attached kern.log file. You can also see the mouse cursor jumping at 0:50. Reply at: https://bugs.launchpad.net/dell- sputnik/+bug/1651635/comments/137 On 2017-11-07T21:11:11+00:00 benjamin.tissoires wrote: Thanks for both logs and the video. This makes things easier to see and understand. The first log did show a ghost touch on the upper right corner of the touchpad, but I wasn't sure if you accidentally touched this part of the touchpad or
[Kernel-packages] [Bug 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
--- Comment From fran...@de.ibm.com 2021-08-20 08:53 EDT--- Verification failed. I installed a Ubuntu 20.04 guest and enabled focal-proposed which bumped up my kernel to 5.4.0-83-generic. There's no "uv" directory in /sys/firmware/ on that kernel version. I also tried the linked 5.4.0-81 deb with the same results. ** Tags removed: verification-needed-focal ** Tags added: verification-failed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+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 1940564] Re: bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3
Booted in a Standard_D48_v3 instance: uname -a Linux selfprovisioned-rtg-bionic 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Tagging verification-done-bionic ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1940564 Title: bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: [Impact] bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3 [Fix] revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to v4.14.240, v4.19.198" This commit originates from an unreleased kernel (5.14-rc1). According to the commit log it purports to head off possible future problems. It does not appear to address a specific bug. It has been backported to 4.14.y and 4.19.y. [Test Plan] Install and boot on an Azure Standard_D48_v3 instance. [Where problems could occur] iscsi requests could hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940564/+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 1940392] Re: fs: removing mandatory locks
https://lists.ubuntu.com/archives/kernel-team/2021-August/123424.html ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed -- 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/1940392 Title: fs: removing mandatory locks Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: Hello, Upstream is dicussing the removal of mandatory locks. To actually do this at some point distros will need to start disabling CONFIG_MANDATORY_FILE_LOCKING. It seems our kernel still defaults to CONFIG_MANDATORY_FILE_LOCKING=y. If feasible I'd like to propose disabling CONFIG_MANDATORY_FILE_LOCKING in the upcoming kernel releases. From the thread it seems that RHEL 8 and Fedora already disable mandatory locks: https://lore.kernel.org/lkml/c65c4e42-9661-1321-eaf8-61b1d6f89...@redhat.com Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940392/+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 1890848] Re: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1890848 Title: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: [Impact] Permission 'ptrace trace' is required to readlink() /proc/*/ns/*, when only 'ptrace read' should be required according to 'man namespaces': "Permission to dereference or read (readlink(2)) these symbolic links is governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see ptrace(2)." [Fix] Upstream commit 338d0be437ef10e247a35aed83dbab182cf406a2 fixes ptrace read check. [Test Plan] BugLink contains the source of a binary that reproduces the issue. In summary, it executes readlink() on /proc/*/ns/*. There's also a policy that has only 'ptrace read' permission. When the bug is fixed, execution is allowed. [Where problems could occur] The regression can be considered as low, since it's lowering the number of permissions required. Existing policies that already contain the permission 'ptrace trace' and 'ptrace read' will have a broader policy than required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890848/+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 787738]
I'm now running kernel 5.10 on Debian. I finally got tired of it enough a few months ago and replaced the keyboard and all of my issues resolved. There are enough people reporting the problem here that it may seem this is a common failure mode for this keyboard. -- 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/787738 Title: [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd behaviour Status in Linux: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Natty: Invalid Status in linux source package in Oneiric: Invalid Status in Fedora: New Bug description: Using the touchpad does not result in expected behavior. The touchpad has three "mouse" buttons on top, and none of these buttons currently function. Using xev does not show any output from these buttons. The touchpad itself works fine. There are two bottom buttons integrated with the touchpad, which do not work consistantly. The left button will sometimes act like a left-click and sometime like a right click, making it hard to move applications on the screen. The right button acts like a left click and only sometimes bring up menus. Trying to change from a left hand to a right hand mouse in mouse options does not change the behavior. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1235 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd252 irq 44' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21da,0010 HDA:80862805,80860101,0010' Controls : 20 Simple ctrls : 8 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue May 24 14:44:59 2011 HibernationDevice: RESUME=UUID=dd9d30b2-4950-42af-87e2-b304fc01e83d InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 428623U ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=4985f74f-9e44-411f-8d41-73f9f68c057d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET28WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: 428623U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET28WW(1.00):bd01/25/2011:svnLENOVO:pn428623U:pvrThinkPadX220:rvnLENOVO:rn428623U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 428623U dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/787738/+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 787738]
Have the same problem as Will with my T480 on kernel 5.4.0-80-generic (Ubuntu 20.04.2 LTS). One can bring it back for a couple of minutes with the following: sudo rmmod -f psmouse sudo modprobe -v psmouse resync_time=5 resetafter=5 Also have a look at xinput --list to see if it both devices (synaptics and trackpoint) came back. However, the same dmesg error pops up after some minutes... -- 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/787738 Title: [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd behaviour Status in Linux: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Natty: Invalid Status in linux source package in Oneiric: Invalid Status in Fedora: New Bug description: Using the touchpad does not result in expected behavior. The touchpad has three "mouse" buttons on top, and none of these buttons currently function. Using xev does not show any output from these buttons. The touchpad itself works fine. There are two bottom buttons integrated with the touchpad, which do not work consistantly. The left button will sometimes act like a left-click and sometime like a right click, making it hard to move applications on the screen. The right button acts like a left click and only sometimes bring up menus. Trying to change from a left hand to a right hand mouse in mouse options does not change the behavior. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1235 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd252 irq 44' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21da,0010 HDA:80862805,80860101,0010' Controls : 20 Simple ctrls : 8 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue May 24 14:44:59 2011 HibernationDevice: RESUME=UUID=dd9d30b2-4950-42af-87e2-b304fc01e83d InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 428623U ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=4985f74f-9e44-411f-8d41-73f9f68c057d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET28WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: 428623U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET28WW(1.00):bd01/25/2011:svnLENOVO:pn428623U:pvrThinkPadX220:rvnLENOVO:rn428623U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 428623U dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/787738/+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 1935040] Re: dev_forward_skb: do not scrub skb mark within the same name space
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1935040 Title: dev_forward_skb: do not scrub skb mark within the same name space Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] The ebpf function 'bpf_redirect' reset the mark when used with the flag BPF_F_INGRESS. There are two main problems with that: - it's not consistent between legacy tunnels and ebpf; - it's not consistent between ingress and egress. In fact, the eBPF program can easily reset the mark, but it cannot preserve it. This kind of patch was already done in the past, see commit 963a88b31ddb ("tunnels: harmonize cleanup done on skb on xmit path"), commit ea23192e8e57 ("tunnels: harmonize cleanup done on skb on rx path") and commit 213dd74aee76 ("skbuff: Do not scrub skb mark within the same name space"). This is fixed upstream with commit ff70202b2d1a ("dev_forward_skb: do not scrub skb mark within the same name space"). https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff70202b2d1a [Test Case] Mark a packet in the POSTROUTING hook, redirect it to another interface and display it with a netfilter log rule to check the mark. [Regression Potential] A user could expect that the mark is reset after a call to bpf_redirect(BPF_F_INGRESS), but he could easily reset it in the eBPF program himself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935040/+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 1940564] Re: bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1940564 Title: bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: [Impact] bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3 [Fix] revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to v4.14.240, v4.19.198" This commit originates from an unreleased kernel (5.14-rc1). According to the commit log it purports to head off possible future problems. It does not appear to address a specific bug. It has been backported to 4.14.y and 4.19.y. [Test Plan] Install and boot on an Azure Standard_D48_v3 instance. [Where problems could occur] iscsi requests could hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940564/+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 1940134] Re: fails to launch linux L2 guests on AMD
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1940134 Title: fails to launch linux L2 guests on AMD Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-hwe-5.8 source package in Focal: Invalid Status in linux source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Bug description: [Impact] Users won't be able to run a Linux inside a Linux guest. [Test case] Launch an L1 guest with libvirt, then launch an L2 guest using qemu inside that first/L1 guest. [Potential regression] There might be reduced performance due to vmexits for interrupt handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+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 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
SRU: https://lists.ubuntu.com/archives/kernel- team/2021-August/123436.html (oem-5.13, hirsute, impish, unstable) ** Description changed: + [SRU Justification] + + [Impact] + + Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support") + in v5.11 fails firmware loading without IRAM recovery feature. However, + the latest firmware from + https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 + doesn't support IRAM, it follows new official ath10k firmwares may no + longer be loadable for kernel newer than v5.11. + + [Fix] + + A fix is proposed to + http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that + turns the lack/failure of IRAM recovery support a warning instead. + + [Test Case] + + With this fix, kernel gives errors about the IRAM supportness, but + proceeds to remaining procedures as before. + + ath10k_pci :04:00.0: No hardware memory + ath10k_pci :04:00.0: failed to copy target iram contents: -12 + ath10k_pci :07:00.0: No hardware memory + ath10k_pci :07:00.0: failed to copy target iram contents: -12 + + [Where problems could occur] + + So the IRAM recovery feature may or may not be supported in the + officially released firmware, and people meet problems when using + non-IRAM supported firmware may still have a fallback to use older, but + IRAM recovery supported ones. + + == original bug report == + Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. - dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.047910] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [7.103260] ath10k_pci :03:00.0: could not init core (-12) [7.103267] ath10k_pci :03:00.0: could not probe fw (-12) [7.108570] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [7.163247] ath10k_pci :04:00.0: could not init core (-12) [7.163268] ath10k_pci :04:00.0: could not probe fw (-12) - - In the ath10k mailing list I found a second patch which makes it possible to load the latest firmware on the card again. + In the ath10k mailing list I found a second patch which makes it + possible to load the latest firmware on the card again. https://www.mail-archive.com/ath10k@lists.infradead.org/msg13655.html I have tested the patch and it works. dmesg: [18245.610112] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.674800] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.731606] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
[Kernel-packages] [Bug 1900254] Re: fails to suspend unless I unbind a device from elants_i2c driver
Launchpad has imported 54 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=207759. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-05-16T16:51:08+00:00 dl3it wrote: The Elantech Touchscreen is not working in Lenovo Ideapad 5 15. [0.550596] elants_i2c i2c-ELAN0001:00: i2c-ELAN0001:00 supply vcc33 not found, using dummy regulator [0.551836] elants_i2c i2c-ELAN0001:00: i2c-ELAN0001:00 supply vccio not found, using dummy regulator [0.560932] elants_i2c i2c-ELAN0001:00: elants_i2c_send failed (77 77 77 77): -121 [0.562427] elants_i2c i2c-ELAN0001:00: software reset failed: -121 [0.595925] elants_i2c i2c-ELAN0001:00: elants_i2c_send failed (77 77 77 77): -121 [0.597974] elants_i2c i2c-ELAN0001:00: software reset failed: -121 [0.621893] elants_i2c i2c-ELAN0001:00: elants_i2c_send failed (77 77 77 77): -121 [0.622504] elants_i2c i2c-ELAN0001:00: software reset failed: -121 [0.632650] elants_i2c i2c-ELAN0001:00: elants_i2c_send failed (4d 61 69 6e): -121 [0.634256] elants_i2c i2c-ELAN0001:00: boot failed: -121 [0.699212] elants_i2c i2c-ELAN0001:00: invalid 'hello' packet: 00 00 ff ff [1.630506] elants_i2c i2c-ELAN0001:00: Failed to read fw id: -121 [1.645508] elants_i2c i2c-ELAN0001:00: unknown packet 00 00 ff ff When booting a test Windows10 (sorry..), it works; so a HW fault can be excluded. When using it, it produces errors: [ 933.159820] elants_i2c i2c-ELAN0001:00: unknown packet 0e 00 04 03 [ 933.167034] elants_i2c i2c-ELAN0001:00: unknown packet 0e 00 04 03 [ 933.172617] elants_i2c i2c-ELAN0001:00: unknown packet 0e 00 04 13 [ 933.180073] elants_i2c i2c-ELAN0001:00: unknown packet 0e 00 04 03 [ 933.185652] elants_i2c i2c-ELAN0001:00: unknown packet 0e 00 04 13 [ 933.192860] elants_i2c i2c-ELAN0001:00: unknown packet 0e 00 04 03 [ 933.198440] elants_i2c i2c-ELAN0001:00: unknown packet 0e 00 04 13 and so on... Same beheaviour for kernel 5.4.xx and 5.6.xx Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- oem-5.6/+bug/1900254/comments/0 On 2020-06-02T06:23:43+00:00 dirkneukirchen wrote: 2 users of Manjaro reported the same errors on their Lenovo Ideapad 5 manjaro forum report: https://forum.manjaro.org/t/elan-touchpad-not- working/143624 Also strange that its using elants_i2c instead of elan_i2c (or generic ones) but seems similar to https://bugzilla.kernel.org/show_bug.cgi?id=203467 Maybe its hardware design issue ? I have no idea why "i8042.dumbkbd=1" would help - are these touchpad / elan "touchscreens" connected to I2C and PS2 and SMBus ? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- oem-5.6/+bug/1900254/comments/1 On 2020-06-02T08:04:33+00:00 dl3it wrote: I fixed it temporarily by changing elants_i2c from "built in" to "module". It works flawlessly now. I would not expect a hardware issue. It looks more like the module beeing started too early. The whole I2C is dead, when running elants_i2c as a module. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- oem-5.6/+bug/1900254/comments/2 On 2020-06-02T10:49:56+00:00 dirkneukirchen wrote: So effectively you blacklist the module because "The whole I2C is dead, when running elants_i2c as a module." reads for me like elants_i2c no longer manages the touchpad. What driver or connection is that input using now? / What dmesg looks when it finds the touchpad ? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- oem-5.6/+bug/1900254/comments/3 On 2020-06-02T11:21:33+00:00 dl3it wrote: Created attachment 289469 dmesg / kernel log Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- oem-5.6/+bug/1900254/comments/4 On 2020-06-02T11:23:38+00:00 dl3it wrote: I fetched a kernel from kernel.org (5.6.14 and 5.7.0-rc7). make menuconfig Device Drivers -> Input device support -> Touchscreens -> Elan eKTH I2C touchscreen -->> set to m rebuild kernel and install... The driver is no longer loaded as built in, but as a module. This leads to a delay of ca. 3-4s. Somehow this seems to help. The Touchpad/screen is connected via i2c1. dl3it@IdeaPad:~$ dmesg | grep ELAN [1.583560] i2c_hid i2c-ELAN0001:00: supply vdd not found, using dummy regulator [1.583575] i2c_hid i2c-ELAN0001:00: supply vddl not found, using dummy regulator [1.646025] input: ELAN0001:00 04F3:3140 Mouse as
[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-intel source package in Focal: New Status in linux source package in Hirsute: Fix Committed Status in linux-intel source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] The USB devices (keyboard, storage...) are failed to be detected when connecting to the problematic root hubs which need longer PowerOn-to-PowerGood delay than it claims in the hub descriptor. It's caused by the upstream fix 90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub"). [Fix] Reverting the upstream fix until a formal fix been placed. [Test Case] 1. Plug the USB device to the ports of problematic root hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Regression Potential] Low. The longer delay is proven safe in old kernels. == Original Bug Description == [Summary] The USB devices (keyboard, storage...) are failed to be detected during boot after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, they will be detected and working ok after re-plugging. The kernel output shows as down below during boot [ 39.350435] hub 1-0:1.0: USB hub found [ 39.398835] hub 1-0:1.0: 12 ports detected [ 39.622744] usb usb1-port3: couldn't allocate usb_device And when I plug out then plug in the same device, it shows [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, bcdDevice= 1.14 [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 After doing kernel bisecting, we found the upstream commit https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2 makes the difference. It indicates that the delay for the root hub from power_on to power_good is not long enough. There was no problem if the delay is 100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 milliseconds. And the XHCI spec also says in section 5.4.8 """ The host is required to have power stable to the port within 20 milliseconds of the '0' to '1' transition of PP. If PPC = '1', software is responsible for waiting 20ms. """ The commit seems to follow the SPEC but could cause problems on some hubs. [Reproduce Steps] 1. Plug the USB device to the physical port #1 and #4 which belongs to high-speed hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Results] Expected: All usb devices connect to the hub should work OK. Actual: USB devices connects to high-speed hub can not be probed. [Additional Information] Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26 [Upstream bug] https://bugzilla.kernel.org/show_bug.cgi?id=214021 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+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 1690085]
Agmon, thank you for your report. Please open a separate issue with the full output of `dmesg` attached, and the output of `acpidump`. Please reference the issues here. -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug
[Kernel-packages] [Bug 1690085]
"Transglobal Overseas Education Consultants is the leading Overseas Consultants in Delhi since 2010. We are providing Study visas, PR Visa, Tourist Visa, Spouse Visa with free admission guidance and free counseling. We provide Our services in UK, USA, Canada, Australia, New Zealand, Singapore. Our head office in Tilak Nagar and Branch Office is Banglore & Ahmedabad. We place the right student in the right universities." https://www.google.com/maps/place/Transglobal+Overseas+Education+Consultants/@28.6355308,77.0949389,17z/data=!3m1!4b1!4m5!3m4!1s0x390d049f4c17f821:0x53dd7da5bbf54bf!8m2!3d28.6355261!4d77.0971276;>overseas education consultants in delhi https://www.google.com/maps/place/Transglobal+Overseas+Education+Consultants/@28.6355308,77.0949389,17z/data=!3m1!4b1!4m5!3m4!1s0x390d049f4c17f821:0x53dd7da5bbf54bf!8m2!3d28.6355261!4d77.0971276;>abroad education consultants in delhi -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now,
[Kernel-packages] [Bug 1690085]
Hello, after while with random AMD Ryzen 5 reboots, final solution was add Kernel parameter: acpi_osi=Linux 3 days of stability with Ubuntu 18.04 5.4.0-80-generic and counting. -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about
[Kernel-packages] [Bug 1923335] Re: At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works)
I can confirm the bug is still in the latest kernels and that it was introduced in the 5.11 series: 5.10.16 - good 5.10.60 - good 5.11.1 - broken 5.14.0-051400rc6drmtip20210820 - broken Next will be to bisect in git but I won't have time to do that this week. -- 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/1923335 Title: At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works) Status in linux package in Ubuntu: In Progress Bug description: At shutdown the spinner logo disapear and a scond later it comes back and stay for 15sec. When I remove "splash" from the grub commandline the shutdown is fast (no extra 15 sec.). I can't find any hints in the log. It seem to happen after the log stopped. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-01-29 (71 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210129) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5580 Package: plymouth 0.9.5-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: wayland-session hirsute TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2020 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 00C013 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd09/25/2020:br1.18:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn00C013:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.product.sku: 07A8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923335/+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 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939937 Title: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.047910] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [7.103260] ath10k_pci :03:00.0: could not init core (-12) [7.103267] ath10k_pci :03:00.0: could not probe fw (-12) [7.108570] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [7.163247] ath10k_pci :04:00.0: could not init core (-12) [7.163268] ath10k_pci :04:00.0: could not probe fw (-12) In the ath10k mailing list I found a second patch which makes it possible to load the latest firmware on the card again. https://www.mail-archive.com/ath10k@lists.infradead.org/msg13655.html I have tested the patch and it works. dmesg: [18245.610112] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.674800] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.731606] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.731620] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.733172] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18245.790380] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.790383] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.790703] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18246.963760] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-intel source package in Focal: New Status in linux source package in Hirsute: Fix Committed Status in linux-intel source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] The USB devices (keyboard, storage...) are failed to be detected when connecting to the problematic root hubs which need longer PowerOn-to-PowerGood delay than it claims in the hub descriptor. It's caused by the upstream fix 90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub"). [Fix] Reverting the upstream fix until a formal fix been placed. [Test Case] 1. Plug the USB device to the ports of problematic root hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Regression Potential] Low. The longer delay is proven safe in old kernels. == Original Bug Description == [Summary] The USB devices (keyboard, storage...) are failed to be detected during boot after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, they will be detected and working ok after re-plugging. The kernel output shows as down below during boot [ 39.350435] hub 1-0:1.0: USB hub found [ 39.398835] hub 1-0:1.0: 12 ports detected [ 39.622744] usb usb1-port3: couldn't allocate usb_device And when I plug out then plug in the same device, it shows [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, bcdDevice= 1.14 [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 After doing kernel bisecting, we found the upstream commit https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2 makes the difference. It indicates that the delay for the root hub from power_on to power_good is not long enough. There was no problem if the delay is 100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 milliseconds. And the XHCI spec also says in section 5.4.8 """ The host is required to have power stable to the port within 20 milliseconds of the '0' to '1' transition of PP. If PPC = '1', software is responsible for waiting 20ms. """ The commit seems to follow the SPEC but could cause problems on some hubs. [Reproduce Steps] 1. Plug the USB device to the physical port #1 and #4 which belongs to high-speed hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Results] Expected: All usb devices connect to the hub should work OK. Actual: USB devices connects to high-speed hub can not be probed. [Additional Information] Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26 [Upstream bug] https://bugzilla.kernel.org/show_bug.cgi?id=214021 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+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 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935846 Title: Sony Dualshock 4 usb dongle crashes the whole system Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Sony Dualshock 4 controller crashes systems. This is the result of a divide by zero when the driver processes requests from Steam and returns invalid data. More details are in the patch description. [Fix] Check whether data is valid and retry up to 3 times if needed. [Test Case] Tested by the bug reporter of LP:1935846. No more crashes after applying this patch. [Where problems could occur] None. The patch checks whether data is valid and retry 3 times before return -EILSEQ if it still fails. == Original descriptions == The hid-sony driver has custom DS4 connect/disconnect logic for the DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth connected DS4. The connect/disconnect logic works fine generally, however not in conjunction with Steam. Steam implements its own DS4 driver using hidraw. Both hid-sony and Steam are issuing their own HID requests and are racing each other during DS4 dongle connect/disconnect resulting in a kernel crash in hid-sony. The problem is that upon a DS4 connect to the dongle, hid-sony kicks of 'ds4_get_calibration_data' from within its dongle hotplug code. The calibration code issues raw HID feature report for reportID 0x02. When Steam is running, it issues a feature report for reportID 0x12 typically just prior to hid-sony requesting feature reportID 0x02. The result is that 'ds4_get_calibration_data' receives the data Steam requested as that's the HID report returing first. Currently this results in it processing invalid data, which ultimately results in a divide by zero upon a future 'dualshock4_parse_report'. The solution for now is to check within 'ds4_get_calibration_data' to check if we received data for the feature report we issued and if not retry. Please consider to add this patch to Ubuntu LTS kernels. Commit: https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935846/+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 1935040] Re: dev_forward_skb: do not scrub skb mark within the same name space
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935040 Title: dev_forward_skb: do not scrub skb mark within the same name space Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] The ebpf function 'bpf_redirect' reset the mark when used with the flag BPF_F_INGRESS. There are two main problems with that: - it's not consistent between legacy tunnels and ebpf; - it's not consistent between ingress and egress. In fact, the eBPF program can easily reset the mark, but it cannot preserve it. This kind of patch was already done in the past, see commit 963a88b31ddb ("tunnels: harmonize cleanup done on skb on xmit path"), commit ea23192e8e57 ("tunnels: harmonize cleanup done on skb on rx path") and commit 213dd74aee76 ("skbuff: Do not scrub skb mark within the same name space"). This is fixed upstream with commit ff70202b2d1a ("dev_forward_skb: do not scrub skb mark within the same name space"). https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff70202b2d1a [Test Case] Mark a packet in the POSTROUTING hook, redirect it to another interface and display it with a netfilter log rule to check the mark. [Regression Potential] A user could expect that the mark is reset after a call to bpf_redirect(BPF_F_INGRESS), but he could easily reset it in the eBPF program himself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935040/+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 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+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 1940134] Re: fails to launch linux L2 guests on AMD
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1940134 Title: fails to launch linux L2 guests on AMD Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-hwe-5.8 source package in Focal: Invalid Status in linux source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Bug description: [Impact] Users won't be able to run a Linux inside a Linux guest. [Test case] Launch an L1 guest with libvirt, then launch an L2 guest using qemu inside that first/L1 guest. [Potential regression] There might be reduced performance due to vmexits for interrupt handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+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