[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04
** Changed in: ubuntu-release-notes Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924685 Title: No sound output/input available after installing 21.04 Status in OEM Priority Project: Won't Fix Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+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 1924717] Re: Internal speaker doesn't work after plug in a headset
** Changed in: ubuntu-release-notes Status: New => Fix Released ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924717 Title: Internal speaker doesn't work after plug in a headset Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: [Summary] Internal speaker doesn't work after plug in a headset. In the meantime, audio for HDMI/Buletooth headset/wired headset are working fine. Only Internal speaker doesn't work. But internal speaker working well if not plug wired headset in. CID:202010-28313 https://certification.canonical.com/hardware/202010-28313/ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1512 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 05:07:59 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Latitude 5520 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.11.0-14-generic root=UUID=8bcd3f6a-d6e8-494d-93fa-6f720bf6e582 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 1132343535 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/13/2021:br1.2:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1924717/+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 1919177] Re: Azure: issues with accelerated networking on Hirsute
** Changed in: cloud-init (Ubuntu)
Milestone: ubuntu-21.04 => hirsute-updates
** Changed in: linux-azure (Ubuntu)
Milestone: ubuntu-21.04 => hirsute-updates
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+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 1926145] Re: bluetooth disconnects and reconnects on 21.04
** Package changed: ubuntu => bluez (Ubuntu) ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926145 Title: bluetooth disconnects and reconnects on 21.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth speaker disconnects randomly and reconnects again. Problem occurred after upgrade to Ubuntu 21.04 ( -d ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926145/+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 1925964] Re: HP NC364T NIC with 20.04.2 LTS Issues
** Package changed: ubuntu => 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/1925964 Title: HP NC364T NIC with 20.04.2 LTS Issues Status in linux package in Ubuntu: New Bug description: This NIC is a 4 Port Copper 1GB Intel 82571B/82571GB Gigabit Ethernet Controller with a Dual Chipset where each Chipset controls 2 ports each (ie (1 Chipset - 2 Ports) * 2). In the latest 20.04.2 LTS, the OS is mapping the ports incorrectly, causing only 2 of the 4 total ports to be allocated via DMESG: thannock@nwtools04-usdc7:~$ lspci 00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev b1) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1) 00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev b1) 00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev b1) 00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 (rev b1) 00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev b1) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09) 00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09) 01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02) 01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out Controller (rev 03) 01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out Processor (rev 03) 01:04.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard Virtual USB Controller 01:04.6 IPMI Interface: Hewlett-Packard Company Integrated Lights-Out Standard KCS Interface 02:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 04:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 05:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 06:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev b4) 07:04.0 PCI bridge: Broadcom BCM5785 [HT1000] PCI/PCI-X Bridge (rev b2) 07:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i (SAS Controller) 09:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) 09:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) 0a:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) 0a:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01) 0a:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01) 0b:00.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0c:02.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0c:04.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) 0d:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 0d:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 0e:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) 0e:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller
[Kernel-packages] [Bug 1924970] Re: Add soundwire sdca codec support
How is the following patch related to this SRU bug? d/p/0001-ucm2-soundwire-use-cfg-amp-instead-of-cfg-spk-component- string.patch >From what I can tell it doesn't seem to be related. ** Changed in: alsa-ucm-conf (Ubuntu) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1924970 Title: Add soundwire sdca codec support Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Incomplete Bug description: [Impact] * The output device in sound settings will non-functional. Sound input device will be empty. An upstream commit add supports for SDW sdca codec support. [Test Plan] * Open settings and select Sound column. Testing speaker won't have any sound output. * Try to update files mentioned here https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/a7f348bb37d2b3254801702299ab2c76833a3c16 https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/651c2c851bf17a1d76e0a046eb33eccbcf98845f * alsactl init * Open settings and select Sound column and test output device again. Sound devices work properly. [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. [Other Info] * The change has been verified on Dell machine with sdca codec. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924970/+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 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Summary changed: - Hot-unplug of disks leaves broken block devices around in Hirsute + Hot-unplug of disks leaves broken block devices around in Hirsute on s390x ** Changed in: linux (Ubuntu Hirsute) Milestone: None => hirsute-updates -- 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+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 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
** Also affects: udev (Ubuntu Hirsute) Importance: Critical Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: systemd (Ubuntu Hirsute) 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+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 1925026] Re: Timer of 100us causes 64-bit app spin on Pi4
** Tags added: raspi-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/1925026 Title: Timer of 100us causes 64-bit app spin on Pi4 Status in linux package in Ubuntu: Confirmed Bug description: This problem happens with 64-bit 20.04 LTS or 20.10 on a Raspberry Pi 4 w/4GB (I am using the official Ubuntu Pi versions). It does NOT happen with either version when running on a standard x86 machine or VM. Also, it does NOT happen when using the 64-bit Raspberry Pi OS (https://downloads.raspberrypi.org/raspios_arm64/images/). So this issue is specific to the official 64-bit Ubuntu on Raspberry Pi version. When a 100us timer is started (via setitimer) the app will spin at 100%. With values slightly higher (150, 200, 1000) this does not happen. I've included the source for a small timer test program that I found reproduces the issue that broke my larger formal app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925026/+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 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Tags removed: rls-hh-incoming ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+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 1923844] Re: i915 drm GPU hang - introduced with linux-image-5.8.0-49-generic
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923844 Title: i915 drm GPU hang - introduced with linux-image-5.8.0-49-generic Status in linux package in Ubuntu: Confirmed Bug description: This is a regression introduced with the latest kernel (linux- image-5.8.0-49-generic). Kubuntu 20.04, since upgrading kernel from version 5.8.0-48.54 to version 5.8.0-49.55 the system boots properly but the GUI often hangs, either immediately after user login to GUI or any time after that (screen stops updating with various artifacts and UI no longer responds) and computer has to be restarted. Messages like these appear in dmesg: Apr 13 08:43:24 kubuntu kernel: [47776.927523] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 08:43:24 kubuntu kernel: [4.029098] i915 :00:02.0: [drm] VMSVGA FIFO[40] context reset due to GPU hang Apr 13 11:25:37 kubuntu kernel: [ 45.168120] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85fc, in plasmashell [2918] Apr 13 11:25:37 kubuntu kernel: [ 45.168166] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 11:25:37 kubuntu kernel: [ 45.270406] i915 :00:02.0: [drm] plasmashell[2918] context reset due to GPU hang Apr 13 11:25:41 kubuntu kernel: [ 47.984475] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85fc, in plasmashell [2918] Apr 13 11:25:41 kubuntu kernel: [ 47.984520] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 11:25:41 kubuntu kernel: [ 48.088097] i915 :00:02.0: [drm] plasmashell[2918] context reset due to GPU hang Apr 13 11:25:47 kubuntu kernel: [ 54.128068] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85fc, in plasmashell [2918] Apr 13 11:25:47 kubuntu kernel: [ 54.128111] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 11:25:47 kubuntu kernel: [ 54.230401] i915 :00:02.0: [drm] plasmashell[2918] context reset due to GPU hang Apr 14 14:35:53 kubuntu kernel: [ 32.106297] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:c07f, in ksplashqml [3096] Apr 14 14:35:53 kubuntu kernel: [ 32.106341] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 14 14:35:53 kubuntu kernel: [ 32.207704] i915 :00:02.0: [drm] ksplashqml[3096] context reset due to GPU hang With previous kernel 5.8.0-48.54 (and all other previous kernels) there was never any problem like this. System is Asus P8Z68V-Pro Gen3, i7-3770, iGPU: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 61 Memory at f740 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 Boot info with i915 and drm: [0.00] microcode: microcode updated early to revision 0x21, date = 2019-02-13 [0.00] Linux version 5.8.0-49-generic (buildd@lgw01-amd64-055) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #55~20.04.1-Ubuntu SMP Fri Mar 26 01:01:07 UTC 2021 (Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.8.0-49-generic root=UUID=123 ro quiet splash vt.handoff=7 [0.00] DMI: System manufacturer System Product Name/P8Z68-V PRO GEN3, BIOS 3802 01/15/2015 [1.083804] fb0: switching to inteldrmfb from EFI VGA [1.083864] i915 :00:02.0: vgaarb: deactivate vga console [1.093201] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.097872] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.119734] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [1.260356] fbcon: i915drmfb (fb0) is primary device [1.260360] i915 :00:02.0: fb0: i915drmfb frame buffer device [5.070962] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. [5.526454] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Not blocking as I can stay on previous kernel but until this is fixed I can no longer use vulnerability fixes
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
** Changed in: u-boot (Ubuntu) Status: Confirmed => In Progress ** Also affects: u-boot (Ubuntu Hirsute) Importance: Critical Status: In Progress ** Also affects: u-boot-menu (Ubuntu Hirsute) Importance: Critical Status: Fix Released ** Also affects: linux-riscv (Ubuntu Hirsute) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: In Progress Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: In Progress Status in u-boot-menu source package in Hirsute: Fix Released Bug description: When booting v5.11 based riscv unmatched image in qemu with uboot, it fails to boot. When booting v5.11 based riscv unmatched kernel+initrd directly, it boots fine. Somehow, it seems that u-boot fails to correctly load & start v5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+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 1920916] Re: cold boot panics on unmatched board, soft reboot is fine
There should be a kernel available with this fix on Monday. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1920916 Title: cold boot panics on unmatched board, soft reboot is fine Status in linux-riscv package in Ubuntu: In Progress Bug description: [ 16.622852] Kernel panic - not syncing: L2CACHE: DirFail @ 0x.0001CB00 [ 16.629408] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.0-1004-generic #4-Ubuntu [ 16.637136] Call Trace: [ 16.639655] [] walk_stackframe+0x0/0xcc [ 16.645131] SMP: stopping secondary CPUs [ 16.649144] ---[ end Kernel panic - not syncing: L2CACHE: DirFail @ 0x.0001CB00 ]--- On cold boot, I am observing L2CACHE DirFail panic, then after soft reset it boots fine. See full attached screenlog.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1920916/+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 1890641] Update Released
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1890641
Title:
Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
module r8169
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Bionic:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing firmware for Realtek RTL8153 Based USB Ethernet Adapters,
which is supported by linux-generic-hwe-18.04 kernel (currently v5.4).
[Fix]
Two upstream commit necessary:
* commit b27d12383e7a ("rtl_nic: add firmware files for RTL8153")
* commit 6f89735800fe ("rtl_nic: update firmware for RTL8153A")
[Test Case]
Without firmware, drive probe would fail with:
$ dmesg | grep firmware | grep rtl8153
r8152 2-4.1:1.0: firmware: failed to load rtl_nic/rtl8153a-2.fw (-2)
r8152 2-4.1:1.0: Direct firmware load for rtl_nic/rtl8153a-2.fw failed with
error -2
r8152 2-4.1:1.0: unable to load firmware patch rtl_nic/rtl8153a-2.fw (-2)
With firmware, it should succeed:
$ dmesg | grep rtl8152
r8152 2-1:1.0: load rtl8153a-3 v2 02/07/20 successfully
r8152 2-1:1.0 eth0: v1.11.11
r8152 2-1:1.0 enp0s20f0u1: renamed from eth0
[Where problems could occur]
While this introduces new firmware blobs and enabled devices supported
by new kernels, it should have little effect on existing systems, but
with new devices up and running, it may still affect power consumptions,
ability to enter deep suspend, etc.
[Other Info]
RTL8153 firmware has been available on Eoan and newer, so only Bionic is
nominated.
== original bug report ==
Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
module r8169
after running sudo apt upgrade in ubuntu 18.04
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 6 22:38:31 2020
InstallationDate: Installed on 2019-06-16 (417 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
Log time: 2020-03-08 22:54:00.439353
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1890641/+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 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
Could you please provide some details regarding the steps you took to
verify that this SRU was good?
** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1890641
Title:
Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
module r8169
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Bionic:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
Missing firmware for Realtek RTL8153 Based USB Ethernet Adapters,
which is supported by linux-generic-hwe-18.04 kernel (currently v5.4).
[Fix]
Two upstream commit necessary:
* commit b27d12383e7a ("rtl_nic: add firmware files for RTL8153")
* commit 6f89735800fe ("rtl_nic: update firmware for RTL8153A")
[Test Case]
Without firmware, drive probe would fail with:
$ dmesg | grep firmware | grep rtl8153
r8152 2-4.1:1.0: firmware: failed to load rtl_nic/rtl8153a-2.fw (-2)
r8152 2-4.1:1.0: Direct firmware load for rtl_nic/rtl8153a-2.fw failed with
error -2
r8152 2-4.1:1.0: unable to load firmware patch rtl_nic/rtl8153a-2.fw (-2)
With firmware, it should succeed:
$ dmesg | grep rtl8152
r8152 2-1:1.0: load rtl8153a-3 v2 02/07/20 successfully
r8152 2-1:1.0 eth0: v1.11.11
r8152 2-1:1.0 enp0s20f0u1: renamed from eth0
[Where problems could occur]
While this introduces new firmware blobs and enabled devices supported
by new kernels, it should have little effect on existing systems, but
with new devices up and running, it may still affect power consumptions,
ability to enter deep suspend, etc.
[Other Info]
RTL8153 firmware has been available on Eoan and newer, so only Bionic is
nominated.
== original bug report ==
Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
module r8169
after running sudo apt upgrade in ubuntu 18.04
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 6 22:38:31 2020
InstallationDate: Installed on 2019-06-16 (417 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
Log time: 2020-03-08 22:54:00.439353
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1890641/+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 1908677] Update Released
The verification of the Stable Release Update for alsa-ucm-conf has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1908677 Title: Dell Latitude 9510 capture volume is too low Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: [Impact] * The internal mic default volume is too low A upstream commit correct the init configuration [Test Case] * Using gnome-sound-recoder to record audio without tweak capture volume The volume is very low * Try to update the init.conf mentioned by https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e $ alsactl init $ amixer cget name='rt715 ADC 07 Capture Volume' numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0 : values=58,58 | dBscale-min=-17.25dB,step=0.75dB,mute=0 * Using gnome-sound-recorder to record again The volume is significantly improved [Where problems could occur] * The change only apply to the hardware with rt715 codec. * [racb] Is there any other hardware that isn't being tested that uses this codec? * The change adjust the volume only, but not change other control, the worst case is the change doesn't take effect. [Other Info] * The change has been verified on Latitude 9510. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908677/+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 1921944] Re: ubuntu 20.04 kernel 5.8.0.48 freezes when thinkpad stylus touches screen Lenovo thinkpad Yoga X1 first series
** Package changed: ubuntu => 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/1921944 Title: ubuntu 20.04 kernel 5.8.0.48 freezes when thinkpad stylus touches screen Lenovo thinkpad Yoga X1 first series Status in linux package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 When ubuntu 20.04 kernel 5.8.0.48 is running and stylus touches screen, ubuntu freezes completely and hard restart via on/of button laptop is necessary. In kernel 5.8.0.44 it still worked/works OKAY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921944/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Hello Dave, or anyone else affected, Accepted bluez into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.1 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. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Committed Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1920179] Re: System freezes when using Wacom tablet after upgrading to linux-image-5.8.0-45-generic
** Package changed: ubuntu-release-upgrader (Ubuntu) => 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/1920179 Title: System freezes when using Wacom tablet after upgrading to linux- image-5.8.0-45-generic Status in linux package in Ubuntu: Confirmed Bug description: I have an Lenovo Thinkpad Yoga 260 with a built-in Wacom digitizer. After the latest Kernel update my system freezes as soon as I put the pen on the screen. Nothing else but a forced power-off is possible. Reverting back to 5.8.0-44 is a work-around, so this seems to be a regression. The relevant entry from /var/log/apt/history.log: Start-Date: 2021-03-17 11:37:43 Commandline: apt dist-upgrade Install: linux-image-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-headers-5.8.0-45:amd64 (5.8.0-45.51, automatic), linux-modules-extra-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-headers-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-modules-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), dctrl-tools:amd64 (2.24-3, automatic) Upgrade: update-manager-core:amd64 (1:20.10.4, 1:20.10.5), linux-headers-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), linux-libc-dev:amd64 (5.8.0-44.50, 5.8.0-45.51), linux-image-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), update-manager:amd64 (1:20.10.4, 1:20.10.5), dkms:amd64 (2.8.3-4, 2.8.3-4ubuntu0.1), python3-update-manager:amd64 (1:20.10.4, 1:20.10.5), libglib2.0-bin:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), libglib2.0-data:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), linux-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), libglib2.0-0:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), libglib2.0-0:i386 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2) End-Date: 2021-03-17 11:38:44 Apport is enabled but no crash report is generated. BTW, I found a similar bug report for Manjaro: https://forum.manjaro.org/t/system-freezes-when-using-wacom-tablet-on-5-10/50339 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 [origin: unknown] ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Fri Mar 19 12:41:12 2021 InstallationDate: Installed on 2020-04-14 (338 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-11-12 (127 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920179/+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 1919342] Re: Stylus and touchscreen not working in kernel 5.8.0-45
** No longer affects: ubuntu-release-upgrader (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/1919342 Title: Stylus and touchscreen not working in kernel 5.8.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After an update from 16th March 2021, the stylus for Acer Spin 5 stopped working and wasn't charging. Returning to version 5.8.0-43 fixed the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 16 16:12:45 2021 InstallationDate: Installed on 2020-12-23 (82 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919342/+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 1918065] Re: Zen 3 (Ryzen 5XXX) temperatures not reported by k10temp
** Package changed: ubuntu => 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/1918065 Title: Zen 3 (Ryzen 5XXX) temperatures not reported by k10temp Status in linux package in Ubuntu: New Bug description: Current reports from `sensors` for Zen 3 CPUs: ``` PCH_CHIP_CPU_MAX_TEMP: +0.0°C PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C ``` This bug is due to the lack of Zen 3 support in Ubuntu's implementation of k10temp. Zen 3 (Ryzen 5XXX) temperature support is now ready as a part of `k10temp`: https://www.kernel.org/doc/html/latest/hwmon/k10temp.html and narrowly missed the window for mainline kernel 5.12. My understanding is it was included in 5.10, removed in 5.11 for documentation/validation reasons, then planned again after updates. With the popularity of these chips increasing, having accurate CPU temp readings is of import in Ubuntu 20.04, as this is an LTS release with support until 2025. Therefore, as we are set at kernel 5.8 at the moment, with 21.04 releasing with kernel 5.11, it may be worth pulling in the latest k10temp to fix this bug as to not delay access to vital CPU information throughout 2020. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918065/+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 1917210] Re: Dell XPS 13 2in1 wakes from sleep when moved on 20.04
** Package changed: ubuntu => 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/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 Status in linux package in Ubuntu: New Bug description: Dell XPS 13 9310 2in1, running Ubuntu OEM kernel (20.04) on 20.04 LTS. Laptop suspends and wakes up when lid is closed and opened, respectively. Laptop erroneously wakes up also in following conditions: 1. lid is closed and laptop is moved/rotated. 2. lid is open, suspended manually (via power button), and laptop is moved/rotated. Until I found out about case 2, I assumed that the hall sensor triggered on slight opening of the lid. However, case 2 shows that this is unlikely a hard ware defect/sensitivity. I suspect that the accelaration sensor triggers waking up from sleep. I can confirm that the problem persist after stopping the iio-sensor-prox service via systemctl. I did not find which kernel module is reponsible for tracking this sensor. Suggestions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+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 1916727] Re: Second monitor not detected after kernel update for Ubuntu 20.04 LTS
** Package changed: linux-hwe-5.8 (Ubuntu) => 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/1916727 Title: Second monitor not detected after kernel update for Ubuntu 20.04 LTS Status in linux package in Ubuntu: New Bug description: Hi I want to follow up this problem (https://answers.launchpad.net/ubuntu/+question/695719) that these updates have a problem: linux-modules-5.8.0-44-generic:amd64 5.8.0-44.50~20.04.1 install linux-image-5.8.0-44-generic:amd64 5.8.0-44.50~20.04.1 install linux-modules-extra-5.8.0-44-generic:amd64 5.8.0-44.50~20.04.1 install linux-hwe-5.8-headers-5.8.0-44:all 5.8.0-44.50~20.04.1 install linux-headers-5.8.0-44-generic:amd64 5.8.0-44.50~20.04.1 The result is: I cannot boot to my own desktop and I have to downgrade my kernel to 5.8.0.43. Can you check it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916727/+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 1916340] Re: Logitech G920 Driving Force don't work when using external USB hub
** Package changed: ubuntu => 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/1916340 Title: Logitech G920 Driving Force don't work when using external USB hub Status in linux package in Ubuntu: New Bug description: I bought a USB hubs that allow to switch ON and OFF every USB port separately. Idea is not to connect and disconnect all the time unnecessary USB peripheral devices like cameras, and especially Logitech G920 Driving Force gaming wheel. I want to notice there is no hardware problem – the wheel is fully functional thru the USB hub under Windows 10. The following is the output of the lsusb and dmesg -w commands in the following situation: 1. No hub connected to PC 2. USB hub connected to PC, USB ports on the hub all switched off. 3. USB hub connected to PC, Logitech G920 Driving Force connected and switched on thru the USB hub 4. After connecting Logitech G920 Driving Force directly to PC(the wheel is working): From what I see when the wheel is connected thru the USB hub HID++ force feedback module is not loading. 1.No hub connected to PC: lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 1532:021e Razer USA, Ltd Bus 001 Device 005: ID 1532:005c Razer USA, Ltd Bus 001 Device 004: ID 046d:082b Logitech, Inc. Webcam C170 Bus 001 Device 003: ID 1532:0514 Razer USA, Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 2.USB HUB connected to PC, USB ports on hub switched off: lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 1532:021e Razer USA, Ltd Bus 001 Device 005: ID 1532:005c Razer USA, Ltd Bus 001 Device 004: ID 046d:082b Logitech, Inc. Webcam C170 Bus 001 Device 003: ID 1532:0514 Razer USA, Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 3.After switching on Logitech G920 Driving Force THRU USB hub: lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 007: ID 046d:c261 Logitech, Inc. Bus 003 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 1532:021e Razer USA, Ltd Bus 001 Device 005: ID 1532:005c Razer USA, Ltd Bus 001 Device 004: ID 046d:082b Logitech, Inc. Webcam C170 Bus 001 Device 003: ID 1532:0514 Razer USA, Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg -w [ 7127.803087] usb 3-1.4: new full-speed USB device number 7 using xhci_hcd [ 7127.929279] usb 3-1.4: New USB device found, idVendor=046d, idProduct=c261, bcdDevice=96.01 [ 7127.929284] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7127.929287] usb 3-1.4: Product: G920 Driving Force Racing Wheel for Xbox One [ 7127.929302] usb 3-1.4: Manufacturer: Logitech [ 7127.929305] usb 3-1.4: SerialNumber: 0bf1c8867e46 4.Connecting Logitech G920 Driving Force directly, without USB hub: lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 009: ID 046d:c262 Logitech, Inc. G920 Driving Force Racing Wheel for Xbox One Bus 003 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 1532:021e Razer USA, Ltd
[Kernel-packages] [Bug 1916064] Re: Touchpad not detected on Ideapad 14ARE05
** Package changed: ubuntu => 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/1916064 Title: Touchpad not detected on Ideapad 14ARE05 Status in linux package in Ubuntu: New Bug description: Laptop: Lenovo Ideapad 5-14ARE05 Laptop - Type 81YM - AMD Ryzen 7 4700U Description: Ubuntu 20.10 Release: 20.10 Linux leptovo 5.8.0-43-generic #49-Ubuntu SMP Fri Feb 5 03:01:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Also tested with: Linux leptovo 5.11.0-051100-generic #202102142330 SMP Sun Feb 14 23:33:21 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux - and other kernels. Hello! After updating the BIOS from 1.06 to 1.10 the touchpad is not recognised anymore. It was working fine with 5.9.12 (updated the version with Ukuu), but now it does not respons with any verion tried by me: 5.8.0.43 / 5.9.16 / 5.10.17 / 5.11.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916064/+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 1916028] Re: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5
** Package changed: ubuntu => 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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: New Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1915931] Re: All versions of Ubuntu hang on boot, bug with NVME drive, i think
** Package changed: ubuntu => 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/1915931 Title: All versions of Ubuntu hang on boot, bug with NVME drive, i think Status in linux package in Ubuntu: Incomplete Bug description: So, after trying multiple versions of Ubuntu (usb installer), all of them failed to boot. Also lubuntu. I was able to fix it using this comment here: https://www.reddit.com/r/linuxhardware/comments/b39orv/ryzen_3550h_asus_tuf_gaming_fx505dy_do_i_need_to/ejeqkji/ In particular, just doing this: "I found that the 256gb nvme Asus used was a wd black series and it has issues on Linux. Try using this on your kernel boot line: nvme_core.default_ps_max_latency_us=5500" I added this to grub and it works perfectly now. This is on an ASUS fx505dy with a Western Digital 256gb nvme black series, and I've seen other users with the same hard drive report similar problems, but different laptops so I think it the HD. sorry, I don't know what package is responsible for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915931/+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 1915659] Re: MSI computer desktop linux kernel 5.8 bug jammed and freeze all programs
** Package changed: ubuntu-meta (Ubuntu) => 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/1915659 Title: MSI computer desktop linux kernel 5.8 bug jammed and freeze all programs Status in linux package in Ubuntu: Incomplete Bug description: MSI computer desktop linux kernel 5.8 bug jammed and freeze all programs i am removed linux kernel 5.8 my MSI computer desktop because when same is trying install again ubuntu 20.04.2 LTS is jammed and nothing happen my MSI desktop computer only MSI desktop linux kernel 5.4 is working only my MSI computer MSI desktop linux kernel 5.8 dont working only jammed and freeze all programs this my intel graphic card information my MSI computer *-display description: VGA compatible controller product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:32 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915659/+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 1872908] Re: bcmwl kernel module does not build with kernel version 5.6 or 5.8
** Changed in: bcmwl (Ubuntu Focal)
Milestone: None => ubuntu-20.04.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1872908
Title:
bcmwl kernel module does not build with kernel version 5.6 or 5.8
Status in bcmwl package in Ubuntu:
Fix Released
Status in bcmwl source package in Focal:
Fix Released
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, _fops,
wl)) == NULL) {
| ^~~~
|
[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel or later
** Changed in: bcmwl (Ubuntu Focal)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1872908
Title:
bcmwl kernel module does not build with 5.6.0 kernel or later
Status in bcmwl package in Ubuntu:
Fix Released
Status in bcmwl source package in Focal:
Triaged
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
3376 | if ((wl->proc_entry = proc_create_data(t
[Kernel-packages] [Bug 1902355] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1902355 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: on a fresh install which happened with no wifi connection so no updates during install once installed I defined a good wifi connection then ran apt-get update && apt-get upgrade I get this error on next reboot ProblemType: Package DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-26-generic Date: Sat Oct 31 07:54:08 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7:./include/linux/log2.h:24:1: error: stray ‘\1’ in program InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageVersion: 6.30.223.271+bdcom-0ubuntu7 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: linux-image-5.8.0-26-generic linux-base RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1902355/+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 1910607] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: el subproceso instalado paquete bcmwl-kernel-source script post-installation devo
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910607 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: el subproceso instalado paquete bcmwl-kernel-source script post-installation devolvió el código de salida de error 10 Status in bcmwl package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: linux-image-5.8.0-34-generic:amd64: Purge linux-modules-5.8.0-34-generic:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 7 17:25:31 2021 ErrorMessage: el subproceso instalado paquete bcmwl-kernel-source script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2020-11-20 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: el subproceso instalado paquete bcmwl-kernel-source script post-installation devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910607/+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 1905211] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in kernel v5.9
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1905211 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in kernel v5.9 Status in bcmwl package in Ubuntu: New Bug description: Impact The DKMS package won't work with new kernel v5.9 on focal fossa. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 Uname: Linux 5.9.0-050900-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: bcmwl-kernel-source:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 17:23:01 2020 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-11-16 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1905211/+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 1914052] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1914052 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-41-generic Date: Mon Feb 1 10:09:25 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-02-01 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1914052/+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 1909369] Re: linux-headers-5.10.3-051003-generic is not supported
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1909369 Title: linux-headers-5.10.3-051003-generic is not supported Status in bcmwl package in Ubuntu: Confirmed Bug description: > $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 > $ sudo apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installé : (aucun) Candidat : 6.30.223.271+bdcom-0ubuntu5 Table de version : 6.30.223.271+bdcom-0ubuntu5 500 500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages Hello, I tried to install a wireless network adapter broadcom BCM4360, i nned to install the package bcmwl-kernel-source but when i try to install it i have the following error : "ERROR (dkms apport): kernel package linux-headers-5.10.3-051003-generic is not supported Error! Bad return status for module build on kernel: 5.10.3-051003-generic (x86_64) " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source (not installed) Uname: Linux 5.10.3-051003-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 21:16:07 2020 InstallationDate: Installed on 2020-01-05 (356 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1909369/+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 1913890] Re: My device is ASUS ViviBook x507. I installed Ubuntu 20.04 LTS. I have a fingerprint sensor that worked with windows 10. Ubuntu can't even recognise it . It wont eve
** Package changed: ubuntu => 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/1913890 Title: My device is ASUS ViviBook x507. I installed Ubuntu 20.04 LTS. I have a fingerprint sensor that worked with windows 10. Ubuntu can't even recognise it . It wont even show up in lsusb, lspci or lshw. Status in linux package in Ubuntu: New Bug description: (base) akash@Akash-Asus:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (base) akash@Akash-Asus:~$ ^C (base) akash@Akash-Asus:~$ fprintd-enroll list_devices failed: No devices available (base) akash@Akash-Asus:~$ ^C (base) akash@Akash-Asus:~$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 (rev 21) 00:1e.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO SPI Controller #0 (rev 21) 00:1e.6 SD Host controller: Intel Corporation Sunrise Point-LP Secure Digital IO Controller (rev 21) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX130] (rev a2) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) (base) akash@Akash-Asus:~$ lshw WARNING: you should run this program as super-user. akash-asus description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 8GiB *-cpu product: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 1132MHz capacity: 3400MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 08 width: 32 bits clock: 33MHz configuration: driver=skl_uncore resources: irq:0 *-display description: VGA compatible controller product: UHD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
Hello bugproxy, or anyone else affected,
Accepted s390-tools into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/s390-tools/2.12.0-0ubuntu3.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: s390-tools (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags removed: verification-done-focal
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Release Notes for Ubuntu:
New
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
[Kernel-packages] [Bug 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
This bug report is missing SRU information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) Status in OEM Priority Project: New Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: The work that went into ubuntu-drivers-common and nvidia-prime is meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid systems, introduced by the NVIDIA 450 driver series. This allows the supported systems to make use of the integrated GPU (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until needed. While powered down, the NVIDIA GPU can still detect any events, should external displays be plugged in. This brings hybrid graphics on Linux on par with Windows. Only the supported GPUs will be able to benefit from this change. This is why NVIDIA provides a hardware database (included in the nvidia packages), which gpu-manager can now parse. The ubuntu-drivers tool relies on that detection to enable this new feature when installing the NVIDIA driver. Another improvement is the ability of ubuntu-drivers to detect LTSB (Long term support branch), NFB (New feature branch), Legacy, Beta flags, which the NVIDIA drivers can have, and make informed detection choices. This work also includes a number of bug fixes reported on errors.ubuntu.com. Requirements: The new ubuntu-drivers-common: The new nvidia-prime: Changes to the NVIDIA drivers: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+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 1910664] Re: Need a new firmware to support RTL8821ce Wifi
Hello AceLan, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.9 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: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1910664 Title: Need a new firmware to support RTL8821ce Wifi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] It shows below messages and fails to enable the wifi [ 3.965229] u kernel: rtw_8821ce :04:00.0: enabling device ( -> 0003) [ 3.965403] u kernel: rtw_8821ce :04:00.0: Direct firmware load for rtw88/rtw8821c_fw.bin failed with error -2 [ 3.965405] u kernel: rtw_8821ce :04:00.0: failed to request firmware [ 3.967613] u kernel: rtw_8821ce :04:00.0: failed to load firmware [Fix] There is a new firmware need to cherry pick 401bd6de rtw88: RTL8821C: add firmware file v24.5 [Test] After add the firmware, it shows [ 3.930187] rtw_8821ce :04:00.0: enabling device ( -> 0003) [ 3.931104] rtw_8821ce :04:00.0: Firmware version 24.5.0, H2C version 12 [ 3.999271] rtw_8821ce :04:00.0 wlp4s0: renamed from wlan0 [Where problems could occur] No problems could occur since it enables a new device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1910664/+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 1911456] Re: Can't receive files over bluetooth unless settings dialog is open
** Tags added: focal ** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1911456 Title: Can't receive files over bluetooth unless settings dialog is open Status in bluez package in Ubuntu: New Bug description: On 18.04 I could send files from my phone to my laptop at any time. On 20.04 I can't get files to be accepted by the laptop over bluetooth. After much frustration and experimenting, I figured out that it will work, but only if the bluetooth settings dialog is open. If the settings dialog is not open, the incoming file is rejected. If the dialog is closed after the file transfer begins, the transfer continues but the file is discarded when the transfer is complete. This is very frustrating. I need to be able to send files (mostly photos and videos) from my phone to my laptop without having to open the settings dialog on the laptop, just like I could before upgrading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1911456/+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 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
** Also affects: bluez (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Hirsute) Importance: High Assignee: Dave Jones (waveform) Status: New ** Tags removed: rls-gg-incoming rls-hh-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: New Status in bluez source package in Groovy: New Status in bluez source package in Hirsute: New Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+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 1910566] Re: Problem with the CH341 driver in Ubuntu 20.04
** Project changed: kernel => 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/1910566 Title: Problem with the CH341 driver in Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I run into this problem trying to program an ESP8266 board, which uses the CH341 chip in the programming interface as a USB-to-Serial interface. The problem appeared after an upgrade from Ubuntu 19.10 to 20.04 (that I carried out one week ago). This is the kernel I am using: === $ uname -r 5.4.0-58-generic === When I connect the ESP8266 board (a Wemos D1 mini) to the USB there is no activity on the syslog (or dmesg), and the kernel module is not loaded. In fact I do not see the /dev/ttyACM0 device in the /dev directory and no useful device appears in the Arduino GUI. I have found the module in the kernel tree but, even forcing the installation, nothing happens: === augusto@Legion:~$ ls /usr/lib/modules/5.4.0-58-generic/kernel/drivers/usb/serial/ch* /usr/lib/modules/5.4.0-58-generic/kernel/drivers/usb/serial/ch341.ko augusto@Legion:~$ sudo modprobe ch341 [sudo] password di augusto: augusto@Legion:~$ lsusb Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 005: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 006: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 001 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub augusto@Legion:~$ lsmod | grep ch34 ch341 20480 0 usbserial 53248 1 ch341 === Without this module it is impossible to work with a relevant number of SBC devices, besides the named Wemos D1 Mini. Trying to solve the problem I also downloaded and installed the module source from https://github.com/juliagoda/CH341SER and compiled on my PC, after removing the "secure boot" feature. I recovered the module installation trace from the syslog files in the previous installation Ubuntu 19.10. The kernel version was probably 5.3.0-64-generic. As said above, at that time the module was operating properly: you notice that the module is loaded and later used to update a sketch: == Dec 30 12:22:43 Legion kernel: [2354065.515635] usb 1-3: new full-speed USB device number 30 using xhci_hcd Dec 30 12:22:43 Legion kernel: [2354065.664692] usb 1-3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64 Dec 30 12:22:43 Legion kernel: [2354065.664697] usb 1-3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Dec 30 12:22:43 Legion kernel: [2354065.664701] usb 1-3: Product: USB Serial Dec 30 12:22:43 Legion kernel: [2354065.666768] ch341 1-3:1.0: ch341-uart converter detected Dec 30 12:22:43 Legion kernel: [2354065.667695] usb 1-3: ch341-uart converter now attached to ttyUSB1 Dec 30 12:22:43 Legion mtp-probe: checking bus 1, device 30: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Dec 30 12:22:43 Legion mtp-probe: bus: 1, device: 30 was not an MTP device Dec 30 12:22:43 Legion snapd[15280]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug Dec 30 12:22:43 Legion mtp-probe: checking bus 1, device 30: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Dec 30 12:22:43 Legion mtp-probe: bus: 1, device: 30 was not an MTP device Dec 30 12:22:45 Legion ModemManager[1198]: Couldn't check support for device '/sys/devices/pci:00/:00:14.0/usb1/1-3': not supported by any plugin Dec 30 12:22:46 Legion systemd[6301]: tracker-extract.service: Succeeded. Dec 30 12:22:46 Legion dbus-daemon[1183]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.52054' (uid=1000 pid=18287 comm="/usr/bin/gnome-shell " label="unconfined") Dec 30 12:22:46 Legion systemd[1]: Starting Fingerprint Authentication Daemon... Dec 30 12:22:46 Legion dbus-daemon[1183]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 30 12:22:46 Legion systemd[1]: Started Fingerprint Authentication Daemon. Dec 30 12:22:50 Legion NetworkManager[1193]: [1609327370.5477] agent-manager: req[0x5574cc0e7540, :1.52054/org.gnome.Shell.NetworkAgent/1000]: agent registered Dec 30 12:22:50 Legion gnome-shell[18287]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.87/org/ayatana/NotificationItem/software_update_available Dec 30 12:22:50 Legion gnome-shell[18287]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.82/org/ayatana/NotificationItem/dropbox_client_18678 Dec 30 12:22:50
[Kernel-packages] [Bug 1910108] Re: computer crashes soon after startup
** Package changed: ubuntu-release-upgrader (Ubuntu) => 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/1910108 Title: computer crashes soon after startup Status in linux package in Ubuntu: New Bug description: Computer crashes about 30 seconds after logging in and connecting with websites.First the screen goes blank, then the hard drive shuts down, and in about 30 seconds it starts up again requiring a new sign-in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.29 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 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jan 4 09:20:14 2021 InstallationDate: Installed on 2020-06-21 (197 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910108/+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 1909417] Re: ubuntu server for raspberry pi 400 will not unpack to SD
** Package changed: linux (Ubuntu) => 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/1909417 Title: ubuntu server for raspberry pi 400 will not unpack to SD Status in Ubuntu: Invalid Bug description: Ubuntu server 20.10 64 bit for raspberry pi 400 downloads fine, but will not unpack to 64GB SD card using Balena Etcher on windows. Similar desktop version will unpack just fine using exactly the same process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909417/+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 1899857] Update Released
The verification of the Stable Release Update for alsa-lib has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+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 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
I'm not comfortable with releasing this given the vagueness of the
verification in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879633/comments/51,
subsequently I'm setting the tags back to verification-needed.
** Tags removed: verification-done-focal
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1879633
Title:
Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Won't Fix
Status in linux-firmware source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification: oem-5.6]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k and all
its prerequisite drivers.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
[Fix]
Tag ath11k-qca6390-bringup-202011301608 from ath tree
(https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks
first stable milestone on the platform/device under development since
v5.6-rc1. Most of the commits under this tag, ~350 commits, have been
in vanilla kernel v5.10-rc4 except those starting from commit
065c9528cc50 ("ath11k: add 64bit check before reading msi high addr").
While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling
in these components are also pulled.
Besides, tx encapsulation
https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/
and a couple more inclusive of 6 GHz capability, BSS Color were also
pulled to satisfy API changes in mac80211/cfg80211.
[Test Case]
1. Install firmwares & boot from patched kernel,
2. ath11k should be now up and running. Check with
`sudo dmesg | grep ath11k`
While this is going to bring massive changes to the kernel, as well as
shared wireless stack that is not only used by ath11k but also many
others, prebuilt kernel/firmware packages were deployed on platforms
with and without ath11k for regression tests, and so far the results are
positive.
[Where problems could occur]
ath11k and its relying parts have never been enabled in oem-5.6, so
changes to them should have little effect on most platforms. For
platforms equip QCA6390, this will be the first time they're probed and
enabled, and as the driver is still under polishing, there can be
regressions, performance lost, power consumption increase at this
moment.
Changes to wireless stack could also be an issue as this introduces
interface changes to the API, so maybe DKMS packages in the wild will be
affected.
== SRU for U/OEM-5.10 ==
[SRU Justification: U/OEM-5.10]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k
driver.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
[Fix]
25 additional fixes in ath tree
(https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag
ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms,
and firmware updates from mainline are required.
[Test Case]
1. Install firmwares & boot from patched kernel,
2. ath11k should be now up and running. Check with
`sudo dmesg | grep ath11k`
[Where problems could occur]
There has been a lot patches landed in kernel since 5.7 devel cycle. The
last bits here has merge base with mainline at v5.10-rc4, and since then
only patches for ath11k itself has been committed.
== Original Bug Description ==
Qualcomm QCA6390 series not recognized due to the lack of ath11k
driver.
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1842 F pulseaudio
CasperMD5CheckResult: skip
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
[Kernel-packages] [Bug 1909866] Re: [Xubuntu 20.04] Distorted HDMI audio
** Package changed: ubuntu => 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/1909866 Title: [Xubuntu 20.04] Distorted HDMI audio Status in linux package in Ubuntu: Incomplete Bug description: After connecting a laptop to TV set via HDMI and redirecting the sound to HDMI the sound becomes distorted. It worked perfectly fine on Xubuntu 18.04. The issue occurred immediately after upgrading to Xubuntu 20.04. It usually works correctly when the movie started playing before the laptop was connected to TV-set. Right after connecting the laptop to the TV-set the movie continues to play with no sound issues. The sound issues occur when a movie is paused and resumed to play. The audio is distorted then. The 100% workaround is to change the refresh rate in Xubuntu's display settings to another value e.g. 60Hz. It works until I pause the movie again. Then I need to switch back to the previous refresh rate e.g. 50Hz and so on. In general I choose between 50 and 60 Hz in a round-robin fashion. The issue occurs when playing the movies via all available players e.g. mplayer, vlc or embedded in web browser. It never occurs when using the Laptop's display. I cannot observe any system log entries regarding this issue. OS: Xubuntu 20.04 Kernel: 5.4.0-58-generic #64-Ubuntu SMP Laptop: Dell Latitude E7440 TV-set: Panasonic TX-42AS500E # dmesg |grep -i audio [0.131266] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [8.527979] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [8.558111] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3226: line_outs=1 (0x16/0x0/0x0/0x0/0x0) type:line [8.558114] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [8.558116] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x15/0x0/0x0/0x0/0x0) [8.558117] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 [8.558118] snd_hda_codec_realtek hdaudioC1D0:inputs: [8.558120] snd_hda_codec_realtek hdaudioC1D0: Dock Mic=0x19 [8.558122] snd_hda_codec_realtek hdaudioC1D0: Headset Mic=0x1a [8.558124] snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12 [10557.458937] Modules linked in: ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep intel_rapl_msr pn544_mei binfmt_misc mei_phy pn544 snd_hda_codec_realtek snd_hda_codec_generic uvcvideo snd_hda_codec_hdmi snd_hda_intel hci snd_intel_dspcfg videobuf2_vmalloc snd_hda_codec nfc btusb videobuf2_memops btrtl snd_hda_core mei_hdcp videobuf2_v4l2 btbcm snd_hwdep videobuf2_common btintel videodev bluetooth mc snd_pcm ecdh_generic ecc snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_common iwlmvm x86_pkg_temp_thermal intel_powerclamp dell_laptop ledtrig_audio coretemp mac80211 kvm_intel snd_seq snd_seq_device libarc4 dell_smm_hwmon snd_timer kvm iwlwifi snd rapl intel_cstate input_leds dell_wmi dell_smbios joydev dcdbas sparse_keymap wmi_bmof dell_wmi_descriptor serio_raw mei_me cfg80211 mei soundcore mac_hid dell_rbtn dell_smo8800 sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea crct10dif_pclmul sysfillrect crc32_pclmul [10557.563972] Modules linked in: ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep intel_rapl_msr pn544_mei binfmt_misc mei_phy pn544 snd_hda_codec_realtek snd_hda_codec_generic uvcvideo snd_hda_codec_hdmi snd_hda_intel hci snd_intel_dspcfg videobuf2_vmalloc snd_hda_codec nfc btusb videobuf2_memops btrtl snd_hda_core mei_hdcp videobuf2_v4l2 btbcm snd_hwdep videobuf2_common btintel videodev bluetooth mc snd_pcm ecdh_generic ecc snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_common iwlmvm x86_pkg_temp_thermal intel_powerclamp dell_laptop ledtrig_audio coretemp mac80211 kvm_intel snd_seq snd_seq_device libarc4 dell_smm_hwmon snd_timer kvm iwlwifi snd rapl intel_cstate input_leds dell_wmi dell_smbios joydev dcdbas sparse_keymap wmi_bmof dell_wmi_descriptor serio_raw mei_me cfg80211 mei soundcore mac_hid dell_rbtn dell_smo8800 sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea crct10dif_pclmul sysfillrect crc32_pclmul # dmesg |grep -i hdmi [0.131266] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [8.543890] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card0/input10 [8.543955] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.0/sound/card0/input11 [8.544014] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/sound/card0/input12 [8.544069] input: HDA Intel HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.0/sound/card0/input13 [8.544133] input: HDA Intel HDMI HDMI/DP,pcm=10 as
[Kernel-packages] [Bug 1909799] Re: Raspberry Pi 400 won't power down
** Package changed: ubuntu => 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/1909799 Title: Raspberry Pi 400 won't power down Status in linux package in Ubuntu: New Bug description: The computer won't power down. Shutting down process stops at: Reached target: Power-off After waiting a while some messages/errors are being displayed. Screenshot attached. I have to disconnect power cable. Reboot works properly. I'm using Ubuntu Mate 20.10, on Raspberry Pi 400. Everything updated. Linux pi-desktop 5.8.0-1010-raspi #13-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909799/+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 1908081] Re: [linux-image-5.8.0-33.generic] Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7)
** Package changed: ubuntu => 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/1908081 Title: [linux-image-5.8.0-33.generic] Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7) Status in linux package in Ubuntu: New Bug description: Hi, kernel: Linux ideapad 5.8.0-33-generic #36-Ubuntu SMP Wed Dec 9 09:14:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Version of Ubuntu: Ubuntu 20.10 up to date at 14 dec 2020 The kernel linux-image-5.8.0-33.generic show a panic on boot. dic 12 11:48:11 ideapad kernel: amdgpu :03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 dic 12 11:48:11 ideapad kernel: [ cut here ] dic 12 11:48:11 ideapad kernel: Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7) dic 12 11:48:11 ideapad kernel: WARNING: CPU: 0 PID: 169 at drivers/gpu/drm/drm_mode_config.c:616 drm_mode_config_validate+0xdb/0x100 [drm] dic 12 11:48:11 ideapad kernel: Modules linked in: hid_rmi rmi_core videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc hi> dic 12 11:48:11 ideapad kernel: CPU: 0 PID: 169 Comm: systemd-udevd Tainted: G O 5.8.0-33-generic #36-Ubuntu dic 12 11:48:11 ideapad kernel: Hardware name: LENOVO 81LW/LNVNB161216, BIOS ARCN34WW 06/03/2020 dic 12 11:48:11 ideapad kernel: RIP: 0010:drm_mode_config_validate+0xdb/0x100 [drm] dic 12 11:48:11 ideapad kernel: Code: 39 d6 75 e5 41 8b 4d 48 41 85 c8 74 09 44 89 c0 f7 d0 85 c8 74 16 49 8b 55 38 41 8b 75 18 48 c7 c7 f0 c8 30 c0 > dic 12 11:48:11 ideapad kernel: RSP: 0018:b17280363aa0 EFLAGS: 00010286 dic 12 11:48:11 ideapad kernel: RAX: RBX: 99c5360192d8 RCX: 0388 dic 12 11:48:11 ideapad kernel: RDX: 0001 RSI: 0082 RDI: 0246 dic 12 11:48:11 ideapad kernel: RBP: b17280363ab8 R08: R09: 0388 dic 12 11:48:11 ideapad kernel: R10: 00aa R11: 99cb9440 R12: 0001 dic 12 11:48:11 ideapad kernel: R13: 99c525d88400 R14: 00020016 R15: 99c536019000 dic 12 11:48:11 ideapad kernel: FS: 7fbbc9f868c0() GS:99c538a0() knlGS: dic 12 11:48:11 ideapad kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) dic 12 11:48:11 ideapad kernel: CS: 0010 DS: ES: CR0: 80050033 dic 12 11:48:11 ideapad kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) dic 12 11:48:11 ideapad kernel: CR2: 7fbbc9f6c154 CR3: 0001a61ee000 CR4: 003406f0 dic 12 11:48:11 ideapad kernel: Call Trace: dic 12 11:48:11 ideapad kernel: drm_dev_register+0x16c/0x1c0 [drm] dic 12 11:48:11 ideapad kernel: amdgpu_pci_probe+0x107/0x180 [amdgpu] dic 12 11:48:11 ideapad kernel: usb 3-2: New USB device found, idVendor=0bda, idProduct=c024, bcdDevice= 1.10 dic 12 11:48:11 ideapad kernel: local_pci_probe+0x48/0x80 dic 12 11:48:11 ideapad kernel: ata2.00: ATAPI: PLDSDVD-RW DA8AESH, XL6M, max UDMA/133 dic 12 11:48:11 ideapad kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 dic 12 11:48:11 ideapad kernel: usb 3-2: Product: Bluetooth Radio dic 12 11:48:11 ideapad kernel: usb 3-2: Manufacturer: Realtek dic 12 11:48:11 ideapad kernel: usb 3-2: SerialNumber: 00e04c01 dic 12 11:48:11 ideapad kernel: pci_call_probe+0x53/0xe0 dic 12 11:48:11 ideapad kernel: pci_device_probe+0xad/0xf0 dic 12 11:48:11 ideapad kernel: really_probe+0x177/0x430 dic 12 11:48:11 ideapad kernel: driver_probe_device+0xe9/0x160 dic 12 11:48:11 ideapad kernel: device_driver_attach+0xab/0xb0 dic 12 11:48:11 ideapad kernel: __driver_attach+0x8f/0x150 dic 12 11:48:11 ideapad kernel: ? device_driver_attach+0xb0/0xb0 dic 12 11:48:11 ideapad kernel: bus_for_each_dev+0x7e/0xc0 dic 12 11:48:11 ideapad kernel: driver_attach+0x1e/0x20 dic 12 11:48:11 ideapad kernel: bus_add_driver+0x135/0x1f0 dic 12 11:48:11 ideapad kernel: driver_register+0x91/0xf0 dic 12 11:48:11 ideapad kernel: __pci_register_driver+0x54/0x60 dic 12 11:48:11 ideapad kernel: amdgpu_init+0x83/0x1000 [amdgpu] dic 12 11:48:11 ideapad kernel: ata1.00: ATA-10: WDC WD10SPZX-24Z10, 04.01A04, max UDMA/133 dic 12 11:48:11 ideapad kernel: ? 0xc0a6a000 dic 12 11:48:11 ideapad kernel: do_one_initcall+0x4a/0x200 dic 12 11:48:11 ideapad kernel: ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA dic 12 11:48:11 ideapad kernel: ? _cond_resched+0x1a/0x50 dic 12 11:48:11 ideapad kernel: ata1.00: configured for UDMA/133 dic 12 11:48:11 ideapad kernel: ? kmem_cache_alloc_trace+0x1a1/0x240 dic 12 11:48:11 ideapad kernel: ata2.00: configured for UDMA/133 dic 12 11:48:11 ideapad kernel: scsi 0:0:0:0: Direct-Access
[Kernel-packages] [Bug 1908048] Re: mircoSD could not operate
** Package changed: ubuntu => 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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+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 1907493] Re: wifi network keeps disconnecting
** Package changed: ubuntu => 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/1907493 Title: wifi network keeps disconnecting Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 with the latest updates on a Thinkpad X220. Since about a week I keep having network disconnects. I am using an Intel Corporation Centrino Advanced-N 6205 wifi chip. Before it's been working great. There seem to be others with this recent problem. https://askubuntu.com/questions/1298278/i-keep-getting-disconnected $dmesg shows: [35764.191444] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [35764.207135] wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised by 5c:49:79:33:f5:69 [35770.664591] e1000e: enp0s25 NIC Link is Down [35823.702523] wlp3s0: disassociated from 5c:49:79:33:f5:69 (Reason: 33=DISASSOC_QAP_NO_BANDWIDTH) [35823.949141] wlp3s0: authenticate with 5c:49:79:33:f5:6a [35823.952112] wlp3s0: send auth to 5c:49:79:33:f5:6a (try 1/3) [35824.027366] wlp3s0: authenticated [35824.028058] wlp3s0: associate with 5c:49:79:33:f5:6a (try 1/3) [35824.031316] wlp3s0: RX AssocResp from 5c:49:79:33:f5:6a (capab=0x1511 status=0 aid=3) [35824.049972] wlp3s0: associated [35824.051644] wlp3s0: deauthenticating from 5c:49:79:33:f5:6a by local choice (Reason: 1=UNSPECIFIED) [35827.875982] wlp3s0: authenticate with 5c:49:79:33:f5:69 [35827.883980] wlp3s0: send auth to 5c:49:79:33:f5:69 (try 1/3) [35827.890394] wlp3s0: 5c:49:79:33:f5:69 denied authentication (status 34) [35828.966804] wlp3s0: authenticate with 5c:49:79:33:f5:6a [35828.971132] wlp3s0: send auth to 5c:49:79:33:f5:6a (try 1/3) [35829.043823] wlp3s0: authenticated [35829.044820] wlp3s0: associate with 5c:49:79:33:f5:6a (try 1/3) [35829.047162] wlp3s0: RX AssocResp from 5c:49:79:33:f5:6a (capab=0x1511 status=0 aid=3) [35829.065508] wlp3s0: associated [35829.144604] wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 5c:49:79:33:f5:6a [35901.739236] wlp3s0: disconnect from AP 5c:49:79:33:f5:6a for new auth to 5c:49:79:33:f5:69 [35901.758760] wlp3s0: authenticate with 5c:49:79:33:f5:69 [35901.762063] wlp3s0: send auth to 5c:49:79:33:f5:69 (try 1/3) [35901.765779] wlp3s0: authenticated [35901.766059] wlp3s0: waiting for beacon from 5c:49:79:33:f5:69 [35901.831428] wlp3s0: associate with 5c:49:79:33:f5:69 (try 1/3) [35901.837432] wlp3s0: RX ReassocResp from 5c:49:79:33:f5:69 (capab=0x1431 status=0 aid=8) [35901.857282] wlp3s0: associated [35901.859310] wlp3s0: deauthenticating from 5c:49:79:33:f5:69 by local choice (Reason: 1=UNSPECIFIED) $journalctl --follow showed this: Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: Associated with 5c:49:79:33:f5:69 Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: l2_packet_send - sendto: No buffer space available Dez 09 20:29:05 meschi-ThinkPad-X220 kernel: wlp3s0: deauthenticating from 5c:49:79:33:f5:69 by local choice (Reason: 1=UNSPECIFIED) Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=5c:49:79:33:f5:69 reason=1 locally_generated=1 Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wifi-name" auth_failures=1 duration=10 reason=WRONG_KEY Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Dez 09 20:29:05 meschi-ThinkPad-X220 NetworkManager[141586]: [1607542145.0780] device (wlp3s0): supplicant interface state: associating -> 4-way handshake Dez 09 20:29:05 meschi-ThinkPad-X220 NetworkManager[141586]: [1607542145.0781] sup-iface[0x560dbca5e1e0,wlp3s0]: connection disconnected (reason -1) Dez 09 20:29:05 meschi-ThinkPad-X220 NetworkManager[141586]: [1607542145.0833] device (wlp3s0): supplicant interface state: 4-way handshake -> disconnected Dez 09 20:29:05 meschi-ThinkPad-X220 NetworkManager[141586]: [1607542145.0849] device (wlp3s0): Activation: (wifi) disconnected during association, asking for new key Dez 09 20:29:05 meschi-ThinkPad-X220 NetworkManager[141586]: [1607542145.0851] device (wlp3s0): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907493/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1906279] Re: amd64: cma_alloc errors at boot
** Package changed: ubuntu => 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/1906279 Title: amd64: cma_alloc errors at boot Status in linux package in Ubuntu: Incomplete Bug description: I am a novice user attempting to get an RX 6800-XT GPU working on Ubuntu 20.04. I'm using Ubuntu 20.04 because it's recommended by the official AMD driver installer. The RX 6800-XT requires kernel 5.10 or later. I have updated to kernel 5.10.0-rc6 using the mainline kernel updater GUI. When booting into 5.10.0-rc6, I see about two dozen lines like > cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 The closest related bug I found was https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753 The boot hangs after those messages are printed. I also tried kernel 5.9.10 and receive the same error. However, if I boot into kernel recovery mode, and then select "continue normal boot", then the system seems to boot normally. My hardware AMD Ryzen 9 3900X 3.8 GHz 12-Core Processor AMD RX 6800-XT GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906279/+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 1905724] Re: Compete system freeze with AMD GPU
** Package changed: ubuntu => 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/1905724 Title: Compete system freeze with AMD GPU Status in linux package in Ubuntu: New Bug description: So, several times a week i experience a complete freeze of the system, but in rather strange way. Spotify keeps playing, but screen is frozen and even NumLock doesnt work. Here are the relevant lines from syslog: Nov 26 13:59:43 home kernel: [13624.224831] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Nov 26 13:59:43 home kernel: [13624.224911] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Nov 26 13:59:48 home kernel: [13624.224980] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Nov 26 13:59:48 home kernel: [13629.344808] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=954733, emitted seq=954735 Nov 26 13:59:48 home kernel: [13629.344870] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process chrome pid 2341 thread chrome:cs0 pid 2356 Nov 26 13:59:48 home kernel: [13629.344872] [drm] GPU recovery disabled. Nov 26 13:59:51 home kernel: [13632.416809] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Nov 26 13:59:51 home kernel: [13632.416883] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Nov 26 13:59:54 home plank.desktop[2060]: --2020-11-26 13:59:54-- https://clients2.google.com/cr/report Nov 26 13:59:54 home plank.desktop[2060]: Resolving clients2.google.com (clients2.google.com)... 216.58.211.142, 2a00:1450:400f:808::200e Nov 26 13:59:54 home plank.desktop[2060]: Connecting to clients2.google.com (clients2.google.com)|216.58.211.142|:443... connected. Nov 26 13:59:55 home plank.desktop[2060]: HTTP request sent, awaiting response... 200 OK Nov 26 13:59:55 home plank.desktop[2060]: Length: unspecified [text/plain] Nov 26 13:59:55 home plank.desktop[2060]: Saving to: ‘/dev/fd/4’ Nov 26 13:59:55 home plank.desktop[2060]: 0K Nov 26 13:59:55 home plank.desktop[2060]: Crash dump id: f034d136a81c3341 Nov 26 13:59:55 home plank.desktop[2060]: 3,45M=0s Nov 26 13:59:55 home plank.desktop[2060]: 2020-11-26 13:59:55 (3,45 MB/s) - ‘/dev/fd/4’ saved [16] Nov 26 14:00:04 home kernel: [13632.416960] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Nov 26 14:00:04 home kernel: [13645.984782] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=954733, emitted seq=954735 Nov 26 14:00:04 home kernel: [13645.984843] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Nov 26 14:00:04 home kernel: [13645.984845] [drm] GPU recovery disabled. Nov 26 14:00:05 home kernel: [13646.391163] GpuWatchdog[28302]: segfault at 0 ip 7f5afd863c4f sp 7f5af587a1c0 error 6 in libcef.so[7f5af97be000+6dbb000] Nov 26 14:00:05 home kernel: [13646.391172] Code: 89 de e8 44 c2 9f fe 80 7d cf 00 79 09 48 8b 7d b8 e8 15 31 67 fe 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 f1 ae f5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e Nov 26 14:00:15 home kernel: [13656.480730] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=954733, emitted seq=954735 Nov 26 14:00:15 home kernel: [13656.480791] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Nov 26 14:00:15 home kernel: [13656.480793] [drm] GPU recovery disabled. Usually this happens when I browse Google Maps. System is: AMD Ryzen 7 3700X 8-Core Processor MSI Radeon 5700XT MSI B450M Mortar MAX. version.log: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 lsb_release -rd Description: elementary OS 5.1.7 Hera Release: 5.1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905724/+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 1904455] Re: impossible de créer « /lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new » (pendant le traitement de « ./lib/firmware/brcm/BCM-0bb4-0306.hcd »): Opération non permise
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1904455 Title: impossible de créer « /lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new » (pendant le traitement de « ./lib/firmware/brcm/BCM-0bb4-0306.hcd »): Opération non permise Status in linux-firmware package in Ubuntu: New Bug description: impossible de créer « /lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new » (pendant le traitement de « ./lib/firmware/brcm/BCM-0bb4-0306.hcd »): Opération non permise ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.13 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Nov 16 15:15:26 2020 InstallationDate: Installed on 2020-11-09 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all RebootRequiredPkgs: linux-image-5.8.0-29-generic linux-base SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to groovy on 2020-11-16 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1904455/+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 1904864] Re: iwlwifi crashes, cannot use wifi
** Package changed: ubuntu-release-upgrader (Ubuntu) => 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/1904864 Title: iwlwifi crashes, cannot use wifi Status in linux package in Ubuntu: Incomplete Bug description: Unable to use Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) on Ubuntu 20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.28 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 15:28:49 2020 InstallationDate: Installed on 2020-11-01 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-11-08 18:09:54.611428 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904864/+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 1905074] Re: After installing kernel 5.8.0-29, my Wacom One tablet is not recognized
** Package changed: ubuntu => 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/1905074 Title: After installing kernel 5.8.0-29, my Wacom One tablet is not recognized Status in linux package in Ubuntu: New Bug description: The tablet does not work when plugged in, and in Settings -> Mouse and Touchpad the tablet is not shown in the list of devices. (The tablet works and is included in the device list when I revert to 5.8.0-28.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905074/+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 1904860] Re: QCA9377 802.11ac Wireless Network Adapter-Network unclaimed on every ubuntu os
** Package changed: ubuntu => 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/1904860 Title: QCA9377 802.11ac Wireless Network Adapter-Network unclaimed on every ubuntu os Status in linux package in Ubuntu: New Bug description: 4 months ago,I installed ubuntu on my lenovo E41-25 notebook. Working damn fine going good. recently i updated my system via `sudo apt update && sudo apt upgrade`. Thats all i do. Now,my wifi adapter not working properly. harish@harish$ sudo dmesg | grep ath10k [ 12.347183] ath10k_pci :02:00.0: failed to iomap BAR0 [ 12.347239] ath10k_pci :02:00.0: failed to claim device: -5 [ 12.347355] ath10k_pci: probe of :02:00.0 failed with error -5 harish@harish$ lshw -c network WARNING: you should run this program as super-user. *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: enp1s0 version: 15 serial: 9c:5a:44:44:f4:41 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:30 ioport:3000(size=256) memory:f0404000-f0404fff memory:f040-f0403fff *-network UNCLAIMED description: Network controller product: QCA9377 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 version: 31 width: 64 bits clock: 33MHz capabilities: cap_list configuration: latency=0 *-network description: Ethernet interface physical id: 1 bus info: usb@2:3 logical name: usb0 serial: ca:74:69:53:09:2a capabilities: ethernet physical configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.225 link=yes multicast=yes harish@harish$ lsmod Module Size Used by rndis_host 20480 0 cdc_ether 20480 1 rndis_host usbnet 45056 2 rndis_host,cdc_ether mii20480 1 usbnet cdc_acm40960 0 rfcomm 81920 4 cmac 16384 2 algif_hash 16384 1 algif_skcipher 16384 1 af_alg 24576 6 algif_hash,algif_skcipher bnep 24576 2 nls_iso8859_1 16384 1 edac_mce_amd 32768 0 kvm_amd98304 0 ccp86016 1 kvm_amd kvm 663552 1 kvm_amd crct10dif_pclmul 16384 1 ghash_clmulni_intel16384 0 snd_hda_codec_conexant28672 1 uvcvideo 98304 0 snd_hda_codec_generic81920 1 snd_hda_codec_conexant aesni_intel 372736 3 amdgpu 4579328 21 ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_conexant videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc snd_hda_codec_hdmi 61440 1 crypto_simd16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel snd_hda_intel 53248 4 snd_intel_dspcfg 24576 1 snd_hda_intel snd_hda_codec 135168 4 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel videobuf2_v4l2 24576 1 uvcvideo snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec videobuf2_common 49152 2 videobuf2_v4l2,uvcvideo videodev 225280 3 videobuf2_v4l2,uvcvideo,videobuf2_common glue_helper16384 1 aesni_intel amd_iommu_v2 20480 1 amdgpu snd_hwdep 20480 1 snd_hda_codec mc 53248 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common snd_pcm 106496 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core btusb 57344 0 btrtl 24576 1 btusb ath10k_pci 49152 0 btbcm 16384 1 btusb btintel24576 1 btusb snd_seq_midi 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi ath10k_core 475136 1 ath10k_pci bluetooth 548864 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm ath36864 1 ath10k_core ecdh_generic 16384 1 bluetooth
[Kernel-packages] [Bug 1904566] Re: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture)
** Also 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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) Status in linux package in Ubuntu: New Status in linux-hwe-5.4 package in Ubuntu: New Bug description: Hi, it isn't easy to describe but i will try and give you all information which seem to interfer with the bug .. Sorry, my system is running with german language output. First my environment : Description: Ubuntu 18.04.5 LTS Release: 18.04 Kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa: $ apt list --installed|grep -i alsa alsa-base/bionic,bionic,now 1.0.25+dfsg-0ubuntu5 all [installiert] alsa-utils/bionic,now 1.1.3-1ubuntu1 amd64 [installiert] libsox-fmt-alsa/bionic-updates,bionic-security,now 14.4.2-3ubuntu0.18.04.1 amd64 [Installiert,automatisch] libzita-alsa-pcmi0/bionic,now 0.2.0-4ubuntu2 amd64 [Installiert,automatisch] jackd: apt list --installed|grep -i jackd jackd/bionic,bionic,now 5 all [Installiert,automatisch] jackd2/bionic,now 1.9.12~dfsg-2 amd64 [Installiert,automatisch] libjack-jackd2-0/bionic,now 1.9.12~dfsg-2 amd64 [Installiert,automatisch] libjack-jackd2-dev/bionic,now 1.9.12~dfsg-2 amd64 [installiert] My interface (Omega) : $ aplay -l Liste der Hardware-Geräte (PLAYBACK) Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC887-VD Analog [ALC887-VD Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 1: ALC887-VD Digital [ALC887-VD Digital] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 7: HDMI 1 [HDMI 1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: Omega [Lexicon Omega], Gerät 0: USB Audio [USB Audio] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: Omega [Lexicon Omega], Gerät 1: USB Audio [USB Audio #1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 The problem: I try to record some audio, using the usb-audio-interface Lexicon Omega. This interface has 4 capture channels, but all efforts to get them working/configured failed. Here is the commandline wich is working (but only two capture-channels !) $ /usr/bin/jackd -T -ndefault -dalsa -r4800 -p256 -n3 H -D -d hw:Omega -i2 -o2 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio1 creating alsa driver ... hw:Omega|hw:Omega|256|3|4800|2|2|nomon|swmeter|-|32bit configuring for 4800Hz, period = 256 frames (53.3 ms), buffer = 3 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 3 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 3 periods for playback The same with 4 capture-channels fails: $ /usr/bin/jackd -T -ndefault -dalsa -r4800 -p256 -n3 H -D -d hw:Omega -i4 -o2 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio1 creating alsa driver ... hw:Omega|hw:Omega|256|3|4800|4|2|nomon|swmeter|-|32bit configuring for 4800Hz, period = 256 frames (53.3 ms), buffer = 3 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: cannot set channel count to 4 for capture ALSA: cannot configure capture channel JackTemporaryException : now quits... Released audio card Audio1 audio_reservation_finish Cannot initialize driver JackServer::Open failed with -1 Failed to open server So, one could say the interface is broken, but i tested on an older system (Ubuntustudio 16.04): $ uname -a 4.10.0-42-lowlatency #46~16.04.1-Ubuntu SMP PREEMPT Mon Dec 4 17:13:40 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ apt list --installed|grep -i alsa alsa-base/bionic,bionic,now
[Kernel-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
I tested groovy again, but this time I installed apport and python3-apport in one step instead of two and it passed without needing to reboot. The verification on Focal also passed with no rebooting required. bdmurray@clean-focal-amd64:~$ apt list apport Listing... Done apport/focal-proposed,focal-proposed,now 2.20.11-0ubuntu27.13 all [installed] N: There are 2 additional versions. Please use the '-a' switch to see them. bdmurray@clean-focal-amd64:~$ sudo pkill -11 upowerd bdmurray@clean-focal-amd64:~$ ls /var/crash/ _usr_lib_upower_upowerd.0.crash ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Fix Committed Status in bluez source package in Focal: Invalid Status in apport source package in Groovy: Fix Committed Status in bluez source package in Groovy: Invalid Status in apport source package in Hirsute: Fix Released Status in bluez source package in Hirsute: Invalid Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
I had to reboot for the verification to pass, but it did. bdmurray@clean-groovy-amd64:~$ apt list apport Listing... Done apport/groovy-proposed,groovy-proposed,now 2.20.11-0ubuntu50.2 all [installed,automatic] N: There are 2 additional versions. Please use the '-a' switch to see them. bdmurray@clean-groovy-amd64:~$ sudo pkill -11 upowerd bdmurray@clean-groovy-amd64:~$ ls /var/crash/ _usr_libexec_upowerd.0.crash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Fix Committed Status in bluez source package in Focal: Invalid Status in apport source package in Groovy: Fix Committed Status in bluez source package in Groovy: Invalid Status in apport source package in Hirsute: Fix Released Status in bluez source package in Hirsute: Invalid Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Hello Dave, or anyone else affected, Accepted bluez into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.55-0ubuntu1.1 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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: bluez (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Description changed: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails - * sudo add-apt-repository ppa:waveform/pi-bluetooth + * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab - * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly + * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Committed Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on
[Kernel-packages] [Bug 1904480] Re: RTL8822CE Realtek Wi-Fi dropping connection
** Package changed: ubuntu => 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/1904480 Title: RTL8822CE Realtek Wi-Fi dropping connection Status in linux package in Ubuntu: New Bug description: Wifi is still connected but it just stops working, this can be resolved by disconnecting or putting wifi on airplane mode and turning it back again. A few cases this does not work and the Wifi stops working and a system restart is needed. This is happening on Ubuntu 20.10 x64 Below the info for the wifi card: description: Wireless interface product: RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: 8c:c8:4b:95:0f:8b width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtw_8822ce driverversion=5.8.0-29-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:79 ioport:2000(size=256) memory:fc70-fc70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904480/+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 1902701] Re: zfs-linux 0.8.3-1ubuntu12.4 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1
Hello Stefan, or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.5 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: zfs-linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1902701 Title: zfs-linux 0.8.3-1ubuntu12.4 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1 Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Focal: Fix Committed Bug description: [SRU Justification] Impact: When attempting to compile the zfs-dkms module on a 5.8 kernel the module fails to properly configure the build. The kernel driver part of zfs-linux is only prepared to handle the kernels it released with. For Ubuntu kernels the zfs module is build based on the zfs-dkms that is current for the series the kernel originates from (so Groovy for 5.8). And this should be the encouraged way to do this. Fix: Add a limitation to the dkms package to only build for supported kernels. This causes the whole build/install to be skipped on 5.8 rather than to fail. Testcase: dkms install runs for 5.4 and 5.8 in Focal. For the 5.8 kernel this should result in: Building initial module for 5.8.0-25-generic Error! The /var/lib/dkms/zfs/0.8.3/5.8.0-25-generic/x86_64/dkms.conf for module zfs includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped. Regression Potential: Since the module fails to compile for the newer kernel there should be nothing that can regress. --- Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/z/zfs-linux/20201016_104632_e52aa@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/z/zfs-linux/20201016_144759_7735c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/z/zfs-linux/20201016_111820_ceeb8@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/z/zfs-linux/20201016_082202_1adb7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902701/+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 1903309] Re: wifi not working properly after upgrade to 20.04
** Package changed: ubuntu => 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/1903309 Title: wifi not working properly after upgrade to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Wifi keeps turning off! On 18.04 there was no problem with RTL8821CE and wifi worked fine and stable. network description: Wireless interface product: RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: a4:fc:77:79:6a:05 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtl8821ce ip=192.168.1.8 latency=0 multicast=yes wireless=IEEE 802.11bgn resources: irq:130 ioport:3000(size=256) memory:a110-a110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903309/+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 1903217] Re: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope
** Package changed: ubuntu => 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/1903217 Title: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope Status in linux package in Ubuntu: New Bug description: Lenovo Yoga Chromebook C630 is missing support in Ubuntu (and Fedora, Manjaro, Gallium etc) for sound, microphone, touchscreen and gyroscope. I asked on the kernel bug tracker and they said I should come to the distro bug tracker to report it. My DMESG outputs are available in the kernel bug here https://bugzilla.kernel.org/show_bug.cgi?id=207509 Note: Lenovo confusingly produces at least two laptops called C630, one of which is this one, an Intel based Chromebook, the other is an ARM based laptop, sometimes called the C630 WOS, which already has bug reports for lack of support but is a completely different laptop. Best To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217/+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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Also affects: apport (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Groovy) Status: New => Triaged ** Changed in: apport (Ubuntu Groovy) Importance: Undecided => High ** Changed in: apport (Ubuntu Focal) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: In Progress Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Triaged Status in bluez source package in Focal: Invalid Status in apport source package in Groovy: Triaged Status in bluez source package in Groovy: New Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Description changed: + [Impact] + apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. + + [Test Case] + On an Ubuntu desktop system perform the following step + 1) sudo pkill -11 upowerd + + With the current version of apport there will not be a crash file for + upowerd in /var/crash/. With the version of apport in -proposed there + will be a crash file for upowerd in /var/crash/. + + [Regression Potential] + In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. + + [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: In Progress Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Confirmed Status in bluez source package in Focal: Invalid Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
** Changed in: grub2 (Ubuntu Groovy) Status: Confirmed => Fix Released ** Changed in: grub2 (Ubuntu) Status: Confirmed => 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/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor Status in grub2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in grub2 source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in grub2 source package in Groovy: Fix Released Status in linux source package in Groovy: Invalid Bug description: I'm running focal devel and the latest kernel (see proc version below) Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version 9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 Dock Monitor is supported very well with multiple usb devices plugged on the monitor. However on reboot I face a black screen with no ability to enter my FDE password. Both my Laptop screen and the attached usb-c display nothing I have to hard power off and reboot without the USB-C monitor plugged in. Otherwise A reboot cycle with the usb-c unplugged works perfectly. Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic without success. I would be happy to provide much more debugging information. I will attach then to the launchpad Bug # --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mclemenceau 2988 F pulseaudio /dev/snd/controlC0: mclemenceau 2988 F pulseaudio /dev/snd/controlC1: mclemenceau 2988 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-05 (64 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-ae0xx NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.41 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2TV18AS#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1866852/+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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: In Progress Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Confirmed Status in bluez source package in Focal: Invalid Bug description: bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
** Package changed: ubuntu => 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/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902457/+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 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
Hello fossfreedom, or anyone else affected, Accepted alsa-lib into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.2-2.1ubuntu2.1 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. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: Invalid Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this results in the failure on setting the init mixer values for HDA sound card, and users experience the mute of audio after installing the 20.10. [Fix] Backport a patch from the latest alsa-lib (v1.2.3+) [Test] Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is muted. Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is not muted. [Regression Potential] This could make the ucm audio fail to initialize, but this possibility is very low, since this patch is from upstream, and I tested on a ucm based machine, the audio is good. On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Hello Markus, or anyone else affected, Accepted libvirt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.5 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: libvirt (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Hello Ryan, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 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: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags removed: verification-done verification-done-focal
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861941
Title:
bcache by-uuid links disappear after mounting bcache0
Status in bcache-tools package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in bcache-tools source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Won't Fix
Status in bcache-tools source package in Focal:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Bug description:
SRU TEAM: The last 2 commits show a summary for the merges/changes
I added some specific (to Bionic) notes in the template.
Thanks!
[Impact]
* bcache-tools udev created symlinks might disappear when other udev
events are processed for the same devices.
* after mkfs.XXX in /dev/bcacheY you might face a condition where
/dev/bcache/by-{uuid,label}/zzz symlinks are gone.
* /dev/bcache/by-{uuid,label}/ symlinks are important so bcache
devices can be addressed by their UUIDs and not the ordering they were
assembled (MAAS depends on this feature, for example).
* it was also discussed in this bug that systemd-udev should *not*
populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
backing devices. this was turned into a discussion whether blkid
should report those or not, and this discussion "died" after sometime.
This last item is what the systemd update is all about: to disallow
/dev/disk/by-XXX/ creation for bcache backing devices (a simple
change that will reduce end users confusion).
[Test Case]
* The reproducer script is here:
https://paste.ubuntu.com/p/37KGy2Smnp/
* Bionic can't reproduce the issue with the 18.04 kernel, nor with
the HWE kernel. Nevertheless, it is preferable that Bionic also do the
same thing: to read bcache superblock and feed environment for
/dev/bcache/by-{uuid,label} symlinks creation.
[Regression Potential]
* We are not depending on bcache device udev events any more when
creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
depending on a wrapper script that heads bcache device superblock. If
there is a bug in this wrapper the symlinks wouldn't work.
* Previously we were thinking in asking the kernel team to remove the
bcache udev event delta script they've done for previous case (LP:
#1729145). It creates the udev events that were being read and filling
the symlinks. We decided not to remove those (just from Groovy and on)
so we don't need to worry on Breaks/Conflicts in between the kernel
package and bcache-tools (and udev)).
* Long story short: kernel will continue to emit bcache udev events
as it did previously but now those events won't be used by anything -
after installing this SRU - because udev wrapper script is doing this
job (and doing it properly)
[Other Info]
- Original Description:
1.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
2.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
root@ubuntu:~# apt-cache policy linux-image-virtual
linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
*** 5.4.0.12.15 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Hello Christian, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 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: systemd (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 linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in util-linux source package in Focal: Confirmed Bug description: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/)
[Kernel-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
** Tags added: rls-gg-incoming -- 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/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Status in pi-bluetooth package in Ubuntu: Confirmed Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+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 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
** Changed in: ubuntu-release-notes Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: Invalid Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this results in the failure on setting the init mixer values for HDA sound card, and users experience the mute of audio after installing the 20.10. [Fix] Backport a patch from the latest alsa-lib (v1.2.3+) [Test] Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is muted. Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is not muted. [Regression Potential] This could make the ucm audio fail to initialize, but this possibility is very low, since this patch is from upstream, and I tested on a ucm based machine, the audio is good. On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1893205] Re: linux-generic-hwe-20.04 transitional to linux-generic does not exist in groovy
The dependencies for linux-generic-hwe-20.04 have changed but this is not a transitional package. So is this fixed? $ apt-cache show linux-generic-hwe-20.04 Package: linux-generic-hwe-20.04 Architecture: amd64 Version: 5.8.0.23.28 Priority: optional Section: kernel Source: linux-meta Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 18 Depends: linux-image-generic-hwe-20.04 (= 5.8.0.23.28), linux-headers-generic-hwe-20.04 (= 5.8.0.23.28) Filename: pool/main/l/linux-meta/linux-generic-hwe-20.04_5.8.0.23.28_amd64.deb Size: 1884 MD5sum: a4c2e89e003330f287e9664df91e7896 SHA1: 06034c36fd355f713b364c02c230ac6a1524e145 SHA256: ca4aa95a8759781451adafca8e7de790aeb8744460b711e673201a588d4d1f78 SHA512: 551f2bca92163ad9009bcfa2f9a025f64ad5f3492b80643ee3d9f96c711209c445e2d55f5a18771dae58cae4fb5188752e76390ed4738fc20f4e87afaaac1e59 Description-en: Complete Generic Linux kernel and headers This package will always depend on the latest complete generic Linux kernel and headers. Description-md5: 000d0a6187a93215f75bba542cc6df27 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1893205 Title: linux-generic-hwe-20.04 transitional to linux-generic does not exist in groovy Status in linux-meta package in Ubuntu: Confirmed Bug description: linux-generic-hwe-20.04 transitional to linux-generic does not exist in groovy, instead it still points at 5.4 kernel. Please create transitional meta from linux-generic-hwe-20.04 to linux- generic. Otherwise machines that installed Ubuntu Desktop focal, then upgrade to groovy, remain on v5.4 kernel, instead of getting v5.8 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1893205/+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 1899519] Re: booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded
** Also affects: linux (Ubuntu Groovy) Importance: High Status: Confirmed ** Changed in: linux (Ubuntu Groovy) Milestone: ubuntu-20.10 => groovy-updates ** Changed in: ubuntu-release-notes Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899519 Title: booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded Status in Release Notes for Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: [Impact] Groovy armhf LPAE kernel fails to load kmods (and thus fail to boot). [Fix] Enable CONFIG_ARM_MODULE_PLTS for armhf [Regression potential] Quoting the arch/arm/Kconfig: "This [option] allows modules to be allocated in the generic vmalloc area after the dedicated module memory area has been exhausted. The modules will use slightly more memory, but after rounding up to page size, the actual memory footprint is usually the same. Disabling this is usually safe for small single-platform configurations. " --- qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [0.00] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym '__stack_chk_fail': relocation 28 out of range (0xbf00b404 -> 0xc10a1dd8) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 41.265330] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) (initramfs) cat /proc/modules (initramfs) modprobe virtio_blk [ 121.814904] virtio_blk: section 4 reloc 3 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf003050 -> 0xc10a90ec) (initramfs) cat /proc/modules (initramfs) Are we miss-building the kernel and/or modules? Or am I miss-launching the VM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899519/+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 1847105] Update Released
The verification of the Stable Release Update for virt-manager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in virt-manager source package in Focal: Fix Released Status in libvirt source package in Groovy: Triaged Bug description: [Impact] * The defaults of virt-manager for disk allocation always worked fine when qcow2 had nothing but sparse support. So sparse=True vs sparse=False made no difference. So it always set sparse=False. Then qcow2 grows non-sparse support, and virt-manager is suddenly defaulting to it, which is not the intention. * For upgraders from pre-Focal this was a regression in two ways: a) allocation of qcow changed to non-sparse (fallocate based) potentially consuming more space b) depending on the underlying FS this made the allocation much slower * Fix by applying the upstream change that Defaults to sparse when requested format isn't raw (for raw the assumption ill stay that users do that for runtime performance, so non-sparse on those stays as-is) [Test Case] * open virt-manager and create a new guest which includes creating a new image for it * when clicking "finish" the image will be created (which e.g. on ZFS will take quite some time) * In the background grep ps output if the qemu-img call for qcow (the default) is using "preallocation=fallocate" (wrong) or "preallocation=metadata" (correct) [Regression Potential] * For upgraders from pre-focal it actually ensures behavior stays as is (no change/regression there) * For users of ZFS where the allocation was slow it fixes this slowness. * But for people using Focal all the time and on non-ZFS there will be a behavior change in no more doing falloc pre-allocating the qemu image. To be cleear there are four modes: 1. no allocation 2. metadata allocation - is initially larger but can improve performance when the image needs to grow 3. falloc - preallocates space for image by calling posix_fallocate 4. full - writes data to the underlying storage The fix changes the default from 3->2 which it always was and should be. As the patch says: "If users want to override it, they can do it via custom created storage." (To be clear, upstream changed this as we fixed it here, so on further upgrades what we apply here will be the behavior anyway, it seems wrong to keep Focal the only one in between kept different) * [racb] The code path being added special cases the 'raw' format and in handling of the default sparse setting. Areas of potential regression are therefore in the handling of the default and override of the default in the cases of both 'raw' and not 'raw'. [Other Info] * The slowness effect might be further mitigated by ZFS implementing more falloc options (thanks Richard for that hint) but that won't be in Focal. This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off
[Kernel-packages] [Bug 1898091] Re: Multiple random crashes for the past week
** Package changed: ubuntu => 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/1898091 Title: Multiple random crashes for the past week Status in linux package in Ubuntu: New Bug description: For the past week or so, I have started to have random crashes. Somtimes it is just an app that crashes, sometimes the machine freezes up completely and sometimes it just reboots. I ran a memory test for about 8 hours over the weekend and it found no issues. Looking through some of the crash dmesg files I see: 202009290318/dmesg.202009290318:1186:[ 5527.345666] BUG: unable to handle kernel paging request at ab1bd511 202009291228/dmesg.202009291228:1194:[12423.898689] BUG: unable to handle kernel paging request at ff8e 202009301804/dmesg.202009301804:1386:[31355.601321] BUG: unable to handle kernel paging request at b2cbb6cf 202010011046/dmesg.202010011046:1200:[ 3081.774984] BUG: unable to handle kernel paging request at a0bd8f625a50 Which still leads to think a memory issue. Going to run a longer memtest. I am usually pretty good and figuring out what is going on but this time I need some help to make sure I am on the right track or tell me I am completely wrong. Thanks in advance. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3921 F pulseaudio /dev/snd/controlC1: chris 3921 F pulseaudio Date: Tue Sep 29 16:09:48 2020 InstallationDate: Installed on 2019-01-07 (632 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7693 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=65a42e57-56c3-47ce-beb9-73c0f182e1d4 ro sbcore.autosuspend=-1 amd_iommu=on iommu=pt crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd10/08/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898091/+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 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
I sponsored the procps changes to Groovy. -- 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/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Released Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Released Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: Won't Fix Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by changing kernel.dmesg_restrict sysctl in /etc/sysctl.d/10-kernel-hardening.conf from '1' to '0', followed by a reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
Hello Kai-Chuan, or anyone else affected, Accepted thermald into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thermald/1.9.1-1ubuntu0.3 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. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: In Progress Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Released Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+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 1845801] Update Released
The verification of the Stable Release Update for gdm3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Fix Committed Status in gdm3 package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-430 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in gdm3 source package in Focal: Fix Released Status in gnome-session source package in Focal: Invalid Status in grub2 source package in Focal: Invalid Status in nvidia-graphics-drivers-390 source package in Focal: Invalid Status in nvidia-graphics-drivers-430 source package in Focal: Invalid Status in nvidia-graphics-drivers-435 source package in Focal: Invalid Status in nvidia-graphics-drivers-440 source package in Focal: Invalid Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes
[Kernel-packages] [Bug 1896348] Re: wifi not working due to bcmwl-kernel-source
>From Apttermlog: Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu6) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-47-generic 5.8.0-18-generic Building for architecture x86_64 Building initial module for 5.4.0-47-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-47-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 ** Package changed: ubuntu-release-upgrader (Ubuntu) => bcmwl (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1896348 Title: wifi not working due to bcmwl-kernel-source Status in bcmwl package in Ubuntu: New Bug description: wifi not working installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 18:07:20 2020 InstallationDate: Installed on 2020-09-18 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to groovy on 2020-09-19 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1896348/+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 1879290] Re: pc: no message on the screen for ~30s on fast HW
Has anything happened that would change the status of this bug or does it still need fixing for uc20? -- 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/1879290 Title: pc: no message on the screen for ~30s on fast HW Status in linux package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: The boot on real HW (ARock B450, Ryzen, NVME 240Gb) takes a long time without any visible feedback. Video: https://photos.app.goo.gl/RmaLviXNorjeh5BP7 With grub debug: https://photos.app.goo.gl/PJuXdxp8uedr7fWp9 (google photos has degraded quality quite a bit, may upload the originals if too bad) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879290/+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 1895039] Re: General protection fault
** Package changed: ubuntu => 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/1895039 Title: General protection fault Status in linux package in Ubuntu: Incomplete Bug description: I am using this reposuitory on ubuntu 18.04 with amd 2400g apu. I am experiencing crashes/freezes in chromium-browser. I can find this in dmesg. [ 875.594090] general protection fault, probably for non-canonical address 0x7ed840c139f11979: [#1] SMP NOPTI [ 875.594099] CPU: 0 PID: 284 Comm: kworker/u64:6 Not tainted 5.7.1-050701-generic #202006071230 [ 875.594101] Hardware name: System manufacturer System Product Name/PRIME B350M-A, BIOS 5204 07/29/2019 [ 875.594117] Workqueue: events_unbound commit_work [drm_kms_helper] [ 875.594255] RIP: 0010:amdgpu_dm_atomic_commit_tail+0x270/0x11b0 [amdgpu] [ 875.594258] Code: fe ff ff 48 8b 43 08 8b 90 e0 02 00 00 41 83 c5 01 44 39 ea 0f 87 3a ff ff ff 4c 8b b5 a8 fd ff ff 4d 85 f6 0f 84 ee 00 00 00 <41> 80 be b0 01 00 00 01 0f 86 a1 00 00 00 48 b9 00 00 00 00 01 00 [ 875.594259] RSP: 0018:aa470110fb88 EFLAGS: 00010202 [ 875.594261] RAX: 8edc8e504000 RBX: 8edc6a39f880 RCX: 8edc875d0f00 [ 875.594263] RDX: 0004 RSI: c0eb0a90 RDI: 0002 [ 875.594265] RBP: aa470110fe18 R08: 0001 R09: 0001 [ 875.594266] R10: 9c86a0a0 R11: R12: 8edc6bf43400 [ 875.594267] R13: 0004 R14: 7ed840c139f11979 R15: 8edc6a27dc00 [ 875.594270] FS: () GS:8edc9080() knlGS: [ 875.594272] CS: 0010 DS: ES: CR0: 80050033 [ 875.594273] CR2: 7fd8e05ed010 CR3: 000406368000 CR4: 003406f0 [ 875.594275] Call Trace: [ 875.594284] ? __switch_to_asm+0x40/0x70 [ 875.594286] ? __switch_to_asm+0x34/0x70 [ 875.594289] ? __switch_to_asm+0x40/0x70 [ 875.594291] ? __switch_to_asm+0x34/0x70 [ 875.594293] ? __switch_to_asm+0x40/0x70 [ 875.594295] ? __switch_to_asm+0x34/0x70 [ 875.594297] ? __switch_to_asm+0x40/0x70 [ 875.594299] ? __switch_to_asm+0x34/0x70 [ 875.594301] ? __switch_to_asm+0x40/0x70 [ 875.594304] ? __switch_to_asm+0x34/0x70 [ 875.594306] ? __switch_to_asm+0x40/0x70 [ 875.594308] ? __switch_to_asm+0x34/0x70 [ 875.594310] ? __switch_to_asm+0x40/0x70 [ 875.594312] ? __switch_to_asm+0x34/0x70 [ 875.594314] ? __switch_to_asm+0x40/0x70 [ 875.594316] ? __switch_to_asm+0x34/0x70 [ 875.594318] ? __switch_to_asm+0x40/0x70 [ 875.594320] ? __switch_to_asm+0x34/0x70 [ 875.594322] ? __switch_to_asm+0x40/0x70 [ 875.594324] ? __switch_to_asm+0x34/0x70 [ 875.594326] ? __switch_to_asm+0x40/0x70 [ 875.594328] ? __switch_to_asm+0x34/0x70 [ 875.594330] ? __switch_to_asm+0x40/0x70 [ 875.594332] ? __switch_to_asm+0x34/0x70 [ 875.594335] ? __switch_to_asm+0x40/0x70 [ 875.594336] ? __switch_to_asm+0x34/0x70 [ 875.594338] ? __switch_to_asm+0x40/0x70 [ 875.594342] ? __switch_to+0x157/0x450 [ 875.594344] ? __switch_to_asm+0x40/0x70 [ 875.594345] ? __switch_to_asm+0x34/0x70 [ 875.594348] ? __schedule+0x2e5/0x780 [ 875.594350] ? preempt_schedule_common+0x18/0x30 [ 875.594352] ? _cond_resched+0x19/0x30 [ 875.594354] ? wait_for_completion_timeout+0x3a/0x100 [ 875.594356] ? reschedule_interrupt+0xa/0x20 [ 875.594366] commit_tail+0x99/0x130 [drm_kms_helper] [ 875.594375] commit_work+0x12/0x20 [drm_kms_helper] [ 875.594377] process_one_work+0x1e8/0x3b0 [ 875.594379] worker_thread+0x4d/0x400 [ 875.594382] kthread+0x104/0x140 [ 875.594383] ? process_one_work+0x3b0/0x3b0 [ 875.594384] ? kthread_park+0x90/0x90 [ 875.594386] ret_from_fork+0x22/0x40 [ 875.594388] Modules linked in: edac_mce_amd kvm joydev amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec crct10dif_pclmul snd_hda_core snd_hwdep amd_iommu_v2 gpu_sched crc32_pclmul snd_pcm ttm ghash_clmulni_intel snd_seq_midi drm_kms_helper snd_seq_midi_event cec snd_rawmidi rc_core snd_seq drm snd_seq_device snd_timer aesni_intel i2c_algo_bit pl2303 crypto_simd fb_sys_fops snd syscopyarea eeepc_wmi ch341 cryptd asus_wmi sysfillrect glue_helper usbserial hid_multitouch sparse_keymap wmi_bmof k10temp ccp sysimgblt soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i2c_piix4 r8169 ahci realtek libahci wmi video gpio_amdpt gpio_generic [ 875.594420] ---[ end trace a232a1a96753b9ba ]--- [ 875.594501] RIP: 0010:amdgpu_dm_atomic_commit_tail+0x270/0x11b0 [amdgpu] [ 875.594504] Code: fe ff ff 48 8b 43 08 8b 90 e0 02 00 00 41 83 c5 01 44 39 ea 0f 87 3a ff ff ff 4c 8b b5 a8 fd ff ff 4d 85 f6 0f 84 ee 00 00 00
[Kernel-packages] [Bug 1894203] Re: Trackpad not get detected and not working
** Package changed: ubuntu-release-upgrader (Ubuntu) => 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/1894203 Title: Trackpad not get detected and not working Status in linux package in Ubuntu: New Bug description: I have checked /proc/bus/input/devices, there is not entry related to trackpad. Below is the content of the same file I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input6 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:35/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:03/input/input8 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input9 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input10 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 14:44:59 2020 InstallationDate: Installed on 2020-05-08 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894203/+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 1891336] Re: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel
See also bug 1215411 for some discussion regarding providing libcpupower. -- 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/1891336 Title: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel Status in cpufreqd package in Ubuntu: New Status in gkrellm2-cpufreq package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I don't know how important that is as gkrellm2-cpufreq itself is scheduled for removal. But I wanted to make sure that it is known that the Debian kernel produces "libcpupower-dev" which isn't available in Ubuntu and thereby blocking various things in proposed. root@d10-sid:~# apt-cache show libcpupower-dev Package: libcpupower-dev Source: linux Version: 5.7.10-1 Installed-Size: 169 Maintainer: Debian Kernel Team Architecture: amd64 Replaces: libcpufreq-dev Provides: libcpufreq-dev Depends: libcpupower1 (= 5.7.10-1) Conflicts: libcpufreq-dev Description-en: CPU frequency and voltage scaling tools for Linux (development files) libcpupower is a library for inspecting and controlling cpufreq and cpuidle tunables. . This package is needed to compile programs against libcpupower. gkrellm2-cpufreq will most likely be removed from goovy as it makes no sense without that build-dep. Never the less the kernel Team could evaluate if providing "libcpupower-dev" makes sense for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1891336/+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 1870189] Re: initramfs does not get loaded
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
Confirmed
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Triaged
Status in grub2 source package in Focal:
New
Status in linux-azure source package in Focal:
Invalid
Status in livecd-rootfs source package in Focal:
New
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+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 1890913] Re: init is using 100% of processor
** No longer affects: apport (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/1890913 Title: init is using 100% of processor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+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 1830084] Re: ubuntu_kernel_selftests ftrace fails
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-azure (Ubuntu Eoan) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1830084 Title: ubuntu_kernel_selftests ftrace fails Status in ubuntu-kernel-tests: Invalid Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-azure source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-oracle source package in Eoan: Won't Fix Bug description: Cloud: Azure Series: Disco Kernel: 5.0.0-1007.7 linux-azure Instance: Standard_D2_v3 and others. 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13 05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest 05/20 14:24:27 DEBUG| utils:0153| [stdout] 05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal number: 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests === 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing check 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer size 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing setting 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and trace_marker 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event - add/remove kprobe events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event - add/remove synthetic events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event - selective clear (compatibility) 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event - generic clear event 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - enable/disable with event level files 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - restricts events based on pid 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - enable/disable with subsystem level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - enable/disable with top level
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: systemd (Ubuntu Eoan) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Fix Released Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Won't Fix Status in systemd package in Debian: Fix Released Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1830084] Re: ubuntu_kernel_selftests ftrace fails
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-gcp (Ubuntu Eoan) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1830084 Title: ubuntu_kernel_selftests ftrace fails Status in ubuntu-kernel-tests: Invalid Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-azure source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-oracle source package in Eoan: Won't Fix Bug description: Cloud: Azure Series: Disco Kernel: 5.0.0-1007.7 linux-azure Instance: Standard_D2_v3 and others. 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13 05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest 05/20 14:24:27 DEBUG| utils:0153| [stdout] 05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal number: 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests === 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing check 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer size 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing setting 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and trace_marker 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event - add/remove kprobe events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event - add/remove synthetic events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event - selective clear (compatibility) 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event - generic clear event 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - enable/disable with event level files 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - restricts events based on pid 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - enable/disable with subsystem level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - enable/disable with top level files
[Kernel-packages] [Bug 1867128] Re: Install nvidia_layers.json in /usr/share/vulkan/implicit_layer.d
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Eoan) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1867128 Title: Install nvidia_layers.json in /usr/share/vulkan/implicit_layer.d Status in nvidia-graphics-drivers-435 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 source package in Bionic: New Status in nvidia-graphics-drivers-440 source package in Bionic: New Status in nvidia-graphics-drivers-435 source package in Eoan: Won't Fix Status in nvidia-graphics-drivers-440 source package in Eoan: Won't Fix Bug description: As per the subject, the nvidia_layers.json file should live in /usr/share/vulkan/implicit_layer.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1867128/+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 1872021] Re: [Ubuntu][Bionic] systemd caused kernel to hang on fsnotify wait-on-completion
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872021 Title: [Ubuntu][Bionic] systemd caused kernel to hang on fsnotify wait-on- completion Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Triaged Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Incomplete Bug description: This is with MAAS 2.7.0, commissioning an HP DL385 G7 with Bionic. During the first boot, the machine performs an apt-get upgrade, which includes an update of ipmitool (1.8.18-5ubuntu0.1) and freeipmi-tools (1.4.11-1.1ubuntu4.1). This triggers hung tasks: [ 66.457048] cloud-init[1534]: Setting up ipmitool (1.8.18-5ubuntu0.1) ... Starting IPMI event daemon... [ OK ] Started IPMI event daemon. [ 67.240857] cloud-init[1534]: Setting up freeipmi-tools (1.4.11-1.1ubuntu4.1) ... [ 67.254241] cloud-init[1534]: Processing triggers for systemd (237-3ubuntu10.39) ... [ 242.642684] INFO: task systemd:1 blocked for more than 120 seconds. [ 242.725654] Not tainted 4.15.0-96-generic #97-Ubuntu [ 242.799835] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.906319] INFO: task kworker/u49:0:6 blocked for more than 120 seconds. [ 242.997214] Not tainted 4.15.0-96-generic #97-Ubuntu [ 243.072024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.381896] cloud-init[1534]: Failed to reload daemon: Connection timed out [ 247.385109] cloud-init[1534]: Processing triggers for man-db (2.8.3-2ubuntu0.1) ... [ 249.828279] cloud-init[1534]: Processing triggers for ureadahead (0.100.0-21) ... [ 249.874840] cloud-init[1534]: Processing triggers for install-info (6.5.0.dfsg.1-2) ... [ 250.160889] cloud-init[1534]: Processing triggers for libc-bin (2.27-3ubuntu1) ... [ 363.465849] INFO: task systemd:1 blocked for more than 120 seconds. [ 363.550072] Not tainted 4.15.0-96-generic #97-Ubuntu [ 363.623823] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.728949] INFO: task kworker/u49:0:6 blocked for more than 120 seconds. [ 363.820481] Not tainted 4.15.0-96-generic #97-Ubuntu [ 363.894774] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 484.291609] INFO: task systemd:1 blocked for more than 120 seconds. [ 484.381026] Not tainted 4.15.0-96-generic #97-Ubuntu [ 484.458451] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 484.568130] INFO: task kworker/u49:0:6 blocked for more than 120 seconds. [ 484.661642] Not tainted 4.15.0-96-generic #97-Ubuntu [ 484.740371] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 484.850615] INFO: task udevadm:2665 blocked for more than 120 seconds. [ 484.942379] Not tainted 4.15.0-96-generic #97-Ubuntu [ 485.018318] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 607.165768] INFO: task systemd:1 blocked for more than 120 seconds. [ 607.250976] Not tainted 4.15.0-96-generic #97-Ubuntu [ 607.325651] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 607.432497] INFO: task kworker/u49:0:6 blocked for more than 120 seconds. [ 607.525757] Not tainted 4.15.0-96-generic #97-Ubuntu [ 607.599770] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 607.707273] INFO: task udevadm:2665 blocked for more than 120 seconds. [ 607.795467] Not tainted 4.15.0-96-generic #97-Ubuntu [ 607.869751] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. I can perform more tests on this system if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1872021/+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 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866972 Title: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Bug description: [Impact] kernel selftest ftrace will fail with: [42] Register/unregister many kprobe events [FAIL] [Test case] Run that selftest with: cd tools/testing/selftests/ftrace/ sudo make run_tests [Regression potential] The suggested fix only change the test, not the ftrace code. From the nature of the test, the change would hardly prevent us from detecting other hard failures besides that we do not return EEXIST currently for duplicate probes. = Issue found on c4.large with 5.0.0-1027.30-aws Test failed with: [42] Register/unregister many kprobe events [FAIL] selftests: ftrace: ftracetest === Ftrace unit tests === [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] [3] Basic trace clock test [PASS] [4] Basic event tracing check[PASS] [5] Change the ringbuffer size [PASS] [6] Snapshot and tracing setting [PASS] [7] trace_pipe and trace_marker [PASS] [8] Generic dynamic event - add/remove kprobe events [PASS] [9] Generic dynamic event - add/remove synthetic events [PASS] [10] Generic dynamic event - selective clear (compatibility) [PASS] [11] Generic dynamic event - generic clear event [PASS] [12] event tracing - enable/disable with event level files [PASS] [13] event tracing - restricts events based on pid [PASS] [14] event tracing - enable/disable with subsystem level files [PASS] [15] event tracing - enable/disable with top level files [PASS] [16] Test trace_printk from module [UNRESOLVED] [17] ftrace - function graph filters with stack tracer [PASS] [18] ftrace - function graph filters [PASS] [19] ftrace - function pid filters [PASS] [20] ftrace - stacktrace filter command [PASS] [21] ftrace - function trace with cpumask[PASS] [22] ftrace - test for function event triggers [PASS] [23] ftrace - function trace on module [UNRESOLVED] [24] ftrace - function profiling [PASS] [25] ftrace - function profiler with function tracing[PASS] [26] ftrace - test reading of set_ftrace_filter [PASS] [27] ftrace - test for function traceon/off triggers [PASS] [28] Test creation and deletion of trace instances while setting an event [PASS] [29] Test creation and deletion of trace instances [PASS] [30] Kprobe dynamic event - adding and removing [PASS] [31] Kprobe dynamic event - busy event check [PASS] [32] Kprobe dynamic event with arguments [PASS] [33] Kprobe event with comm arguments[PASS] [34] Kprobe event string type argument [PASS] [35] Kprobe event symbol argument[PASS] [36] Kprobe event argument syntax[PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer [PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events [FAIL] [43] Kprobe dynamic event - adding and removing [PASS] [44] test for the preemptirqsoff tracer [UNSUPPORTED] [45] Test wakeup tracer [PASS] [46] Test wakeup RT tracer [PASS] [47] event trigger - test extended error support [PASS] [48] event trigger - test field variable support [PASS] [49] event trigger - test multiple actions on hist trigger [PASS] [50] event trigger - test inter-event histogram trigger onmatch action [PASS] [51] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [52] event trigger - test inter-event histogram trigger onmax action [PASS] [53] event trigger - test synthetic_events syntax parser [PASS] [54] event trigger - test event enable/disable trigger [PASS] [55] event trigger - test trigger filter [PASS] [56] event trigger - test histogram modifiers[PASS] [57] event trigger - test multiple histogram triggers[PASS] [58] event trigger - test snapshot-trigger [PASS] [59] event trigger - test stacktrace-trigger [PASS] [60] trace_marker trigger - test snapshot trigger[PASS] [61] trace_marker trigger - test histogram with synthetic event against
[Kernel-packages] [Bug 1867128] Re: Install nvidia_layers.json in /usr/share/vulkan/implicit_layer.d
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1867128 Title: Install nvidia_layers.json in /usr/share/vulkan/implicit_layer.d Status in nvidia-graphics-drivers-435 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 source package in Bionic: New Status in nvidia-graphics-drivers-440 source package in Bionic: New Status in nvidia-graphics-drivers-435 source package in Eoan: Won't Fix Status in nvidia-graphics-drivers-440 source package in Eoan: Won't Fix Bug description: As per the subject, the nvidia_layers.json file should live in /usr/share/vulkan/implicit_layer.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1867128/+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 1864045] Re: [SRU] Hibernation events sometimes missed on repeated attempts
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: acpid (Ubuntu Eoan) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864045 Title: [SRU] Hibernation events sometimes missed on repeated attempts Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in acpid source package in Bionic: Incomplete Status in linux source package in Bionic: Incomplete Status in acpid source package in Eoan: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: When testing hibernation / resume on AWS with 5.0 or 5.3 kernels on bionic (using acpid 1:2.0.28-1ubuntu1), we sometimes see failure with repeated attempts. The first attempt will always be triggered, but the next attempt may not. The result is the agent never triggers the hibernation process and the instance will be forced to shutdown after a timeout period. Two workarounds have been identified. The first is to restart acpid during the resume handler. The second is to use the latest upstream acpid (as of Feb 1, 2020). This second workaround indicates there may be a patch missing in the acpid in bionic (1:2.0.28-1ubuntu1) to work with the 5.0+ kernels. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel on a bionic image with on-demand hibernation support enabled. 2) Hibernate and resume the instance, ensuring the system is fully resumed afterward and the swap file has been removed. 3) Hibernate and resume another time. The hibernate should be triggered immediately and the instance should become unresponsive as it saves state to disk. 4) Resume the instance, it should come back with the same processes running. 5) Repeat 3) - 4) as necessary. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: acpid 1:2.0.28-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1864045/+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 1877654] Re: Add XDP support to hv_netvsc driver
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-azure (Ubuntu Eoan) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1877654 Title: Add XDP support to hv_netvsc driver Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Confirmed Status in linux-azure source package in Eoan: Won't Fix Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Bug description: Microsoft would like to request the following three patches in all releases supported on Azure: 351e1581395fc (“hv_netvsc: Add XDP support”) 12fa74383ed4d (“hv_netvsc: Update document for XDP support”) 184367dce4f7 (“hv_netvsc: Fix XDP refcnt for synthetic and VF NICs”) These patches add support of XDP in native mode to the hv_netvsc driver, and transparently sets the XDP program on the associated VF NIC as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877654/+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 1886364] Re: initiator causes kernel crash when login lun/disk on Focal
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Eoan) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886364 Title: initiator causes kernel crash when login lun/disk on Focal Status in ceph-iscsi package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Confirmed Bug description: Software version linaro@j13-r120-t32-09:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal linaro@j13-r120-t32-09:~$ uname -a Linux j13-r120-t32-09 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 17:57:16 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux linaro@j13-r120-t32-09:~$ stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search ceph-iscsi Sorting... Done Full Text Search... Done ceph-iscsi/focal,now 3.4-0ubuntu2 all [installed] common logic and CLI tools for creating and managing LIO gateways for Ceph stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search tcmu-runner Sorting... Done Full Text Search... Done libtcmu2/focal,now 1.5.2-5build1 arm64 [installed,automatic] Library that handles the userspace side of the LIO TCM-User backstore tcmu-runner/focal,now 1.5.2-5build1 arm64 [installed] Daemon that handles the userspace side of the LIO TCM-User backstore Hardware cavium thx1 root@j13-r120-t32-09:/home/linaro# lshw -c cpu *-cpu description: CPU product: ARM (CN88xx) vendor: CN8890-2000BG2601-CP-Y-G physical id: 2e bus info: cpu@0 version: 2.1 serial: CPU Serial# slot: Socket size: 2GHz capacity: 2GHz clock: 156MHz capabilities: lm configuration: cores=48 enabledcores=48 root@j13-r120-t32-09:/home/linaro# lshw -c system j13-r120-t32-09 description: System product: R120-T32-00 (01234567890123456789AB) vendor: GIGABYTE version: 0100 serial: GHG2N2912A0009 width: 64 bits capabilities: smbios-3.0.0 dmi-3.0.0 smp cp15_barrier setend swp tagged_addr_disabled configuration: chassis=server family=Server sku=01234567890123456789AB uuid=--4000-8000-1C1B0D94A9DE Reproduce Setup ceph iscsi gate way and initiator in the same ubuntu focal all-in-one. iSCSI targets setup 1, $ apt install ceph-iscsi targetcli-fb 2, ceph iscsi config stack@j13-r120-t32-09:~/devstack-plugin-ceph$ sudo cat /etc/ceph/iscsi-gateway.cfg [config] api_port = 5002 api_password = openstack api_user = openstack api_secure = false prometheus_host = 10.101.96.110 gateway_keyring = ceph.client.admin.keyring cluster_name = ceph trusted_ip_list = 10.101.96.110,localhost minimum_gateways = 1 pool = volumes 3, target iqn, client iqn, disk/lun creation https://docs.ceph.com/docs/master//rbd/iscsi-target-cli/ iSCSI initiator setup 1, $ apt install open-iscsi https://www.server-world.info/en/note?os=Ubuntu_18.04=iscsi=3 2, $ iscsiadm -m discovery -t sendtargets -p 10.101.96.110 $ sudo iscsiadm -m node -T iqn.1993-08.org.opendev:01:a9aa4032d2c1 -l Login lun cause crash ceph iscsi gw node [ 122.112611] xfs filesystem being mounted at /var/lib/ceph supports timestamps until 2038 (0x7fff) linaro@j13-r120-t32-09:~$ [ 1512.796815] Unable to handle kernel read from unreadable memory at virtual address 01dc0040 [ 1512.805865] Mem abort info: [ 1512.808647] ESR = 0x9604 [ 1512.811702] EC = 0x25: DABT (current EL), IL = 32 bits [ 1512.817023] SET = 0, FnV = 0 [ 1512.820089] EA = 0, S1PTW = 0 [ 1512.823238] Data abort info: [ 1512.826128] ISV = 0, ISS = 0x0004 [ 1512.829972] CM = 0, WnR = 0 [ 1512.832933] user pgtable: 4k pages, 48-bit VAs, pgdp=000cd14a [ 1512.839410] [01dc0040] pgd= [ 1512.844300] Internal error: Oops: 9604 [#1] SMP [ 1512.849169] Modules linked in: target_core_pscsi target_core_file target_core_iblock iscsi_target_mod xfs xt_REDIRECT xt_comment xt_nat xt_mark xt_connmark ip6table_raw iptable_raw xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc target_core_user uio target_core_mod nf_conntrack_netlink binfmt_misc nls_iso8859_1 nfnetlink_cttimeout nfnetlink ipmi_ssif ipmi_devintf cavium_rng_vf joydev input_leds ipmi_msghandler cavium_rng thunderx_edac openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel ip_tables x_tables autofs4 crct10dif_ce
