[Kernel-packages] [Bug 1951668] 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 1951668 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/1951668 Title: touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: niklaus@niklaus-Nitro-AN517-54:~$ 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/PNP0A08:00/device:1c/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 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/input2 U: Uniq= H: Handlers=kbd event2 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/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse" P: Phys=usb-:00:14.0-5/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.0/0003:2717:003B.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B: KEY=e080ffdf01cf fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse" P: Phys=usb-:00:14.0-5/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.1/0003:2717:003B.0002/input/input6 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse Consumer Control" P: Phys=usb-:00:14.0-5/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.1/0003:2717:003B.0002/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=13 B: KEY=838c000 c 0 B: MSC=10 I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse Consumer Control" P: Phys=usb-:00:14.0-5/input2 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.2/0003:2717:003B.0003/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=1f B: KEY=302ff 0 0 48317aff32d bfd6 1 130ff38b17c000 677bfad941dfed 9ed6804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse Keyboard" P: Phys=usb-:00:14.0-5/input2 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.2/0003:2717:003B.0003/input/input9 U: Uniq= H: Handlers=sysrq kbd event9 B: PROP=0 B: EV=100013 B: KEY=e080ffdf01cf fffe B: MSC=10 I: Bus=0019 Vendor=1025 Product=1229 Version= N: Name="Acer Wireless Radio Control" P: Phys=acer-wireless/input0 S: Sysfs=/devices/LNXSYSTM:00/10251229:00/input/input10 U: Uniq= H: Handlers=rfkill kbd event10 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Acer WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input11 U: Uniq= H: Handlers=rfkill kbd event11 B: PROP=0 B: EV=13 B: KEY=1c 0 0 0 0 160080c00 30 10 0 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b64f Version=9649 N: Name="HD User Facing: HD User Facing" P: Phys=usb-:00:14.0-9/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0/input/input12 U: Uniq= H:
[Kernel-packages] [Bug 1951668] [NEW] touchpad not working
Public bug reported: niklaus@niklaus-Nitro-AN517-54:~$ 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/PNP0A08:00/device:1c/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 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/input2 U: Uniq= H: Handlers=kbd event2 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/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse" P: Phys=usb-:00:14.0-5/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.0/0003:2717:003B.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B: KEY=e080ffdf01cf fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse" P: Phys=usb-:00:14.0-5/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.1/0003:2717:003B.0002/input/input6 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse Consumer Control" P: Phys=usb-:00:14.0-5/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.1/0003:2717:003B.0002/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=13 B: KEY=838c000 c 0 B: MSC=10 I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse Consumer Control" P: Phys=usb-:00:14.0-5/input2 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.2/0003:2717:003B.0003/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=1f B: KEY=302ff 0 0 48317aff32d bfd6 1 130ff38b17c000 677bfad941dfed 9ed6804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=2717 Product=003b Version=0111 N: Name="MI Dongle MI Wireless Mouse Keyboard" P: Phys=usb-:00:14.0-5/input2 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.2/0003:2717:003B.0003/input/input9 U: Uniq= H: Handlers=sysrq kbd event9 B: PROP=0 B: EV=100013 B: KEY=e080ffdf01cf fffe B: MSC=10 I: Bus=0019 Vendor=1025 Product=1229 Version= N: Name="Acer Wireless Radio Control" P: Phys=acer-wireless/input0 S: Sysfs=/devices/LNXSYSTM:00/10251229:00/input/input10 U: Uniq= H: Handlers=rfkill kbd event10 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Acer WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input11 U: Uniq= H: Handlers=rfkill kbd event11 B: PROP=0 B: EV=13 B: KEY=1c 0 0 0 0 160080c00 30 10 0 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b64f Version=9649 N: Name="HD User Facing: HD User Facing" P: Phys=usb-:00:14.0-9/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0/input/input12 U: Uniq= H: Handlers=kbd event12 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input16 U: Uniq= H: Handlers=event16 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S:
[Kernel-packages] [Bug 1951666] [NEW] /usr/share/libdrm/amdgpu.ids: No such file or directory
Public bug reported: I use the snap version of Smplayer on Ubuntu 21.10 (because the apt-installed mpv missed some libs). It seems to work correctly but I got an cli error message: "/usr/share/libdrm/amdgpu.ids: No such file or directory" Does it mean there is no hardware acceleration? Could you fix it? Additional question: In general I use only verified snaps. Could you verify the publisher of the mentioned Smplayer snap? She/He seems to be OK. Thanks, Richard ** Affects: snap (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => snap (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951666 Title: /usr/share/libdrm/amdgpu.ids: No such file or directory Status in snap package in Ubuntu: New Bug description: I use the snap version of Smplayer on Ubuntu 21.10 (because the apt-installed mpv missed some libs). It seems to work correctly but I got an cli error message: "/usr/share/libdrm/amdgpu.ids: No such file or directory" Does it mean there is no hardware acceleration? Could you fix it? Additional question: In general I use only verified snaps. Could you verify the publisher of the mentioned Smplayer snap? She/He seems to be OK. Thanks, Richard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1951666/+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 1899690] Re: HWE Kernel causes incompatable behavior with Kubernetes
I reproduced it in bionic with hwe kernel, and a privileged docker container with iptables 1.8.3, with host networking. Didn't try other versions yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1899690 Title: HWE Kernel causes incompatable behavior with Kubernetes Status in linux-meta-hwe-5.4 package in Ubuntu: New Bug description: This is a follow up from a bug that I filed for Kubernetes: https://github.com/kubernetes/kubernetes/issues/95409 **What happened**: I'm running Kubernetes on my Ubuntu 18.04 systems. Kubernetes is installed via Rancher (RKE). My Kubernetes 1.17 cluster (and Kubernetes 1.16 cluster) has 40-50 firewall rules that say `[unsupported revision]`. I am concerned this will cause problems with ``` # iptables-save ... -A KUBE-SEP-AAAREDACTED1 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED1 -p tcp -m tcp -j DNAT [unsupported revision] -A KUBE-SEP-AAAREDACTED2 -s 10.99.99.40/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED2 -p tcp -m tcp -j DNAT [unsupported revision] -A KUBE-SEP-AAAREDACTED3 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED3 -p tcp -m tcp -j DNAT [unsupported revision] ``` **What you expected to happen**: I expect these firewall rules to be valid, like so: ``` # iptables-save ... -A KUBE-SEP-AAAREDACTED1 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED1 -p tcp -m tcp -j DNAT --to-destination 10.99.99.27:9153 -A KUBE-SEP-AAAREDACTED2 -s 10.99.99.40/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED2 -p tcp -m tcp -j DNAT --to-destination 10.99.99.40:3306 -A KUBE-SEP-AAAREDACTED3 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED3 -p tcp -m tcp -j DNAT --to-destination 10.99.99.27:53 ``` **How to reproduce it (as minimally and precisely as possible)**: 1. Allocate a worker node 1. Install Ubuntu 18.04.5 2. Install Kubernetes with Canal * I'm using Rancher & RKE, and I assume this happens with vanilla versions of Kubernetes as well. 3. Install the Ubuntu LTS Hardware Enablement (HWE) kernel via https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Server 4. Reboot 5. When the system comes back online & Docker is running, look for invalid iptables rules as shown above. ** Environment ** - 18.04.5 LTS (Bionic Beaver) - Kernel - Linux cntest13 5.4.0-48-generic #52~18.04.1-Ubuntu SMP Thu Sep 10 12:50:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux\ - Kubernetes 1.17.11 - Installed via RKE - Canal version: rancher/calico-node:v3.13.4 (Not sure how to tell the other version numbers) - Docker version: 18.9.9 Happens with both Bare Metal and VM systems: - Bare metal nodes - AMD EPYC 7452 32-Core Processor, large memory, multiple NICs to different networks - VMs on VMware vSphere Default iptables version: ``` # iptables --version iptables v1.6.1 # ls -ld `which iptables` lrwxrwxrwx 1 root root 13 Nov 12 2017 /sbin/iptables -> xtables-multi # ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04 5.4.0.48.52~18.04.42 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 Date: Tue Oct 13 19:19:20 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1899690/+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 1945565] Re: [SRU] Revert amdgpu/renoir firmware
For 5.14 and 5.15 it will come in as part of stable update process. It is picked up in 5.15.3 for 5.15.y: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y=bb7e50b476abb8fc94a9891bb7f08ab21801fec5 It's picked up in 5.14.19 for 5.14.y: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.14.y=af09862cb5661cfdedd114ae50c7aaed94bd185a As there is no 5.13.y, Canonical will need to manually pull this in for 5.13 OEM kernel. Please restore the new firmware once it's pulled in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945565 Title: [SRU] Revert amdgpu/renoir firmware Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Revert below change, this issue is gone. commit a543b9c1bfd12e60d962acd48108234481a8581f Author: Alex Deucher Date: Thu Jul 1 12:23:11 2021 +0800 amdgpu: update renoir firmware from 21.20 BugLink: https://bugs.launchpad.net/bugs/1934014 From internal git commit: 8b05e03570818d047d7ea0a7388c89c4192fd20b Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0) [khfeng: Squashed multiple updates into one commit] Signed-off-by: Kai-Heng Feng Signed-off-by: Timo Aaltonen [Test] Verify S3 on renoir's platforms. [Where problems could occur] Renoir based systems can't resume from s2idle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+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 1899690] Re: HWE Kernel causes incompatable behavior with Kubernetes
I know it's been a long time, but can you still get to the version of iptables that's running inside the k8s pod that is inserting these rules? I assume it was kube-router? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1899690 Title: HWE Kernel causes incompatable behavior with Kubernetes Status in linux-meta-hwe-5.4 package in Ubuntu: New Bug description: This is a follow up from a bug that I filed for Kubernetes: https://github.com/kubernetes/kubernetes/issues/95409 **What happened**: I'm running Kubernetes on my Ubuntu 18.04 systems. Kubernetes is installed via Rancher (RKE). My Kubernetes 1.17 cluster (and Kubernetes 1.16 cluster) has 40-50 firewall rules that say `[unsupported revision]`. I am concerned this will cause problems with ``` # iptables-save ... -A KUBE-SEP-AAAREDACTED1 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED1 -p tcp -m tcp -j DNAT [unsupported revision] -A KUBE-SEP-AAAREDACTED2 -s 10.99.99.40/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED2 -p tcp -m tcp -j DNAT [unsupported revision] -A KUBE-SEP-AAAREDACTED3 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED3 -p tcp -m tcp -j DNAT [unsupported revision] ``` **What you expected to happen**: I expect these firewall rules to be valid, like so: ``` # iptables-save ... -A KUBE-SEP-AAAREDACTED1 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED1 -p tcp -m tcp -j DNAT --to-destination 10.99.99.27:9153 -A KUBE-SEP-AAAREDACTED2 -s 10.99.99.40/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED2 -p tcp -m tcp -j DNAT --to-destination 10.99.99.40:3306 -A KUBE-SEP-AAAREDACTED3 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED3 -p tcp -m tcp -j DNAT --to-destination 10.99.99.27:53 ``` **How to reproduce it (as minimally and precisely as possible)**: 1. Allocate a worker node 1. Install Ubuntu 18.04.5 2. Install Kubernetes with Canal * I'm using Rancher & RKE, and I assume this happens with vanilla versions of Kubernetes as well. 3. Install the Ubuntu LTS Hardware Enablement (HWE) kernel via https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Server 4. Reboot 5. When the system comes back online & Docker is running, look for invalid iptables rules as shown above. ** Environment ** - 18.04.5 LTS (Bionic Beaver) - Kernel - Linux cntest13 5.4.0-48-generic #52~18.04.1-Ubuntu SMP Thu Sep 10 12:50:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux\ - Kubernetes 1.17.11 - Installed via RKE - Canal version: rancher/calico-node:v3.13.4 (Not sure how to tell the other version numbers) - Docker version: 18.9.9 Happens with both Bare Metal and VM systems: - Bare metal nodes - AMD EPYC 7452 32-Core Processor, large memory, multiple NICs to different networks - VMs on VMware vSphere Default iptables version: ``` # iptables --version iptables v1.6.1 # ls -ld `which iptables` lrwxrwxrwx 1 root root 13 Nov 12 2017 /sbin/iptables -> xtables-multi # ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04 5.4.0.48.52~18.04.42 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 Date: Tue Oct 13 19:19:20 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1899690/+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 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
FYI I did experience such hard reboots (very annoying, for sure!) with lwfinger dkms driver, but never (never) since some time and especially since Ubuntu did include rtw89 in 5.15 kernel. Maybe I'm lucky, or that's solved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Confirmed Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967/+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 1951643] Re: Hirsute update: upstream stable patchset 2021-11-19
** Description changed: + SRU Justification - 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: - 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-11-19 -upstream stable patchset 2021-11-19 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v5.10.73, v5.14.12 + + from git://git.kernel.org/ + + Partially revert "usb: Kconfig: using select for USB_COMMON dependency" + usb: chipidea: ci_hdrc_imx: Also search for 'phys' phandle + USB: cdc-acm: fix racy tty buffer accesses + USB: cdc-acm: fix break reporting + usb: typec: tcpm: handle SRC_STARTUP state if cc changes + drm/nouveau/kms/tu102-: delay enabling cursor until after assign_windows + xen/privcmd: fix error handling in mmap-resource processing + mmc: meson-gx: do not use memcpy_to/fromio for dram-access-quirk + mmc: sdhci-of-at91: wait for calibration done before proceed + mmc: sdhci-of-at91: replace while loop with read_poll_timeout + ovl: fix missing negative dentry check in ovl_rename() + ovl: fix IOCB_DIRECT if underlying fs doesn't support direct IO + nfsd: fix error handling of register_pernet_subsys() in init_nfsd() + nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero + SUNRPC: fix sign error causing rpcsec_gss drops + xen/balloon: fix cancelled balloon action + ARM: dts: omap3430-sdp: Fix NAND device node + ARM: dts: imx6dl-yapp4: Fix lp5562 LED driver probe + ARM: dts: qcom: apq8064: use compatible which contains chipid + riscv: Flush current cpu icache before other cpus + bus: ti-sysc: Add break in switch statement in sysc_init_soc() + soc: qcom: socinfo: Fixed argument passed to platform_set_data() + ARM: dts: qcom: apq8064: Use 27MHz PXO clock as DSI PLL reference + ARM: at91: pm: do not panic if ram controllers are not enabled + soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment + ARM: dts: imx: Add missing pinctrl-names for panel on M53Menlo + ARM: dts: imx: Fix USB host power regulator polarity on M53Menlo + ARM: dts: imx6qdl-pico: Fix Ethernet support + PCI: hv: Fix sleep while in non-sleep context when removing child devices from the bus + ath5k: fix building with LEDS=m + arm64: dts: qcom: pm8150: use qcom,pm8998-pon binding + xtensa: use CONFIG_USE_OF instead of CONFIG_OF + xtensa: call irqchip_init only when CONFIG_USE_OF is selected + iwlwifi: pcie: add configuration of a Wi-Fi adapter on Dell XPS 15 + bpf, arm: Fix register clobbering in div/mod implementation + soc: ti: omap-prm: Fix external abort for am335x pruss + bpf: Fix integer overflow in prealloc_elems_and_freelist() + net/mlx5e: IPSEC RX, enable checksum complete + net/mlx5: E-Switch, Fix double allocation of acl flow counter + phy: mdio: fix memory leak + net_sched: fix NULL deref in fifo_set_limit() + powerpc/fsl/dts: Fix phy-connection-type for fm1mac3 + ptp_pch: Load module automatically if ID matches + dt-bindings: drm/bridge: ti-sn65dsi86: Fix reg value + ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence + net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size() + net: bridge: fix under estimation in br_get_linkxstats_size() + net/sched: sch_taprio: properly cancel timer from taprio_destroy() + net: sfp: Fix typo in state machine debug string + netlink: annotate data races around nlk->bound + bus: ti-sysc: Use CLKDM_NOAUTO for dra7 dcan1 for errata i893 + drm/sun4i: dw-hdmi: Fix HDMI PHY clock setup + video: fbdev: gbefb: Only instantiate device when built for IP32 + drm/nouveau: avoid a use-after-free when BO init fails + drm/nouveau/kms/nv50-: fix file release memory leak + drm/nouveau/debugfs: fix file release memory leak + gve: Correct available tx qpl check + gve: Avoid freeing NULL pointer + rtnetlink: fix if_nlmsg_stats_size() under estimation + gve: fix gve_get_stats() + gve: report 64bit tx_bytes counter from gve_handle_report_stats() + i40e: fix endless loop under rtnl + i40e: Fix freeing of uninitialized misc IRQ vector + net: prefer socket bound to interface when not in VRF + powerpc/iommu: Report the correct most efficient DMA mask for PCI devices + i2c: acpi: fix
[Kernel-packages] [Bug 1951643] [NEW] Hirsute update: upstream stable patchset 2021-11-19
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-11-19 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Hirsute) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1951643 Title: Hirsute update: upstream stable patchset 2021-11-19 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: In Progress Bug description: 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-11-19 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951643/+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 1919282] Re: 'HP ImagePad' doesn't work at all in "HP Pavilion 15-p077TX Notebook" after ubuntu 20.04 installation
*** This bug is a duplicate of bug 1931787 *** https://bugs.launchpad.net/bugs/1931787 I have the exact same issue on HP 15dy3008ca with linux kernel 5.10. Did you get past this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1919282 Title: 'HP ImagePad' doesn't work at all in "HP Pavilion 15-p077TX Notebook" after ubuntu 20.04 installation Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: Installed ubuntu 20.04 2 days ago. Touchpad is not working and is not present in devices list. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 16 12:25:03 2021 InstallationDate: Installed on 2021-03-14 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1919282/+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 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
Specifically, https://github.com/lwfinger/rtw89/commit/14be64e6e0f6541efee8a39f3f115b5e0343 mention system crash :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Confirmed Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967/+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 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
For what it is worth, at some point, using https://github.com/lwfinger/rtw89 branch's v7 was making my laptop crashing, only symptom was me going away and coming back the laptop is rebooted. It was happening after ~24-48h of uptime, regularly enough for it to be painful. I think my latest build was with https://github.com/lwfinger/rtw89/commit/a3f3f39908872fe9edc887d857836d9cb4cb598c and this was much rather stable. @kaihengfeng Can we hope you cherry pick all the new fixes coming on v7 branch? Without stability, I'll have to blacklist the kernel-bundled driver and go back to the dkms one self-built :/ Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Confirmed Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967/+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 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
I'm still seeing this problem happening on a Razer Blade 15 Advanced (mid-2021). The issue only happens after a resume from suspend (both on laptop lid close and on suspend from the command line using `sudo pm-suspend` Upon wake, the mouse is jerky, clicking on things, and becomes increasingly unresponsive. The terminal (dmesg) is constantly writing: ``` i2c_hid i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/65535) ``` None of the workarounds I have seen seem to be able to restore the trackpad to working order. Such as.. ``` sudo rmmod i2c_hid hid_multitouch && sudo modprobe i2c_hid hid_multitouch ``` and ``` xinput --disable 19 && xinput --enable 19 ``` Only a hard shutdown and a restart seem to fix things. -- 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/1798363 Title: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Lots of these things ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blurhy 2908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 17 20:07:13 2018 InstallationDate: Installed on 2018-10-10 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798363/+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 1951634] 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 1951634 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/1951634 Title: package iotop missing Status in linux package in Ubuntu: Incomplete Bug description: Hello sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" iotop Command 'iotop' not found, but can be installed with: sudo apt install iotop sudo apt install iotop Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package iotop Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951634/+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 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
** Changed in: linux-raspi2 (Ubuntu) Assignee: Ryan Finnie (fo0bar) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: This issue was reported in this mailing list thread first https://lists.ubuntu.com/archives/snapcraft/2016-December/002138.html Hardware: RPi3 Image: http://www.finnie.org/software/raspberrypi/ubuntu-rpi3/ubuntu-16.04-preinstalled-server-armhf+raspi3.img.xz [Steps to Reproduce] 1. Install the image in an SD card. Use it to boot into the system. 2. Issue the command "sudo apt-get update; sudo apt-get install linux-image-4.4.0-1038-raspi2 linux-headers-4.4.0-1038-raspi2 linux-raspi2-headers-4.4.0-1038 -y" 3. Reboot [Expected Result] Boot into the system with kernel 4.4.0-1038-raspi2 [Actual Result] The system stop at the booting session with the message 'Starting kernel...' and never goes to the login session. [Additional Info] 4.4.0-1029-raspi2 and 4.4.0-1034-raspi2 were used as the forementioned apt installation steps. They work well. They could go to the login session and ready for use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+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 1951634] [NEW] package iotop missing
Public bug reported: Hello sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" iotop Command 'iotop' not found, but can be installed with: sudo apt install iotop sudo apt install iotop Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package iotop Thanks ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951634 Title: package iotop missing Status in linux package in Ubuntu: New Bug description: Hello sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" iotop Command 'iotop' not found, but can be installed with: sudo apt install iotop sudo apt install iotop Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package iotop Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951634/+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 1950968] Re: v5.15 RT kernel fails to boot on some arm64 instances
** Changed in: linux (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: d2021.10.26/jammy/linux-realtime/5.15.0-1002.2 failed to boot on helo- kernel.arm64 without any logs. - Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-1002-realtime Found initrd image: /boot/initrd.img-5.15.0-1002-realtime Found linux image: /boot/vmlinuz-5.13.0-21-generic Found initrd image: /boot/initrd.img-5.13.0-21-generic done . Rebooting for installed Kernel meta package Traceback (most recent call last): File "/home/maas/ckct/sut-prep", line 187, in exit(app.main(args)) File "/home/maas/ckct/sut-prep", line 74, in main if instance.provision(): File "/home/maas/ckct/lib/target.py", line 1301, in provision s.reboot(progress=reboot) File "/home/maas/ckct/lib/target.py", line 621, in reboot s.wait_for_target() File "/home/maas/ckct/lib/target.py", line 173, in wait_for_target raise WaitForTarget(message) lib.target.WaitForTarget: The specified timeout (30 minutes) was reached while waiting for the target system (10.229.83.183) to come back up. WARNING - [2021-11-15 10:42:43.270713] ssh command (return): uname -vr (0) 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 09:01:50 UTC 2021 - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+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 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"
Hello, I've tested the focal-proposed versions of nvidia-driver-450-server- generic and nvidia-470-server-generic, and the changes look good. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it
Confirming this problem. The work-around does not work for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-465 in Ubuntu. https://bugs.launchpad.net/bugs/1933880 Title: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a restart, run `sudo apt autoremove nvidia-driver-465`. 2. Leaving the terminal open, suspend the machine. Expected behavior: the machine suspend successfully and can be woken up successfully. Actual behavior: the machine doesn't suspend. It either: - hang with no respond other than SysRq+REISUB (or maybe network, but I didn't test), or - return you back to the login screen. Upon logging in, you'll notice that the terminal you opened is gone. Upon further inspection (on a session that doesn't hang), it's been found that X server died with: Fatal server error: [66.422] (EE) systemd-logind disappeared (stopped/restarted?) And checking journal for systemd-logind log, it said: Error during inhibitor-delayed operation (already returned success to client): Unit nvidia-suspend.service is masked. before the new process takes it place. The system is Ubuntu 20.04, X.org session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 03:34:00 2021 InstallationDate: Installed on 2021-03-15 (105 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=th_TH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+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 1951616] [NEW] VC4 PixelValve and HDMI Drivers Locking Improvements for 5.13
Public bug reported: [From] https://github.com/raspberrypi/linux/pull/4674 [Description] Hi, Here's a backport for 5.13 of the series found here: https://lore.kernel.org/dri-devel/20211025141113.702757-1-max...@cerno.tech/ This series is a follow-up of a previous discussion with upstream that pointed out we had a number of illegal accesses to KMS structures in our pixelvalves and hdmi drivers, or access done without proper care. This series was just merged in drm-misc, is part of rpi-5.15.y already and I plan on sending a PR for 5.10 as well. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1951616 Title: VC4 PixelValve and HDMI Drivers Locking Improvements for 5.13 Status in linux-raspi package in Ubuntu: New Bug description: [From] https://github.com/raspberrypi/linux/pull/4674 [Description] Hi, Here's a backport for 5.13 of the series found here: https://lore.kernel.org/dri-devel/20211025141113.702757-1-max...@cerno.tech/ This series is a follow-up of a previous discussion with upstream that pointed out we had a number of illegal accesses to KMS structures in our pixelvalves and hdmi drivers, or access done without proper care. This series was just merged in drm-misc, is part of rpi-5.15.y already and I plan on sending a PR for 5.10 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1951616/+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 1951583] Re: bbswitch dkms build failure with 5.15 on armhf and ppc64el
** Also affects: bbswitch (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Jammy)
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1951583
Title:
bbswitch dkms build failure with 5.15 on armhf and ppc64el
Status in bbswitch package in Ubuntu:
New
Status in bbswitch source package in Jammy:
New
Bug description:
It looks like bbswitch is using acpi_bus_get_device() on any
architectures, but this function is not available on armhf or ppc64el:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit
declaration of function ‘acpi_bus_get_device’; did you mean
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
| ^~
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
| ^~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1951583/+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 1951608] [NEW] build error with linux 5.15 on jammy
Public bug reported: CC [M] /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1295:27: error: initialization of ‘void (*)(struct device *)’ from incompatible pointer type ‘int (*)(struct device *)’ [-Werror=incompatible-pointer-types] 1295 | .remove = ddcci_device_remove | ^~~ ** Affects: ddcci-driver-linux (Ubuntu) Importance: Undecided Status: New ** Affects: ddcci-driver-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ddcci-driver-linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951608 Title: build error with linux 5.15 on jammy Status in ddcci-driver-linux package in Ubuntu: New Status in ddcci-driver-linux source package in Jammy: New Bug description: CC [M] /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1295:27: error: initialization of ‘void (*)(struct device *)’ from incompatible pointer type ‘int (*)(struct device *)’ [-Werror=incompatible-pointer-types] 1295 | .remove = ddcci_device_remove | ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1951608/+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 1951606] 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 1951606
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/1951606
Title:
bonding: arp monitoring is failing with tuntap interfaces
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
When tuntap interfaces are slaves of a bonding interface, arp
monitoring is unusable.
This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
active backup with arp monitoring"). It will be included in linux
v5.16.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31d27fbed5d
[Test Case]
Create a bonding with two tuntap interfaces and arp monitoring
configured. Before the patch, slave interfaces are flapping
continuously.
Example:
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:28 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:31 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:31 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:32 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:35 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:35 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:36 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:37 dut-vm kernel: bond0: (slave ntfp3): link status definitely up
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp3): making interface the new
active one
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951606/+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 1951606] [NEW] bonding: arp monitoring is failing with tuntap interfaces
Public bug reported:
[Impact]
When tuntap interfaces are slaves of a bonding interface, arp monitoring
is unusable.
This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
active backup with arp monitoring"). It will be included in linux v5.16.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31d27fbed5d
[Test Case]
Create a bonding with two tuntap interfaces and arp monitoring
configured. Before the patch, slave interfaces are flapping
continuously.
Example:
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:28 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:31 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:31 dut-vm kernel: bond0: now running without any active interface!
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:32 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:35 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:35 dut-vm kernel: bond0: now running without any active interface!
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:36 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:37 dut-vm kernel: bond0: (slave ntfp3): link status definitely up
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp3): making interface the new
active one
[Regression Potential]
The patch is trivial, the potential regressions are low.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
When tuntap interfaces are slaves of a bonding interface, arp monitoring
- is fails
+ is unusable.
This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
active backup with arp monitoring"). It will be included in linux v5.16.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31d27fbed5d
[Test Case]
Create a bonding with two tuntap interfaces and arp monitoring
configured. Before the patch, slave interfaces are flapping
continuously.
Example:
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:28 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:31 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:31 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:32 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:35 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:35 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:36 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:37 dut-vm kernel: bond0: (slave ntfp3): link status definitely up
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp3): making interface the new
active one
[Regression Potential]
The patch is trivial, the potential regressions are low.
** Summary changed:
- bondig: arp monitoring is failing with tuntap interfaces
+ bonding: arp monitoring is failing with tuntap interfaces
--
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/1951606
Title:
bonding: arp monitoring is failing with tuntap interfaces
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
When tuntap interfaces are slaves of a bonding interface, arp
monitoring is unusable.
This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
active backup with arp monitoring"). It will be included in linux
v5.16.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31d27fbed5d
[Test Case]
Create a bonding with two tuntap interfaces and arp monitoring
configured. Before the patch, slave interfaces are flapping
continuously.
Example:
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status
[Kernel-packages] [Bug 1948960] Autopkgtest regression report (nvidia-graphics-drivers-450-server/450.156.00-0ubuntu0.21.10.2)
All autopkgtests for the newly accepted nvidia-graphics-drivers-450-server (450.156.00-0ubuntu0.21.10.2) for impish have finished running. The following regressions have been reported in tests triggered by the package: pyopencl/2021.1.2-1build2 (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/impish/update_excuses.html#nvidia-graphics-drivers-450-server [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 nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1951583] Re: bbswitch dkms build failure with 5.15 on armhf and ppc64el
Attached debdiff can fix the build error on armhf and ppc64el.
** Patch added: "bbswitch-fix-build-error-on-armhf-and-ppc64el.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951583/+attachment/5542102/+files/bbswitch-fix-build-error-on-armhf-and-ppc64el.debdiff
--
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/1951583
Title:
bbswitch dkms build failure with 5.15 on armhf and ppc64el
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Jammy:
Incomplete
Bug description:
It looks like bbswitch is using acpi_bus_get_device() on any
architectures, but this function is not available on armhf or ppc64el:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit
declaration of function ‘acpi_bus_get_device’; did you mean
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
| ^~
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
| ^~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951583/+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 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
For further needs-testing ;-) , latest proposed Jammy's 5.15 kernel solved this issue too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Confirmed Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967/+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 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
Ubuntu 21.10 with kernel 5.15.3-051503-generic is affected too. ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Confirmed Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967/+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 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others
@Elia, I have the same hardware and a full power-cycle (complete shutdown, then start) was enough for WIFI to show-up again in BIOS and OS. Would try that first before touching the battery ;) Revert to 5.13.0-20 was enogh for me as well. -- 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/1950515 Title: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others Status in linux package in Ubuntu: Confirmed Bug description: In the 5.13.0-21 kernel, the device fails: $ lshw -c network *-network description: Network controller product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] vendor: Qualcomm physical id: 0 bus info: pci@:72:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:182 memory:a250-a25f $ lspci | grep Qualcomm 72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) $ sudo modprobe ath11k_pci $ sudo dmesg | grep ath [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002) [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0 [ 10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110 [ 10.337692] ath11k_pci :72:00.0: failed to send qmi firmware indication: -110 [ 39.931711] ath11k_pci :72:00.0: link down error during global reset [ 45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 45.575668] ath11k_pci :72:00.0: qca6390 hw2.0 [ 45.630047] ath11k_pci :72:00.0: failed to set pcie link register 0x01e0c0ac: 0x != 0x0010 [ 45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110 [ 45.650253] ath11k_pci :72:00.0: link down error during global reset $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no In the 5.13.0-20 kernel, the device works: $ sudo dmesg | grep ath [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002) [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0 [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0x [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0 [ 351.080712] ath11k_pci :72:00.0: link down error during global reset [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:23:07 2021 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 InstallationDate: Installed on 2021-05-04 (190 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 09/30/2021 dmi.bios.release: 3.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.0 dmi.board.name: 0MRT12 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950515/+subscriptions --
[Kernel-packages] [Bug 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-418-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-418-server/418.226.00-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-460-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-460-server/460.106.00-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-460-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-460-server/460.106.00-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-418-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-418-server/418.226.00-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-470-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470-server/470.82.01-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-418-server into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-418-server/418.226.00-0ubuntu0.21.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.156.00-0ubuntu0.21.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.156.00-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.156.00-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-470-server into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470-server/470.82.01-0ubuntu0.21.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.156.00-0ubuntu0.21.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: nvidia-graphics-drivers-418-server (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Impish) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-418-server into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-418-server/418.226.00-0ubuntu0.21.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-470-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470-server/470.82.01-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-470-server into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470-server/470.82.01-0ubuntu0.21.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-460-server into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-460-server/460.106.00-0ubuntu0.21.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1948960] Please test proposed package
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-460-server into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-460-server/460.106.00-0ubuntu0.21.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948960 Title: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests" Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: [Impact] This release demotes nvidia-settings and nvidia-prime from "Recommends" to "Suggests" dependencies for the -server NVIDIA drivers, for the following reasons: - The Ubuntu default behavior is to install "recommended" packages. - The -server packages are associated with TRDs, which are generally used on Tesla GPUs, which are generally used on servers. - nvidia-settings pulls in many GUI bits which are generally not relevant to servers. [Test Case] Installing the main metapackage should be possible without pulling in the two above mentioned dependencies. [Regression Potential] Low, as no change other than dropping the two dependencies is involved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1951583] 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 1951583
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/1951583
Title:
bbswitch dkms build failure with 5.15 on armhf and ppc64el
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Jammy:
Incomplete
Bug description:
It looks like bbswitch is using acpi_bus_get_device() on any
architectures, but this function is not available on armhf or ppc64el:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit
declaration of function ‘acpi_bus_get_device’; did you mean
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
| ^~
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
| ^~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951583/+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 1951580] Re: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951580 Title: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o In file included from /tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3, from ./arch/x86/include/asm/bug.h:84, from ./include/linux/bug.h:5, from /tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3, from /tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4, from ./include/linux/skbuff.h:13, from /tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3, from ./include/linux/if_ether.h:19, from /tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3, from ./include/linux/etherdevice.h:20, from /tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3, from /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In function ‘iwl_mei_free_shared_mem’: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17: error: implicit declaration of function ‘mei_cldev_dma_unmap’ [-Werror=implicit-function-declaration] 243 | WARN_ON(mei_cldev_dma_unmap(cldev)); | ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951580/+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 1951583] [NEW] bbswitch dkms build failure with 5.15 on armhf and ppc64el
Public bug reported:
It looks like bbswitch is using acpi_bus_get_device() on any
architectures, but this function is not available on armhf or ppc64el:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit declaration
of function ‘acpi_bus_get_device’; did you mean ‘acpi_get_gpe_device’?
[-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
| ^~
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
| ^~
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1951583
Title:
bbswitch dkms build failure with 5.15 on armhf and ppc64el
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
New
Bug description:
It looks like bbswitch is using acpi_bus_get_device() on any
architectures, but this function is not available on armhf or ppc64el:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit
declaration of function ‘acpi_bus_get_device’; did you mean
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
| ^~
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
| ^~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951583/+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 1951580] Re: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy
Actually... is this dkms really needed in jammy? Now that the build is fixed I just noticed that I get this error if I try to install it on a 5.15 kernel: iwlwifi.ko: Running module version sanity check. Module has been obsoleted due to being included in kernel 5.14.0. We will avoid installing for future kernels above 5.14.0. You may override by specifying --force. -- 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/1951580 Title: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o In file included from /tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3, from ./arch/x86/include/asm/bug.h:84, from ./include/linux/bug.h:5, from /tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3, from /tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4, from ./include/linux/skbuff.h:13, from /tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3, from ./include/linux/if_ether.h:19, from /tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3, from ./include/linux/etherdevice.h:20, from /tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3, from /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In function ‘iwl_mei_free_shared_mem’: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17: error: implicit declaration of function ‘mei_cldev_dma_unmap’ [-Werror=implicit-function-declaration] 243 | WARN_ON(mei_cldev_dma_unmap(cldev)); | ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951580/+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 1951580] Re: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy
Debdiff in attach seems to resolve the problem (tested on jammy with the latest 5.15 from -proposed). ** Patch added: "iwlwifi-fix-build-error-with-kernel-5.15.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951580/+attachment/5542079/+files/iwlwifi-fix-build-error-with-kernel-5.15.debdiff -- 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/1951580 Title: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o In file included from /tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3, from ./arch/x86/include/asm/bug.h:84, from ./include/linux/bug.h:5, from /tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3, from /tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4, from ./include/linux/skbuff.h:13, from /tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3, from ./include/linux/if_ether.h:19, from /tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3, from ./include/linux/etherdevice.h:20, from /tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3, from /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In function ‘iwl_mei_free_shared_mem’: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17: error: implicit declaration of function ‘mei_cldev_dma_unmap’ [-Werror=implicit-function-declaration] 243 | WARN_ON(mei_cldev_dma_unmap(cldev)); | ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951580/+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 1951580] Re: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy
https://gitlab.com/vicamo/backport-iwlwifi-dkms/-/issues/12 <- also filed an issue 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/1951580 Title: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o In file included from /tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3, from ./arch/x86/include/asm/bug.h:84, from ./include/linux/bug.h:5, from /tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3, from /tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4, from ./include/linux/skbuff.h:13, from /tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3, from ./include/linux/if_ether.h:19, from /tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3, from ./include/linux/etherdevice.h:20, from /tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3, from /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In function ‘iwl_mei_free_shared_mem’: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17: error: implicit declaration of function ‘mei_cldev_dma_unmap’ [-Werror=implicit-function-declaration] 243 | WARN_ON(mei_cldev_dma_unmap(cldev)); | ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951580/+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 1951580] 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 1951580 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 ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951580 Title: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o In file included from /tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3, from ./arch/x86/include/asm/bug.h:84, from ./include/linux/bug.h:5, from /tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3, from /tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4, from ./include/linux/skbuff.h:13, from /tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3, from ./include/linux/if_ether.h:19, from /tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3, from ./include/linux/etherdevice.h:20, from /tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3, from /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In function ‘iwl_mei_free_shared_mem’: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17: error: implicit declaration of function ‘mei_cldev_dma_unmap’ [-Werror=implicit-function-declaration] 243 | WARN_ON(mei_cldev_dma_unmap(cldev)); | ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951580/+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 1951580] [NEW] backport-iwlwifi-dkms fails to build with kernel 5.15 jammy
Public bug reported: CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o In file included from /tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3, from ./arch/x86/include/asm/bug.h:84, from ./include/linux/bug.h:5, from /tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3, from /tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4, from ./include/linux/skbuff.h:13, from /tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3, from ./include/linux/if_ether.h:19, from /tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3, from ./include/linux/etherdevice.h:20, from /tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3, from /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In function ‘iwl_mei_free_shared_mem’: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17: error: implicit declaration of function ‘mei_cldev_dma_unmap’ [-Werror=implicit-function-declaration] 243 | WARN_ON(mei_cldev_dma_unmap(cldev)); | ^~~ ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Tags: jammy ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Bug watch added: gitlab.com/vicamo/backport-iwlwifi-dkms/-/issues #12 https://gitlab.com/vicamo/backport-iwlwifi-dkms/-/issues/12 -- 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/1951580 Title: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o In file included from /tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3, from ./arch/x86/include/asm/bug.h:84, from ./include/linux/bug.h:5, from /tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3, from /tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4, from ./include/linux/skbuff.h:13, from /tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3, from ./include/linux/if_ether.h:19, from /tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3, from ./include/linux/etherdevice.h:20, from /tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3, from /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In function ‘iwl_mei_free_shared_mem’: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17: error: implicit declaration of function ‘mei_cldev_dma_unmap’ [-Werror=implicit-function-declaration] 243 | WARN_ON(mei_cldev_dma_unmap(cldev)); | ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951580/+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 1951563] Re: alsa/sdw: add sdw audio machine driver for several ADL machines
** Description changed: - This bug is for tracking purpose. + [Impact] + In the Dell oem project, we need to enable the sdw audio on several + ADL machines, without these patches, the audio can't work at all. + + [Fix] + Backport some patches from upstream, this adds the audio machine + drivers for those adl platforms. + + [Test] + Booting the patched kernel, open the gnome-sound-setting, we could + see the speaker and microphone, plug headset, the headphone and + headset-mic all work well. + + [Where problems could occur] + This add some machine drivers for sdw audio, if it could introduce + regression, it will be on the Dell previous generation machines which + has sdw audio, it could make the audio on those machines not work. But + this possibility is very low, we already tested the patches on those + machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951563 Title: alsa/sdw: add sdw audio machine driver for several ADL machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] In the Dell oem project, we need to enable the sdw audio on several ADL machines, without these patches, the audio can't work at all. [Fix] Backport some patches from upstream, this adds the audio machine drivers for those adl platforms. [Test] Booting the patched kernel, open the gnome-sound-setting, we could see the speaker and microphone, plug headset, the headphone and headset-mic all work well. [Where problems could occur] This add some machine drivers for sdw audio, if it could introduce regression, it will be on the Dell previous generation machines which has sdw audio, it could make the audio on those machines not work. But this possibility is very low, we already tested the patches on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951563/+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 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others
Hi, I have the same issue, Wifi disabled when updating to 5.13.0-21 kernel, I regress to my last version 5.11.0-34 (I will try with 5.13.0-20). To solve the issue I need to detach the battery from the motherboard. Hardware name: Dell Inc. XPS 15 9500 BIOS 1.9.1 08/11/2021 5.13.0-21-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/1950515 Title: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others Status in linux package in Ubuntu: Confirmed Bug description: In the 5.13.0-21 kernel, the device fails: $ lshw -c network *-network description: Network controller product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] vendor: Qualcomm physical id: 0 bus info: pci@:72:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:182 memory:a250-a25f $ lspci | grep Qualcomm 72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) $ sudo modprobe ath11k_pci $ sudo dmesg | grep ath [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002) [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0 [ 10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110 [ 10.337692] ath11k_pci :72:00.0: failed to send qmi firmware indication: -110 [ 39.931711] ath11k_pci :72:00.0: link down error during global reset [ 45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 45.575668] ath11k_pci :72:00.0: qca6390 hw2.0 [ 45.630047] ath11k_pci :72:00.0: failed to set pcie link register 0x01e0c0ac: 0x != 0x0010 [ 45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110 [ 45.650253] ath11k_pci :72:00.0: link down error during global reset $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no In the 5.13.0-20 kernel, the device works: $ sudo dmesg | grep ath [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002) [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0 [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0x [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0 [ 351.080712] ath11k_pci :72:00.0: link down error during global reset [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:23:07 2021 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 InstallationDate: Installed on 2021-05-04 (190 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 09/30/2021 dmi.bios.release: 3.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.0 dmi.board.name: 0MRT12 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1949889] Re: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command
I can see tests being build and executed: * ubuntu_kernel_selftests.net:reuseport_bpf * ubuntu_kernel_selftests.net:reuseport_bpf_cpu * ubuntu_kernel_selftests.net:reuseport_dualstack * ubuntu_kernel_selftests.net:reuseaddr_conflict * buntu_kernel_selftests.net:reuseport_bpf_numa With Bionic 4.15.0-163.171 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949889 Title: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following binaries in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can only be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset and it's is not ideal for the granularity improvement, in which we will want to run tests one-by-one. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 1st and 5th patch can be cherry-picked. The 2nd needs to be backported with some context adjustment (can be applied with git -cp but not git am -C2). The 3rd and 4th patch would need to be applied with -C2. The third patch (8ce72dc3) is the fix for this issue. To get it applied more easily we will need the first two. The 4th (27d79a2b) and the 5th (e2e88325) patches are included here as they have been marked as a fix for 8ce72dc3. Since we don't use KBUILD_OUTPUT and the vm test, I think the risk of adding these two is pretty low. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change (compared side-by-side). Please find attachment in the bug report for the test result. [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949889/+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 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back
I can see this test available in Impish 5.13.0-22.22: ubuntu_kernel_selftests.net:l2tp.sh ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1934293 Title: Add l2tp.sh in net from ubuntu_kernel_selftests back Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable bit with our autotest-client-tests suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in the patch "UBUNTU: SAUCE: selftests/net -- disable timeout" Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in our test suite [2], we still need to revert that SAUCE patch to get it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" This test only exists in our tree since Focal. [Test] Run the net test suite in kselftest with patched source tree: sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] This is only for testing tools, however if commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we might crash our testing node like in bug 1854968. Also, we might see new failures caused by this test in the test report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934293/+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 1951563] Re: alsa/sdw: add sdw audio machine driver for several ADL machines
** Tags added: oem-priority originate-from-1926446 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951563 Title: alsa/sdw: add sdw audio machine driver for several ADL machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951563/+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 1951563] [NEW] alsa/sdw: add sdw audio machine driver for several ADL machines
Public bug reported: This bug is for tracking purpose. ** Affects: linux (Ubuntu) Importance: Medium Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Critical Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Medium Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Assignee: Hui Wang (hui.wang) => (unassigned) -- 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/1951563 Title: alsa/sdw: add sdw audio machine driver for several ADL machines Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951563/+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 1951470] Re: webkit javascript segmentation fault
adjusted the affected package (linux --> libqt5webkit5) ** Package changed: linux (Ubuntu) => qtwebkit-opensource-src (Ubuntu) ** Tags added: universe -- 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/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: New Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Andreas Krebbel - 2021-11-15 09:44:04 == In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes the property offset as pointer size (hence 64 bit) value: 2141: instructions[i + 6].u.pointer = reinterpret_cast(op.operand); while the same slot is accessed later by the jitted code as 32 bit integer: macro getProperty(slow) loadisFromInstruction(6, t1) This fails on big endian targets since the integer access takes the higher part of the 64 bit value. Changing: macro getProperty(slow) loadisFromInstruction(6, t1) to macro getProperty(slow) loadpFromInstruction(6, t1) in llint/LowLevelInterpreter64.asm fixes the problem for me. I could not reproduce the problem on Ubuntu 20.10. In upstream webkit the problem got fixed as a side effect of a larger change but in the end quite similar to the change I'm proposing. The value resides somewhere else now but it is accessed as 64 bit value in getProperty: macro getProperty() loadp OpGetFromScope::Metadata::m_operand[t5], t1 If you have the jsc binary from the webkit package available the problem can be reproduced with just 'jsc -e "i=Math.min"' == Comment: #2 - Andreas Krebbel - 2021-11-15 09:49:55 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1951470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
Effects Macbook Intel too, several people reporting similar issues on Reddit etc. nouveau_modeset argument helps device being able to sleep (power light slowly cycling etc) but that time it doesn't wake up the screen. Using nvidia drivers is not a possibility since they aren't working on old hardware/nvidia chip. (it is a separate bug) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] Re: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40
The bug referred to above (https://bugzilla.kernel.org/show_bug.cgi?id=214455) is marked as RESOLVED CODE_FIX. When should we expect to be getting this in Ubuntu? ** Bug watch added: Linux Kernel Bug Tracker #214455 https://bugzilla.kernel.org/show_bug.cgi?id=214455 -- 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/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+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 1951470] Re: webkit javascript segmentation fault
This does not look like an Ubuntu system. Linux kernel has wrong version: "Linux 193438490afd 5.8.15-301.fc33.s390x". Are you sure you are testing it on Ubuntu image? -- 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/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Andreas Krebbel - 2021-11-15 09:44:04 == In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes the property offset as pointer size (hence 64 bit) value: 2141: instructions[i + 6].u.pointer = reinterpret_cast(op.operand); while the same slot is accessed later by the jitted code as 32 bit integer: macro getProperty(slow) loadisFromInstruction(6, t1) This fails on big endian targets since the integer access takes the higher part of the 64 bit value. Changing: macro getProperty(slow) loadisFromInstruction(6, t1) to macro getProperty(slow) loadpFromInstruction(6, t1) in llint/LowLevelInterpreter64.asm fixes the problem for me. I could not reproduce the problem on Ubuntu 20.10. In upstream webkit the problem got fixed as a side effect of a larger change but in the end quite similar to the change I'm proposing. The value resides somewhere else now but it is accessed as 64 bit value in getProperty: macro getProperty() loadp OpGetFromScope::Metadata::m_operand[t5], t1 If you have the jsc binary from the webkit package available the problem can be reproduced with just 'jsc -e "i=Math.min"' == Comment: #2 - Andreas Krebbel - 2021-11-15 09:49:55 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1951470/+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 1951470] Re: webkit javascript segmentation fault
** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Andreas Krebbel - 2021-11-15 09:44:04 == In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes the property offset as pointer size (hence 64 bit) value: 2141: instructions[i + 6].u.pointer = reinterpret_cast(op.operand); while the same slot is accessed later by the jitted code as 32 bit integer: macro getProperty(slow) loadisFromInstruction(6, t1) This fails on big endian targets since the integer access takes the higher part of the 64 bit value. Changing: macro getProperty(slow) loadisFromInstruction(6, t1) to macro getProperty(slow) loadpFromInstruction(6, t1) in llint/LowLevelInterpreter64.asm fixes the problem for me. I could not reproduce the problem on Ubuntu 20.10. In upstream webkit the problem got fixed as a side effect of a larger change but in the end quite similar to the change I'm proposing. The value resides somewhere else now but it is accessed as 64 bit value in getProperty: macro getProperty() loadp OpGetFromScope::Metadata::m_operand[t5], t1 If you have the jsc binary from the webkit package available the problem can be reproduced with just 'jsc -e "i=Math.min"' == Comment: #2 - Andreas Krebbel - 2021-11-15 09:49:55 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1951470/+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
