[Kernel-packages] [Bug 1833281] Re: System freeze when memory is put on SWAP in Linux >4.10.x
Possible duplicate of LP: #1861359. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.sku: T
[Kernel-packages] [Bug 1845632] Re: After dist-upgrade, s390x running X-fips/B-fips kernel will boot into generic kernel
Oh btw, IIRC this issue does not exist before I file this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845632 Title: After dist-upgrade, s390x running X-fips/B-fips kernel will boot into generic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on s390x KVM Steps: 1. Deploy a s390x KVM with Xenial 2. Enable -proposed 3. Enable FIPS ppa 4. Install the FIPS kernel with linux-fips meta package 5. reboot 6. dist-upgrade 7. reboot The system will boot into the correct fips kernel on step 5, but it will boot into the generic kernel in proposed on step 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869823] Re: No sound after kernel update
Hi, Confirming this started with 5.3.0-42 and also occurs in 5.3.0-45. Tried other fixes. Finally, I had to revert to 5.3.0-40. Machine: Lenovo YOGA C930 laptop OS: Linux Mint 19.3 / Ubuntu 18.04 Other info: ➜ ~ uname -r 5.3.0-42-generic ➜ ~ lspci -nnk | grep -A2 Audio 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Subsystem: Lenovo Sunrise Point-LP HD Audio [17aa:3831] Kernel driver in use: snd_soc_skl Kernel modules: snd_hda_intel, snd_soc_skl ➜ ~ sudo dmesg | grep -i audio [ 0.103742] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [ 3.714632] snd_soc_skl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 3.957703] HDMI HDA Codec ehdaudio0D2: Max dais supported: 3 [ 214.794189] Modules linked in: rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc ccm hid_sensor_als hid_sensor_accel_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio hid_sensor_custom 8250_dw hid_sensor_hub snd_soc_dmic aufs wacom hid_multitouch snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_soc_skl(-) snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc overlay snd_soc_sst_dsp bnep snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel mei_hdcp kvm_intel snd_intel_nhlt intel_rapl_msr snd_hda_codec kvm snd_hda_core irqbypass snd_hwdep snd_pcm iwlmvm snd_seq_midi crct10dif_pclmul nls_iso8859_1 snd_seq_midi_event crc32_pclmul ghash_clmulni_intel mac80211 [ 215.890790] snd_soc_skl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 215.902992] HDMI HDA Codec ehdaudio0D2: Max dais supported: 3 -- 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/1869823 Title: No sound after kernel update Status in linux package in Ubuntu: Confirmed Bug description: With the -45 kernel, sound output and input are unavailable. Output shows a Dummy device, no Input devices. This is a regression from the -40 kernel where the Output was working (no Input though). Attempted to use SOF, i.e. the fix mentioned in https://github.com/thesofproject/linux/issues/1877 This results in system freezes, failed boots, and failure to wake from sleep. Edit: I have now noticed that it fails to wake from sleep in general with this kernel. Even without the SOF driver. Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 lspci: https://pastebin.com/6ft2qvTT dmesg: https://pastebin.com/4DLg6wy4 Thanks, Matt --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-03-17 (13 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: gpd0 no wireless extensions. wlp0s20f3 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Inspiron 7591 2n1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=df0d1f5a-7ff4-440f-bac3-f31750947cd4 ro quiet splash acpi_osi=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-45-generic N/A linux-backports-modules-5.3.0-45-generic N/A linux-firmware1.187 Tags: tricia Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0NNW5N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd12/24/2019:svnDellInc.:pnInspiron75912n1:pvr:rvnDellInc.:rn0NNW5N:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 2n1 dmi.product.sku: 0950 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869763] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1869763 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in linux package in Ubuntu: Incomplete Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869799] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1869799 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869799 Title: no sound driver since 5.3.0.42 kernel Status in linux package in Ubuntu: Incomplete Bug description: no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the problem. i have only a dummy soundcard. no sound. 5.3.0.42 kernel works fine. my sound card is intel 100 / c230 hd audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: eoan kernel-sound -- 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/1869799 Title: no sound driver since 5.3.0.42 kernel Status in linux package in Ubuntu: Incomplete Bug description: no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the problem. i have only a dummy soundcard. no sound. 5.3.0.42 kernel works fine. my sound card is intel 100 / c230 hd audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
** Package changed: linux-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/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in linux package in Ubuntu: Incomplete Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864505] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1864505 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Status in zfs-linux package in Ubuntu: Triaged Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869823] Re: No sound after kernel update
** Description changed: With the -45 kernel, sound output and input are unavailable. Output shows a Dummy device, no Input devices. This is a regression from the -40 kernel where the Output was working (no Input though). Attempted to use SOF, i.e. the fix mentioned in https://github.com/thesofproject/linux/issues/1877 This results in system freezes, failed boots, and failure to wake from sleep. + Edit: I have now noticed that it fails to wake from sleep in general + with this kernel. Even without the SOF driver. + Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 - lspci: https://pastebin.com/6ft2qvTT dmesg: https://pastebin.com/4DLg6wy4 Thanks, Matt - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-03-17 (13 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: - gpd0 no wireless extensions. - - wlp0s20f3 no wireless extensions. - - lono wireless extensions. + gpd0 no wireless extensions. + + wlp0s20f3 no wireless extensions. + + lono wireless extensions. MachineType: Dell Inc. Inspiron 7591 2n1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=df0d1f5a-7ff4-440f-bac3-f31750947cd4 ro quiet splash acpi_osi=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 RelatedPackageVersions: - linux-restricted-modules-5.3.0-45-generic N/A - linux-backports-modules-5.3.0-45-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.3.0-45-generic N/A + linux-backports-modules-5.3.0-45-generic N/A + linux-firmware1.187 Tags: tricia Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0NNW5N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd12/24/2019:svnDellInc.:pnInspiron75912n1:pvr:rvnDellInc.:rn0NNW5N:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 2n1 dmi.product.sku: 0950 dmi.sys.vendor: Dell Inc. -- 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/1869823 Title: No sound after kernel update Status in linux package in Ubuntu: Confirmed Bug description: With the -45 kernel, sound output and input are unavailable. Output shows a Dummy device, no Input devices. This is a regression from the -40 kernel where the Output was working (no Input though). Attempted to use SOF, i.e. the fix mentioned in https://github.com/thesofproject/linux/issues/1877 This results in system freezes, failed boots, and failure to wake from sleep. Edit: I have now noticed that it fails to wake from sleep in general with this kernel. Even without the SOF driver. Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 lspci: https://pastebin.com/6ft2qvTT dmesg: https://pastebin.com/4DLg6wy4 Thanks, Matt --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-03-17 (13 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: gpd0 no wireless extensions. wlp0s20f3 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Inspiron 7591 2n1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=df0d1f5a-7ff4-440f-bac3-f31750947cd4 ro quiet splash acpi_osi=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-45-generic N/A linux-backports-modules-5.3.0-45-generic N/A linux-firmware1.187 Tags: tricia Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0NNW5N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chas
[Kernel-packages] [Bug 1869823] Re: No sound after kernel update
Weird, this should be fixed in the 5.3.0-43 kernel, I don't know why it is reproduced in -45 kernel. This bug was fixed by this bug: https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061 -- 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/1869823 Title: No sound after kernel update Status in linux package in Ubuntu: Confirmed Bug description: With the -45 kernel, sound output and input are unavailable. Output shows a Dummy device, no Input devices. This is a regression from the -40 kernel where the Output was working (no Input though). Attempted to use SOF, i.e. the fix mentioned in https://github.com/thesofproject/linux/issues/1877 This results in system freezes, failed boots, and failure to wake from sleep. Edit: I have now noticed that it fails to wake from sleep in general with this kernel. Even without the SOF driver. Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 lspci: https://pastebin.com/6ft2qvTT dmesg: https://pastebin.com/4DLg6wy4 Thanks, Matt --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-03-17 (13 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: gpd0 no wireless extensions. wlp0s20f3 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Inspiron 7591 2n1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=df0d1f5a-7ff4-440f-bac3-f31750947cd4 ro quiet splash acpi_osi=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-45-generic N/A linux-backports-modules-5.3.0-45-generic N/A linux-firmware1.187 Tags: tricia Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0NNW5N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd12/24/2019:svnDellInc.:pnInspiron75912n1:pvr:rvnDellInc.:rn0NNW5N:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 2n1 dmi.product.sku: 0950 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864505] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343658/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASUSTeKCOMPUTERI
[Kernel-packages] [Bug 1864505] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343660/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASUSTeK
[Kernel-packages] [Bug 1864505] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343664/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd0
[Kernel-packages] [Bug 1864505] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343663/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnA
[Kernel-packages] [Bug 1864505] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343662/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASUSTeKCOMPUTE
[Kernel-packages] [Bug 1868894] Re: [uc18] docker overlayfs* seems broken
** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1868894 Title: [uc18] docker overlayfs* seems broken Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Bionic: New Bug description: A customer recently reported that 'sudo docker run hello-world' fails on a pi3 or pi4 running UC18. Looking at the journal, the failure appears to be caused by an apparmor denial related docker's overlay2 storage driver. I've tried both the unified and the Pi3 specific UC18 images and both fail with the same error. The same command works fine on other devices running UC18 (I've tested multipass+macOS, and dragonboard), and also works on a Pi3b running our standard UC16 image. Here are the details from the UC18 image. $ snap list core 16-2.43.3 8691stablecanonical✓ core core18202001241673stablecanonical✓ base docker18.09.9 427 stablecanonical✓ - pi18-127 18-pi canonical✓ gadget pi-kernel 5.3.0-1019.21~18.04.1 104 18-pi canonical✓ kernel snapd 2.43.3 6438stablecanonical✓ snapd And here's the apparmor denial: Mar 24 19:38:55 localhost sudo[3095]: awe : TTY=pts/0 ; PWD=/home/awe ; USER=root ; COMMAND=/snap/bin/docker run hello-world Mar 24 19:39:02 localhost audit[2932]: AVC apparmor="DENIED" operation="open" profile="snap.docker.dockerd" name="/system-data/var/snap/docker/common/var-lib-docker/overlay2/afce643d5ac2c31f46b8c867c35abea776166c6da199fab370c30af17d314fd7-init/diff/.dockerenv" pid=2932 comm="dockerd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 I've been told this may end up being something that gets worked around in snapd, however as this looks like a regression, I'm erring on the side of caution and filing this bug anyways. Please let me know if there's anything else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1868894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864505] Re: wifi service stops periodically
apport information ** Tags added: apport-collected ** Description changed: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: justin 2184 F pulseaudio + /dev/snd/controlC0: justin 2184 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a + InstallationDate: Installed on 2016-07-30 (1340 days ago) + InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + MachineType: ASUSTeK COMPUTER INC. X550LA + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro + ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-42-generic N/A + linux-backports-modules-5.3.0-42-generic N/A + linux-firmware1.183.4 + Tags: eoan + Uname: Linux 5.3.0-42-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/30/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: X550LA.303 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: X550LA + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: ATN12345678901234567 + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: X + dmi.product.name: X550LA + dmi.product.sku: ASUS-NotebookSKU + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/
[Kernel-packages] [Bug 1864505] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343659/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:sv
[Kernel-packages] [Bug 1864505] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343661/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASUSTeKCOMPUTE
[Kernel-packages] [Bug 1864505] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343668/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASUST
[Kernel-packages] [Bug 1864505] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343667/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnA
[Kernel-packages] [Bug 1864505] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343671/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASU
[Kernel-packages] [Bug 1864505] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343666/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/201
[Kernel-packages] [Bug 1864505] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343665/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnA
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Note: I don't even have any NVIDIA stuff. -- 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 gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: 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 GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864505] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343669/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASUSTeKCOMPU
[Kernel-packages] [Bug 1864505] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1864505/+attachment/5343670/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Incomplete Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASUSTeKCOMPU
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I am currently having this issue. The issue = Login Loop. Distro: Ubuntu 19.10 As a temporary solution, I am using Lightdm instead of default GDM3. Is there anything that I can help, do let me know. -- 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 gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: 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 GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsu
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I just see kernel 5.3.0-45-101 as a new kernel and in the changelog only see "Bump ABI". Where can i see all changes and will it fix more of this issue here or make it worse again? -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836858] Re: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
Done: https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/102 ** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #102 https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/102 ** Also affects: plymouth via https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/102 Importance: Unknown Status: Unknown ** Changed in: plymouth (Ubuntu) Status: New => Confirmed ** Changed in: plymouth (Ubuntu) Importance: Undecided => Low -- 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/1836858 Title: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background Status in Plymouth: Unknown Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Bug description: I am trying flickerfree boot in 19.10 [1], but find it actually flickers part way through: 1. BIOS logo on a black background. 2. Display mode resets, no image on a black background briefly. 3. BIOS logo on a black background. The flicker occurs seemingly during kernel startup since my peripherals are lit up before the problem occurs. Suspecting this might be related to FB handover: [2.751028] fb0: switching to inteldrmfb from EFI VGA I tried disabling that with a big hammer: i915.modeset=0 so it stays in efifb, and that works -- no more flickering, providing I don't let i915 take over the framebuffer. [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 17 16:34:36 2019 InstallationDate: Installed on 2019-05-02 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) MachineType: LENOVO 10M7CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1836858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864505] Re: wifi service stops periodically
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in linux package in Ubuntu: Confirmed Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 2184 F pulseaudio /dev/snd/controlC0: justin 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c4e464fc-56d9-45b5-ae86-0395f688169a InstallationDate: Installed on 2016-07-30 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550LA Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=cb095263-d212-4d82-8838-adb6b2404e49 ro ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (156 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.303:bd09/30/2013:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnA
[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Cannot connect BT earphones or speakers
** Attachment added: "5.3.0-18-btmon-speaker.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1869857/+attachment/5343689/+files/5.3.0-18-btmon-speaker.log ** Description changed: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control - center, either using bluetoothctl. + center, either using bluetoothctl. I've tried with previous versions of + the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, + so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, - bluez 5.50) + bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) - -> in g-c-c, the device appears as "Not Set Up" (OK) + -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it - -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) + -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: - $ sudo bluetoothctl + $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: - 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... + 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed - - Additional information == $ lspci -vv -s 01:00.0 01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) - Subsystem: Intel Corporation Dual Band
[Kernel-packages] [Bug 1869857] [NEW] [Intel 7265][Regression] Cannot connect BT earphones or speakers
Public bug reported: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control center, either using bluetoothctl. I've tried with previous versions of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed Additional information == $ lspci -vv -s 01:00.0 01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi $ dmesg | grep -i bluetooth [ 15.748300] Bluetooth: Core ver 2.22 [ 15.748312] Bluetooth: HCI device and connection manager initialized [ 15.748315] Bluetooth: HCI socket layer initialized [ 15.748317] Bluetooth: L2CAP socket layer initialized [ 15.748320] Bluetooth: SCO socket layer initialized [ 15.925524] Bluetooth: hci0: read Intel version: 370810011003110e00 [ 15.926254] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-h
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu10 --- zfs-linux (0.8.3-1ubuntu10) focal; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Make debian/patches/4000-zsys-support.patch more robust in case of corruption and faster: - Don’t call out zsys if the system hasn’t changed compared to its cache. This drastically speed up boot by some seconds. - Drop into emergency mode with some error message in dmesg with the failing command output in case some errors happen during revert. Prevents thus booting which would have screwed over root partition by creating a /boot non empty directory (like /boot/grub) in mounting over. Let now user still boot without reverting to be able to fix the issue. - Base what we import on cache file so that in the future (once grub is fixed) booting with multiple rpool and bpool. (LP: #1867007) * debian/patches/4500-fix-generator-invalid-cache.patch: - Removed, not needed anymore with previous patch enhancement. -- Didier Roche Mon, 30 Mar 2020 17:05:32 +0200 ** Changed in: zfs-linux (Ubuntu) Status: Triaged => Fix Released -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839504] Re: [ICL-Graphics] Black screen at desktop on kernel for ICL
closing for osp1 ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: Triaged => Invalid ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839504 Title: [ICL-Graphics] Black screen at desktop on kernel for ICL Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Invalid Bug description: Description: Recent 5.2 kernels showing black screen after logging into ICL machine. Commit which introduce this issue: Author: Ville Syrjälä drm/i915: Make sure we have enough memory bandwidth on ICL ICL has so many planes that it can easily exceed the maximum effective memory bandwidth of the system. We must therefore check that we don't exceed that limit ... Commit fix this issue commit 56e9371bc3f3e7d6c1a197a45d550b2ce6af25f6 Author: Ville Syrjälä Date: Thu Jun 6 15:42:10 2019 +0300 drm/i915: Deal with machines that expose less than three QGV points Target Kernel: 5.3 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1839504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Cannot connect BT earphones or speakers
I can't see anyone else reporting such issues right now. What model of speaker/headphones is it? ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1869857 Title: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing Status in bluez package in Ubuntu: New Bug description: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control center, either using bluetoothctl. I've tried with previous versions of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed Additional information == $ lspci -vv -s 01:00.0 01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 Control: I/O- Mem+ BusMast
[Kernel-packages] [Bug 1862858] Re: CIFS accesses DFS referral with wrong Kerberos ticket
I have tested 5.4.0-21.25 from focal-proposed. The DFS referrals work correctly. -- 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/1862858 Title: CIFS accesses DFS referral with wrong Kerberos ticket Status in linux package in Ubuntu: Incomplete Bug description: kubuntu 19.10 with kernel 5.3.0-29-generic and64. This looks like a regression in the kernel CIFS module after the 4.15 & 5.0 kernels. These earlier kernels follow the DFS referrals without error. The problem: - Use mount.cifs with kerberos authentication to mount a samba server hosting a DFS root. You will get a KRB ticket for the "dfs_root" machine. - Attempt to access a host a host via a DFS referral (call this "target_host") - Access will fail with "Permission Denied". - Use Wireshark to monitor CIFS and KRB traffic. - The kernel attempts to authenticate to "target_host" using the KRB ticket for "dfs_root". Note: - A DFS target running Win2008R2 will reply with STATUS_MORE_PROCESSING_REQUIRED, then the kernel will get a KRB ticket for "target_host" and use it. The connection is then successful. - A DFS target running Samba 4.7.6 will reply with STATUS_LOGON_FAILURE. The connection fails. Expected Result: - Successful connection. - The kernel should get a KRB ticket for "target_host" and use it. (This is what kernels 4.15 and 5.0 do [and a Windows client]) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stephen1839 F pulseaudio /dev/snd/controlC2: stephen1839 F pulseaudio /dev/snd/controlC0: stephen1839 F pulseaudio /dev/snd/controlC1: stephen1839 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=4df5ccea-5eb4-45e3-a0b0-7b1311fdaba5 InstallationDate: Installed on 2018-11-09 (459 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Gigabyte Technology Co., Ltd. GA-MA790X-UD4P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-29-generic root=UUID=f009da0b-176e-49e6-a6a0-bb594e6754a8 ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-20 (114 days ago) UserGroups: adm bacula cdrom kvm libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10c dmi.board.name: GA-MA790X-UD4P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10c:bd09/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790X-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790X-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790X-UD4P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Cannot connect BT earphones or speakers
Oh, it's a UE BOOM. ** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Summary changed: - [Intel 7265][Regression] Cannot connect BT earphones or speakers + [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing -- 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/1869857 Title: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing Status in bluez package in Ubuntu: New Bug description: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control center, either using bluetoothctl. I've tried with previous versions of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed Additional information == $ lspci -vv -s 01:00.0 01:00.0 Network controller: Intel Corporation Wirele
[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing
Just testing my own machine again I quickly encountered a crash in bluetoothd. Do you see anything like that on your machine (run dmesg)? -- 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/1869857 Title: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing Status in bluez package in Ubuntu: New Bug description: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control center, either using bluetoothctl. I've tried with previous versions of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed Additional information == $ lspci -vv -s 01:00.0 01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
Is there anything left to do in systemd? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing
Please also try kernel 5.3 or older on 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/1869857 Title: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing Status in bluez package in Ubuntu: New Bug description: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control center, either using bluetoothctl. I've tried with previous versions of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed Additional information == $ lspci -vv -s 01:00.0 01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- P
[Kernel-packages] [Bug 1869860] [NEW] Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source
Public bug reported: I am using Ubuntu 18.04 with kernel 4.15.0-91-generic and packet bcmwl- kernel-source version 6.30.223.271+bdcom-0ubuntu5~18.04.1 from bionic- updates. Wifi BCM43228 802.11a/b/g/n [14e4:4359] is fine working. But working stops after installing ubuntu mainline kernel v5.6 (image, modules, headers-all, headers-amd64). While installing kernel there were error messages regarding dkms and no dkms-modul was built. bcmwl-kernel-source should support kernel v5.6 ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- 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/1869860 Title: Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source Status in bcmwl package in Ubuntu: New Bug description: I am using Ubuntu 18.04 with kernel 4.15.0-91-generic and packet bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu5~18.04.1 from bionic-updates. Wifi BCM43228 802.11a/b/g/n [14e4:4359] is fine working. But working stops after installing ubuntu mainline kernel v5.6 (image, modules, headers-all, headers-amd64). While installing kernel there were error messages regarding dkms and no dkms-modul was built. bcmwl-kernel-source should support kernel v5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1869860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
Hey Balint. I just added the task post ZFS upload (the upload was yesterday and I added the task this morning) so indeed, there is some work needed, part of it being in systemd. Basically, systemd isn’t capable of mounting datasets when pool names are duplicated on a machine zfs-mount-generator generates .mount units with the pool name. systemd needs to either, for all poo«ls mactching the desired name - prefers pool id matching zpool.cache - check every pools for their dataset and import the first matching one (same dataset path) - or the .mount unit should be able to import by ID and zfs-mount-generator upstream should generate a pool id somewhere in the unit file. ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Marking as invalid for systemd since there is not much pointing at systemd here. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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 gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: 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 GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1869501] Re: Bluetooth status in the Unity menu bar does not always match status in system settings
** Package changed: bluez (Ubuntu) => indicator-bluetooth (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/1869501 Title: Bluetooth status in the Unity menu bar does not always match status in system settings Status in indicator-bluetooth package in Ubuntu: New Status in unity-control-center package in Ubuntu: Invalid Bug description: When no Bluetooth device is connected and I turn off Bluetooth with the switch in the menu of the notification icon, the Bluetooth status in System Settings app is still "on" however Bluetooth seems to be off. Also, when Bluetooth is turned on, the status of a paired device may show "connection on" in the notification icon menu when it is actually not connected, as System Settings do show correctly. In this case I have to switch off and on again if I want to activate the connection. Also, I can not switch the connection to a paired device on or off with the System Settings app. The switches are grey and I can not click them, however they do always show the correct status. Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop Info: unity: 7.5.0+19.10.20190924-0ubuntu1 unity-control-center: 15.04.0+19.10.20190921-0ubuntu1 service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago Docs: man:bluetoothd(8) Main PID: 1035 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) Memory: 3.5M CGroup: /system.slice/bluetooth.service └─1035 /usr/lib/bluetooth/bluetoothd Mär 28 14:17:39 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd0: fd(22) ready Mär 28 16:46:32 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:49:02 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd1: fd(22) ready Mär 28 16:49:22 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:50:05 Abook bluetoothd[1035]: Control: Refusing unexpected connect Mär 28 16:50:08 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd2: fd(22) ready Mär 28 16:53:38 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:58:41 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:59:23 Abook bluetoothd[1035]: Control: Refusing unexpected connect Mär 28 16:59:25 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd3: fd(22) ready Bluetooth device: T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0029 Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 28 16:53:08 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-01-20 (68 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1869501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868538] Re: Focal update: v5.4.27 upstream stable release
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1868538 Title: Focal update: v5.4.27 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.27 upstream stable release from git://git.kernel.org/ Linux 5.4.27 ipv4: ensure rcu_read_lock() in cipso_v4_error() ARM: 8961/2: Fix Kbuild issue caused by per-task stack protector GCC plugin HID: add ALWAYS_POLL quirk to lenovo pixart mouse HID: google: add moonball USB id mm: slub: add missing TID bump in kmem_cache_alloc_bulk() ARM: 8958/1: rename missed uaccess .fixup section ARM: 8957/1: VDSO: Match ARMv8 timer in cntvct_functional() net: qrtr: fix len of skb_put_padto in qrtr_node_enqueue blk-mq: insert flush request to the front of dispatch queue jbd2: fix data races at struct journal_head sfc: fix timestamp reconstruction at 16-bit rollover points net: rmnet: fix packet forwarding in rmnet bridge mode net: rmnet: fix bridge mode bugs net: rmnet: use upper/lower device infrastructure net: rmnet: do not allow to change mux id if mux id is duplicated net: rmnet: remove rcu_read_lock in rmnet_force_unassociate_device() net: rmnet: fix suspicious RCU usage net: rmnet: fix NULL pointer dereference in rmnet_changelink() net: rmnet: fix NULL pointer dereference in rmnet_newlink() hinic: fix a bug of rss configuration hinic: fix a bug of setting hw_ioctxt hinic: fix a irq affinity bug net: phy: mscc: fix firmware paths slip: not call free_netdev before rtnl_unlock in slip_open signal: avoid double atomic counter increments for user accounting kbuild: add dt_binding_check to PHONY in a correct place kbuild: add dtbs_check to PHONY drm/amdgpu: fix memory leak during TDR test(v2) blk-mq: insert passthrough request into hctx->dispatch directly net: ll_temac: Handle DMA halt condition caused by buffer underrun net: ll_temac: Fix RX buffer descriptor handling on GFP_ATOMIC pressure net: ll_temac: Add more error handling of dma_map_single() calls net: ll_temac: Fix race condition causing TX hang mac80211: rx: avoid RCU list traversal under mutex net: ks8851-ml: Fix IRQ handling and locking net: usb: qmi_wwan: restore mtu min/max values after raw_ip switch scsi: libfc: free response frame from GPN_ID cfg80211: check reg_rule for NULL in handle_channel_custom() tracing: Fix number printing bug in print_synth_event() selftests/rseq: Fix out-of-tree compilation HID: hid-bigbenff: fix race condition for scheduled work during removal HID: hid-bigbenff: call hid_hw_stop() in case of error HID: hid-bigbenff: fix general protection fault caused by double kfree HID: i2c-hid: add Trekstor Surfbook E11B to descriptor override ACPI: watchdog: Set default timeout in probe HID: apple: Add support for recent firmware on Magic Keyboards ACPI: watchdog: Allow disabling WDAT at boot drm/amdgpu: Fix TLB invalidation request when using semaphore netfilter: xt_hashlimit: unregister proc file before releasing mutex netfilter: hashlimit: do not use indirect calls during gc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867656] Re: Remove linux-firmware dependency from kernel meta packages for s390x
This bug was fixed in the package linux-meta - 5.4.0.21.25 --- linux-meta (5.4.0.21.25) focal; urgency=medium * Bump ABI 5.4.0-21 * Packaging resync (LP: #1786013) - [Packaging] update variants -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 18:49:44 -0300 ** Changed in: linux-meta (Ubuntu) Status: Fix Committed => Fix Released -- 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/1867656 Title: Remove linux-firmware dependency from kernel meta packages for s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-meta package in Ubuntu: Fix Released Bug description: As far as we understand all firmware upgrades (and the firmware itself) is coming from the HMC on case of IBM Z and LinuxONE. This not only incl. the CEC code, but also all the firmware for the different cards and adapters. If this is the case (and will be in future), it would make sense for us to get rid of the linux-firmware package for s390x - this would make things leaner, reduce size and eventually increase (installation) performance ... So please IBM can you confirm that all firmware updates (MCLs) are always done via the HMC and that is therefore the linux-firmware package is obsolete on s390x? Thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868217] Re: Make Dell WD19 dock more reliable after suspend
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1868217 Title: Make Dell WD19 dock more reliable after suspend Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: Incomplete Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When Dell WD19 dock connects multiple USB3 storage devices, the USB Hub used internally may stop working after suspend. [Fix] Disable LPM on the Realtek USB Hub, and let xHCI controller make sure the link state transition is completed. [Test] After applying the patches, the Dell WD19 works reliably after thousand times for suspend/resume cycle. [Regression Potential] Low. This replaces the currently "msleep" way with more robust mechanism. I also test other systems and nothing breaks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867753] Re: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867790] Re: update-version-dkms doesn't add a BugLink
This bug was fixed in the package linux - 5.4.0-21.25
---
linux (5.4.0-21.25) focal; urgency=medium
* CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling
-- Thadeu Lima de Souza Cascardo Thu, 26 Mar
2020 17:51:28 -0300
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835
--
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/1867790
Title:
update-version-dkms doesn't add a BugLink
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
In Progress
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Status in linux source package in Focal:
Fix Released
Bug description:
== Impact ==
When there are updates on the dkms versions used for a linux build,
'update-version-dkms' saves the new version(s) in 'debian/dkms-versions' and
commits it. The commit doesn't have any BugLink, so it gets added to the debian
changelog under "* Miscellaneous Ubuntu changes".
== Fix ==
Change 'update-version-dkms' to add a BugLink to
https://bugs.launchpad.net/bugs/1786013 ("Packaging resync"), which is the bug
report being used for all the other automated commits.
== Test Case ==
In one of the main kernels, run 'update-version-dkms' and make sure it adds a
valid BugLink.
== Regression Potential ==
Low. This only changes how the automated commits are generated and later
added to the changelog.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867790/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867903] Re: Focal update: v5.4.26 upstream stable release
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1867903 Title: Focal update: v5.4.26 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.26 upstream stable release from git://git.kernel.org/ Linux 5.4.26 net/smc: cancel event worker during device removal net/smc: check for valid ib_client_data ipv6: restrict IPV6_ADDRFORM operation iommu/amd: Fix IOMMU AVIC not properly update the is_run bit in IRTE i2c: acpi: put device when verifying client fails iommu/vt-d: Ignore devices with out-of-spec domain number iommu/vt-d: Fix the wrong printing in RHSA parsing netfilter: nft_chain_nat: inet family is missing module ownership netfilter: nf_tables: dump NFTA_CHAIN_FLAGS attribute netfilter: nft_tunnel: add missing attribute validation for tunnels netfilter: nft_payload: add missing attribute validation for payload csum flags netfilter: cthelper: add missing attribute validation for cthelper perf bench futex-wake: Restore thread count default to online CPU count nl80211: add missing attribute validation for channel switch nl80211: add missing attribute validation for beacon report scanning nl80211: add missing attribute validation for critical protocol indication i2c: gpio: suppress error on probe defer iommu/vt-d: Fix RCU-list bugs in intel_iommu_init() driver code: clarify and fix platform device DMA mask allocation drm/i915/gvt: Fix unnecessary schedule timer when no vGPU exits pinctrl: core: Remove extra kref_get which blocks hogs being freed drm/i915/gvt: Fix dma-buf display blur issue on CFL virtio_ring: Fix mem leak with vring_new_virtqueue() pinctrl: imx: scu: Align imx sc msg structs to 4 pinctrl: meson-gxl: fix GPIOX sdio pins clk: imx8mn: Fix incorrect clock defines batman-adv: Don't schedule OGM for disabled interface iommu/vt-d: Fix a bug in intel_iommu_iova_to_phys() for huge page iommu/vt-d: Fix RCU list debugging warnings iommu/vt-d: dmar: replace WARN_TAINT with pr_warn + add_taint iommu/dma: Fix MSI reservation allocation x86/mce: Fix logic and comments around MSR_PPIN_CTL perf/amd/uncore: Replace manual sampling check with CAP_NO_INTERRUPT flag mt76: fix array overflow on receiving too many fragments for a packet i2c: designware-pci: Fix BUG_ON during device removal efi: Add a sanity check to efivar_store_raw() efi: Fix a race and a buffer overflow while reading efivars via sysfs x86/ioremap: Map EFI runtime services data as encrypted for SEV macintosh: windfarm: fix MODINFO regression fscrypt: don't evict dirty inodes after removing key blk-iocost: fix incorrect vtime comparison in iocg_is_idle() ipmi_si: Avoid spurious errors for optional IRQs s390/dasd: fix data corruption for thin provisioned devices fuse: fix stack use after return ARC: define __ALIGN_STR and __ALIGN symbols for ARC KVM: nVMX: avoid NULL pointer dereference with incorrect EVMCS GPAs KVM: x86: clear stale x86_emulate_ctxt->intercept value gfs2_atomic_open(): fix O_EXCL|O_CREAT handling on cold dcache cifs_atomic_open(): fix double-put on late allocation failure ktest: Add timeout for ssh sync testing pinctrl: falcon: fix syntax error mmc: sdhci-pci-gli: Enable MSI interrupt for GL975x drm/i915: Defer semaphore priority bumping to a workqueue drm/i915: be more solid in checking the alignment drm/amd/display: remove duplicated assignment to grph_obj_type workqueue: don't use wq_select_unbound_cpu() for bound works netfilter: x_tables: xt_mttg_seq_next should increase position index netfilter: xt_recent: recent_seq_next should increase position index netfilter: synproxy: synproxy_cpu_seq_next should increase position index netfilter: nf_conntrack: ct_cpu_seq_next should increase position index iommu/vt-d: quirk_ioat_snb_local_iommu: replace WARN_TAINT with pr_warn + add_taint virtio-blk: fix
[Kernel-packages] [Bug 1836030] Re: enable realtek ethernet device ASPM function
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1836030 Title: enable realtek ethernet device ASPM function Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: = SRU for 5.4 Focal kernel === [Impact] The PC state stays at PC3 if r8169 driver doesn't enable ASPM. [Fix] Applied same series of patches from v5.5-rc1 and disable ASPM L1.1 only, instead of disable ASPM completely. [Test] Verified on machines with realtek Ethernet device, the Ethernet works well after S3 test 30 times and the system can enter PC10. [Regression Potential] Low, from realtek engineer, r8169 driver supports ASPM L0s and L1, and we only disable ASPM L1.1 which is pretty safe and should be disabled by default. == SRU for 5.0 OEM OSP1 kernel = [Impact] The PC state stays at PC3 if realtek ethernet doesn't enable ASPM. [Fix] Discussed with upstream and they would like to use sysfs to toggle the ASPM link states, but the patches didn't get merged yet, so we merger them as SAUCE patches. [Test] Verified on machines with realtek ethernet device, the ethernet works well and the system can enter PC10. [Regression Potential] High. From upstream maintainer, enable realtek ethernet ASPM may lead to some serious issue, so regression is expected. Those regression should come from old realtek chips, we'll make sure all new platforms with realtek NIC have no any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858299] Re: This laptop contains a touchpadwhich is not recognized.
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1858299 Title: This laptop contains a touchpadwhich is not recognized. Status in linux package in Ubuntu: Fix Released Bug description: This laptop contains a touchpad which is not recognized. The laptop is the Trekstore Surfbook E11B. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deathmetal 1119 F pulseaudio CurrentDesktop: LXQt Date: Sat Jan 4 23:09:34 2020 InstallationDate: Installed on 2020-01-04 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TREKSTOR SURFBOOK E11B ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=c3bcb5e6-3626-422a-b348-dbdb31c269d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BIOS_V1.1.5 dmi.board.asset.tag: Default string dmi.board.name: Gemini_Lake_Celeron_V01 dmi.board.vendor: TS_EMDOOR dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBIOS_V1.1.5:bd08/30/2018:svnTREKSTOR:pnSURFBOOKE11B:pvrDefaultstring:rvnTS_EMDOOR:rnGemini_Lake_Celeron_V01:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Surfbook dmi.product.name: SURFBOOK E11B dmi.product.sku: NFCN4SW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859269] Re: [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE kernel branch
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1859269 Title: [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] roce patchset have merged into mainline 5.5rc6 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] RDMA/hns: Delete unnecessary callback functions for cq RDMA/hns: Rename the functions used inside creating cq RDMA/hns: Redefine the member of hns_roce_cq struct RDMA/hns: Redefine interfaces used in creating cq IB/umem: remove the dmasync argument to ib_umem_get RDMA/hns: Modify appropriate printings RDMA/hns: Fix non-standard error codes RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code RDMA/hns: Simplify doorbell initialization code RDMA/hns: Replace not intuitive function/macro names RDMA/hns: Modify fields of struct hns_roce_srq RDMA/hns: Delete unnecessary uar from hns_roce_cq RDMA/hns: Remove unnecessary structure hns_roce_sqp RDMA/hns: Delete unnecessary variable max_post RDMA/hns: Remove unsupported modify_port callback RDMA: Connect between the mmap entry and the umap_priv structure RDMA/hns: Fix build error again RDMA/hns: Fix memory leak on 'context' on error return path RDMA/hns: Bugfix for qpc/cqc timer configuration RDMA/hns: Fix to support 64K page for srq RDMA/hns: Delete BITS_PER_BYTE redefinition RDMA/hns: Prevent undefined behavior in hns_roce_set_user_sq_size() RDMA/hns: Release qp resources when failed to destroy qp RDMA/hns: Fix a spelling mistake in a macro RDMA/hns: Modify return value of restrack functions RDMA/hns: Modify variable/field name from vlan to vlan_id RDMA/hns: Fix wrong parameters when initial mtt of srq->idx_que RDMA/hns: remove a redundant le16_to_cpu RDMA/hns: Prevent memory leaks of eq->buf_list RDMA/hns: Correct the value of srq_desc_size RDMA/hns: Correct the value of HNS_ROCE_HEM_CHUNK_LEN RDMA/hns: Add support for reporting wc as software mode RDMA/hns: Bugfix for posting a wqe with sge RDMA/hns: Fix coding style issues RDMA/hns: Replace custom macros HNS_ROCE_ALIGN_UP RDMA/hns: Remove redundant print information RDMA/hns: Delete unnessary parameters in hns_roce_v2_qp_modify() RDMA/hns: Update the value of qp type RDMA/hns: Remove unused function hns_roce_init_eq_table() RDMA/hns: Avoid printing address of mtt page RDMA/hns: Simplify the calculation and usage of wqe idx for post verbs update 01120 RDMA/hns: Get pf capabilities from firmware RDMA/hns: Add interfaces to get pf capabilities from firmware RDMA/hns: Remove some redundant variables related to capabilities RDMA/hns: Add support for extended atomic in userspace [Status] (Fix committed): RDMA/hns: Delete unnecessary callback functions for cq (Fix committed): RDMA/hns: Rename the functions used inside creating cq (Fix committed): RDMA/hns: Redefine the member of hns_roce_cq struct (Fix committed): RDMA/hns: Redefine interfaces used in creating cq (Fix committed): IB/umem: remove the dmasync argument to ib_umem_get (Fix committed): RDMA/hns: Modify appropriate printings (Fix committed): RDMA/hns: Fix non-standard error codes (Fix committed): RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code (Fix committed): RDMA/hns: Simplify doorbell initialization code (Fix committed): RDMA/hns: Replace not intuitive function/macro names (Fix committed): RDMA/hns: Modify fields of struct hns_roce_srq (Fix committed): RDMA/hns: Delete unnecessary uar from hns_roce_cq (Fix committed): RDMA/hns: Remove unnecessary structure hns_roce_sqp (Fix committed): RDMA/hns: Delete unnecessary variable max_post (Fix committed): RDMA/hns: Remove unsupported modify_port callback (Fix committed): RDMA: Connect between the mmap entry and the umap_priv structure (Fix committed): RDMA/hns: Fix build error again (Fix committed): RDMA/hns: Fix memory leak on 'context' on error return path (Fix committed): R
[Kernel-packages] [Bug 1866734] Re: All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1866734 Title: All PS/2 ports on PS/2 Serial add-in bracket are not working after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: New Status in linux-oem source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] PS/2 ports on PS/2 Serial add-in card do not work after S3. [Fix] The i8042 controller selftest fails while resuming, adding retry fix this issue. [Test] Verified on the target machine, the ps/2 keyboard keeps working after S3 test 30 times. [Regression Potential] Low, there is a retry logic in controller selftest, but it returns directly if it fails to communicate with the controller. This commit make it retry 5 times before return fails. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1866734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867178] Re: Focal update: v5.4.25 upstream stable release
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1867178 Title: Focal update: v5.4.25 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.25 upstream stable release from git://git.kernel.org/ Linux 5.4.25 drm/virtio: module_param_named() requires linux/moduleparam.h csky: Implement copy_thread_tls block, bfq: remove ifdefs from around gets/puts of bfq groups block, bfq: get a ref to a group when adding it to a service tree efi: READ_ONCE rng seed size before munmap efi/x86: Handle by-ref arguments covering multiple pages in mixed mode efi/x86: Align GUIDs to their size in the mixed mode runtime wrapper powerpc: fix hardware PMU exception bug on PowerVM compatibility mode systems EDAC/synopsys: Do not print an error with back-to-back snprintf() calls bus: ti-sysc: Fix 1-wire reset quirk arm64: dts: meson: fix gxm-khadas-vim2 wifi dmaengine: coh901318: Fix a double lock bug in dma_tc_handle() dma-buf: free dmabuf->name in dma_buf_release() hwmon: (adt7462) Fix an error return in ADT7462_REG_VOLT() ARM: dts: imx7-colibri: Fix frequency for sd/mmc ARM: dts: dra7xx-clocks: Fixup IPU1 mux clock parent source ARM: dts: am437x-idk-evm: Fix incorrect OPP node names ARM: imx: build v7_cpu_resume() unconditionally IB/hfi1, qib: Ensure RCU is locked when accessing list RMDA/cm: Fix missing ib_cm_destroy_id() in ib_cm_insert_listen() regulator: stm32-vrefbuf: fix a possible overshoot when re-enabling RDMA/core: Fix protection fault in ib_mr_pool_destroy RDMA/iwcm: Fix iwcm work deallocation RDMA/siw: Fix failure handling during device creation RDMA/nldev: Fix crash when set a QP to a new counter but QPN is missing RDMA/rw: Fix error flow during RDMA context initialization Revert "RDMA/cma: Simplify rdma_resolve_addr() error flow" soc: imx-scu: Align imx sc msg structs to 4 firmware: imx: Align imx_sc_msg_req_cpu_start to 4 firmware: imx: scu-pd: Align imx sc msg structs to 4 firmware: imx: misc: Align imx sc msg structs to 4 arm64: dts: imx8qxp-mek: Remove unexisting Ethernet PHY ARM: dts: imx6: phycore-som: fix emmc supply phy: mapphone-mdm6600: Fix write timeouts with shorter GPIO toggle interval phy: mapphone-mdm6600: Fix timeouts by adding wake-up handling drm/i915/selftests: Fix return in assert_mmap_offset() drm/i915: Program MBUS with rmw during initialization drm/sun4i: de2/de3: Remove unsupported VI layer formats drm/sun4i: Fix DE2 VI layer format support drm/sun4i: Add separate DE3 VI layer formats drm: kirin: Revert "Fix for hikey620 display offset problem" drm/panfrost: Don't try to map on error faults spi: atmel-quadspi: fix possible MMIO window size overrun ASoC: dapm: Correct DAPM handling of active widgets during shutdown ASoC: Intel: Skylake: Fix available clock counter incrementation ASoC: pcm512x: Fix unbalanced regulator enable call in probe error path ASoC: pcm: Fix possible buffer overflow in dpcm state sysfs output powerpc/mm: Fix missing KUAP disable in flush_coherent_icache() powerpc: Convert flush_icache_range & friends to C powerpc: define helpers to get L1 icache sizes ASoC: intel: skl: Fix possible buffer overflow in debug outputs ASoC: intel: skl: Fix pin debug prints ASoC: SOF: Fix snd_sof_ipc_stream_posn() ASoC: topology: Fix memleak in soc_tplg_manifest_load() ASoC: topology: Fix memleak in soc_tplg_link_elems_load() drm/virtio: fix resource id creation race drm/virtio: make resource id workaround runtime switchable. spi: bcm63xx-hsspi: Really keep pll clk enabled ARM: dts: ls1021a: Restore MDIO compatible to gianfar arm64: dts: meson-sm1-sei610: add missing interrupt-names dm: fix congested_fn for request-based device dm zoned: Fix reference counter initial value of chunk works dm writecache: verify watermark during resume dm: report suspended devic
[Kernel-packages] [Bug 1867109] Re: [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1867109 Title: [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: virtio-blk disks can go dissfunctional when swiotlb fills up virtio-blk hw queue gets possibly permanently stopped when swiotlb full For example, with a PV guest choose a small swiotlb (30MB) and create IO load on several virtio-blk disks simultaneously. It actually should not matter what causes the swiotlb pressure (can be virtio-net as well). Fixes posted upstream: https://lkml.org/lkml/2020/2/13/306 We will need backports to support Protected Virtualization. IBM verified that the patches apply cleanly on focal/master-next, upstream commit ids for reference: commit bab7e6f05699a481787f7659c4f766dd87187dae Author: Halil Pasic Date: Thu Feb 13 13:37:27 2020 +0100 virtio-blk: fix hw_queue stopped on arbitrary error commit 24506976aec92052e9fe328146a2e574a1190986 Author: Halil Pasic Date: Thu Feb 13 13:37:28 2020 +0100 virtio-blk: improve virtqueue error to BLK_STS Also applies cleanly on 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1867109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835531] Re: [20.04 FEAT] Base KVM setup for secure guests - kernel part
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780590] Re: Add support for Realtek 8723DE wireless adapter
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1780590 Title: Add support for Realtek 8723DE wireless adapter Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux-firmware source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] There's no in-kernel support for Realtek 8723DE, so users need to use out-of-tree DKMS which is not from Ubuntu archive. This has security implication and should be avoided. Also this provides pretty bad user experience. [Fix] Add support to Realtek 8723DE. All commits are cherry-picked from Realtek maintained repo: https://github.com/rtlwifi-linux/rtw88_8723de [Test] With the patch series applied, 8723DE can scan and connect to APs succesfully. Also did some S3 smoke test, it continues to work. [Regression Potential] Low. The device in question was never supported, and if there's any regression, we can count on Realtek Wireless team, thy are now pretty responsive on upstream mailing list. === Original Bug Report === recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. Everything in the installation was fine until the moment to start session. The problem is that the wireless network card does not detect me and when entering the configuration I simply get an error message saying that no wireless adapter was found. I have already followed all the tutorials I found on the web. and update the driver of a github repository, and install how much program they told me to install and I still can not connect via wifi. I just do not know what to do. I have a laptop hp 14-bs004 came with windows 10 installed. The information on the network card is as follows: Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: d723] Subsystem: Hewlett-Packard Company Device [103c: 8319] Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort- SERR- Kernel modules: wl already install the most recent kernel, already intale driver driver realtek rtl8723be according to the instructions of the git repository. and nothing has worked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 22:57:40 2018 InstallationDate: Installed on 2018-07-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1780590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. [FIXES] These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement All are clean cherry picks into the 5.4 branch and can be pulled from my branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1864484-smartpqi-to-1.2.10-025 [TESTING] modinfo for smartpqi should show: version:1.2.10-025 description:Driver for Microsemi Smart Family Controller version 1.2.10-025 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866772] Re: Sys oopsed with sysfs test in ubuntu_stress_smoke_test on X-hwe ARM64
This bug was fixed in the package linux - 5.4.0-21.25
---
linux (5.4.0-21.25) focal; urgency=medium
* CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling
-- Thadeu Lima de Souza Cascardo Thu, 26 Mar
2020 17:51:28 -0300
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835
--
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/1866772
Title:
Sys oopsed with sysfs test in ubuntu_stress_smoke_test on X-hwe ARM64
Status in Stress-ng:
New
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Incomplete
Status in linux source package in Eoan:
Incomplete
Status in linux source package in Focal:
Fix Released
Bug description:
== SRU Request [ BIONIC, EOAN, FOCAL ] ==
Reading /sys/firmware/acpi/tables/data/BERT as root at at odd byte
offset will cause an oops. This is because the source address is I/O
mapped and this needs to be read with an I/O memcpy rather than an
memcpy.
== Fix ==
The fix is upstream (linux-next) commit that will land in 5.7, the
backport to bionic, eoan and focal is just a minor context wiggle.
commit 08c07cefb3042a55bc9f8243814b504d5eff93f3
Author: Colin Ian King
Date: Thu Mar 12 11:13:45 2020 +
ACPI: sysfs: copy ACPI data using io memory copying
== Test ==
Running on hotdog with the reproducer below (run as root):
#include
#include
#include
#include
#include
#include
#include
int main(void)
{
int fd;
char buffer[3];
ssize_t n;
fd = open("/sys/firmware/acpi/tables/data/BERT", O_RDONLY);
if (fd < 0) {
fprintf(stderr, "open failed: %d (%s)\n", errno,
strerror(errno));
return -1;
}
do {
n = read(fd, buffer, sizeof(buffer));
} while (n > 0);
return 0;
}
Without the fix it will oops. With the fix it works OK.
== Regession Potential ==
This only affects the reading of the ACPI BERT table from /sys as root
so it is limited in scope to just a very narrow use case. Normally the
BERT table is just handled by the kernel, so access to this table is
just for debugging purposes.
---
Issue found on new ARM64 node "hotdog" 4.15.0-91.92~16.04.1
Failed 2 of 2 attempts.
Test suite HEAD SHA1: 3f43e81
sysfs STARTING
sysfs RETURNED 0
sysfs FAILED (kernel oopsed)
[ 1075.760640] Unable to handle kernel paging request at virtual address
4a70072a
[ 1075.763319] Unable to handle kernel paging request at virtual address
4a70e4ba
[ 1075.768563] Mem abort info:
[ 1075.768566] ESR = 0x9621
[ 1075.768568] Exception class = DABT (current EL), IL = 32 bits
[ 1075.768569] SET = 0, FnV = 0
[ 1075.768570] EA = 0, S1PTW = 0
[ 1075.768571] Data abort info:
[ 1075.768577] ISV = 0, ISS = 0x0021
[ 1075.776489] Mem abort info:
[ 1075.776491] ESR = 0x9621
[ 1075.776493] Exception class = DABT (current EL), IL = 32 bits
[ 1075.776494] SET = 0, FnV = 0
[ 1075.776495] EA = 0, S1PTW = 0
[ 1075.776496] Data abort info:
[ 1075.776500] ISV = 0, ISS = 0x0021
[ 1075.779284] CM = 0, WnR = 0
[ 1075.779288] swapper pgtable: 4k pages, 48-bit VAs, pgd = facfed4f
[ 1075.779290] [4a70072a] *pgd=00bffcffe003,
*pud=009f6122c003, *pmd=00bf5adf4003, *pte=006880280703
[ 1075.782342] CM = 0, WnR = 0
[ 1075.782346] swapper pgtable: 4k pages, 48-bit VAs, pgd = facfed4f
[ 1075.782352] [4a70e4ba] *pgd=00bffcffe003,
*pud=009f6122c003, *pmd=00bf5adf4003, *pte=00688028e703
[ 1075.788262] Internal error: Oops: 9621 [#2] SMP
[ 1075.788269] Modules linked in: unix_diag binfmt_misc snd_seq
snd_seq_device snd_timer snd soundcore userio vfio_iommu_type1 vfio hci_vhci
bluetooth ecdh_generic uhid cuse vhost_vsock vmw_vsock_virtio_transport_common
vhost_net vhost vsock tap dccp_ipv4 dccp ipx p8023 atm psnap p8022 llc
algif_rng algif_aead anubis fcrypt khazad seed tea md4 michael_mic
poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic tgr192
wp512 algif_hash chacha20_neon chacha20_generic blowfish_generic
blowfish_common cast5_generic des_generic salsa20_generic camellia_generic
cast6_generic cast_common serpent_generic twofish_generic twofish_common
algif_skcipher af_alg nls_iso8859_1 ipmi_ssif ipmi_devintf joydev input_leds
ipmi_msghandler shpchp i2c_xlp9xx(+) thunderx2_pmu ib_iser rdma_cm iw_cm ib_cm
ib_core
[ 1075.942470] iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4
btrfs zstd_compress raid10 raid456 async_raid6_recov
[Kernel-packages] [Bug 1864442] Re: dmaengine: hisilicon: Add Kunpeng DMA engine support
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1864442 Title: dmaengine: hisilicon: Add Kunpeng DMA engine support Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] This patch adds a driver for HiSilicon Kunpeng DMA engine. This DMA engine which is an PCIe iEP offers 30 channels, each channel has a send queue, a complete queue and an interrupt to help to do tasks. This DMA engine can do memory copy between memory blocks or between memory and device buffer [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] e9f08b65250d dmaengine: hisilicon: Add Kunpeng DMA engine support https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/dma?h=v5.6-rc1&id=e9f08b65250d73ab70e79e194813f52b8d306784 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1864442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu Focal) Status: Triaged => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [ 911.413625] Restarting tasks ... done. [ 911.462021] PM: suspend exit It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867099] Re: please help enable CONFIG_EROFS_FS_ZIP
This bug was fixed in the package linux - 5.4.0-21.25 --- linux (5.4.0-21.25) focal; urgency=medium * CVE-2020-8835 - SAUCE: bpf: undo incorrect __reg_bound_offset32 handling -- Thadeu Lima de Souza Cascardo Thu, 26 Mar 2020 17:51:28 -0300 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835 -- 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/1867099 Title: please help enable CONFIG_EROFS_FS_ZIP Status in linux package in Ubuntu: Fix Released Bug description: Greeting, It seems that the Ubuntu configuration for EROFS file system disables compression support, which is not the current default option.. Therefore, I'd recommand the following default options, please help apply them from linux kernel 5.4+. CONFIG_EROFS_FS=m # CONFIG_EROFS_FS_DEBUG is not set CONFIG_EROFS_FS_XATTR=y CONFIG_EROFS_FS_POSIX_ACL=y CONFIG_EROFS_FS_SECURITY=y CONFIG_EROFS_FS_ZIP=y CONFIG_EROFS_FS_CLUSTER_PAGE_LIMIT=1 Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867656] Re: Remove linux-firmware dependency from kernel meta packages for s390x
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- 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/1867656 Title: Remove linux-firmware dependency from kernel meta packages for s390x Status in Ubuntu on IBM z Systems: Fix Released Status in linux-meta package in Ubuntu: Fix Released Bug description: As far as we understand all firmware upgrades (and the firmware itself) is coming from the HMC on case of IBM Z and LinuxONE. This not only incl. the CEC code, but also all the firmware for the different cards and adapters. If this is the case (and will be in future), it would make sense for us to get rid of the linux-firmware package for s390x - this would make things leaner, reduce size and eventually increase (installation) performance ... So please IBM can you confirm that all firmware updates (MCLs) are always done via the HMC and that is therefore the linux-firmware package is obsolete on s390x? Thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867753] Re: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal
** Changed in: ubuntu-z-systems Status: Fix Committed => 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/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature
With LP 1835531 now Fix Released, I'm changing the kernel entry of this ticket also to Fix Released - and with that the project entry, too. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => 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/1866866 Title: [FFe] Please accept patches for secure guest feature Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: Fix Released Bug description: The secure guest feature (aka protvirt) affects multiple components (kernel, qemu and s390-tools - see below). While dedicated tickets for the different components exist since quite a while, the code arrived late and/or discussion to get it upstream accepted took longer than expected. (Even if we as of today didn't reached the kernel freeze, I'm already adding kernel to this FFe.) Since this is a very important feature the current IBM Z and LinuxONE family, it's requested to be included into focal, the next LTS release, to become exploitable by long running systems. The code is largely architecture specific. No brand new packages or new upstream version are requested, only the cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able. kernel: The patch set for the kernel is huge (30+ commits), but has only one common code patch (two files). The arch specific patches landed in between in linux-next, the arch specific one is expected to land there very soon (hours/days from now). The common-code patch ran through several hands and landed in between in Andrew Morton's mmots tree. A pre-screening of the code was done by the kernel team and it looked acceptable. (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531) qemu: The entire code seems to be arch specific. Again a pre-screening of the maintainer lead to the fact that it should be acceptable, too. (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546) s390-tools: The entire tool only exists for the s390x architecture. Hence obviously everything is arch specific on that. (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534) Currently work is going on to test this function end to end based on Ubuntu components (means based on our s390-tools, qemu and kernel [focal master-next] trees). On top I applied the patches to the packages as well and did manual test buids. With that a potential regression can be considered as low - and even in case of a regression, it will affect s390x only. The patches are being staged for this feature in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867109] Re: [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up
** Changed in: ubuntu-power-systems Status: Fix Committed => 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/1867109 Title: [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: virtio-blk disks can go dissfunctional when swiotlb fills up virtio-blk hw queue gets possibly permanently stopped when swiotlb full For example, with a PV guest choose a small swiotlb (30MB) and create IO load on several virtio-blk disks simultaneously. It actually should not matter what causes the swiotlb pressure (can be virtio-net as well). Fixes posted upstream: https://lkml.org/lkml/2020/2/13/306 We will need backports to support Protected Virtualization. IBM verified that the patches apply cleanly on focal/master-next, upstream commit ids for reference: commit bab7e6f05699a481787f7659c4f766dd87187dae Author: Halil Pasic Date: Thu Feb 13 13:37:27 2020 +0100 virtio-blk: fix hw_queue stopped on arbitrary error commit 24506976aec92052e9fe328146a2e574a1190986 Author: Halil Pasic Date: Thu Feb 13 13:37:28 2020 +0100 virtio-blk: improve virtqueue error to BLK_STS Also applies cleanly on 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1867109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835531] Re: [20.04 FEAT] Base KVM setup for secure guests - kernel part
** Changed in: ubuntu-z-systems Status: Fix Committed => 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/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815588] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1815588
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1815588
Title:
speed mismatch trying to attach usb device to guest vm
Status in libvirt package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Distro: 18.04.02, just recently upgraded from 16.04
MachineType: LENOVO 20J7S02N00
All of the machines USB ports are USB 3.0
I added the USB drive from virt-managers UI. Trying to start the guest
vm results in:
Error starting domain: internal error: process exited while connecting to
monitor: 2019-02-12T11:12:16.334471Z qemu-system-x86_64: -device
usb-host,hostbus=2,hostaddr=2,id=hostdev0,bus=usb.0,port=1: Warning: speed
mismatch trying to attach usb device "Porsche Desktop" (super speed) to bus
"usb.0", port "1" (full+high speed)
2019-02-12T11:12:16.485645Z qemu-system-x86_64: -device
usb-host,hostbus=2,hostaddr=2,id=hostdev0,bus=usb.0,port=1: failed to open host
usb device 2:2
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in
newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1508, in startup
self._backend.create()
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1062, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor:
2019-02-12T11:12:16.334471Z qemu-system-x86_64: -device
usb-host,hostbus=2,hostaddr=2,id=hostdev0,bus=usb.0,port=1: Warning: speed
mismatch trying to attach usb device "Porsche Desktop" (super speed) to bus
"usb.0", port "1" (full+high speed)
2019-02-12T11:12:16.485645Z qemu-system-x86_64: -device
usb-host,hostbus=2,hostaddr=2,id=hostdev0,bus=usb.0,port=1: failed to open host
usb device 2:2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1815588/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815588] Re: speed mismatch trying to attach usb device to guest vm
Thanks David, so it might be issues with special HW types.
I'm glad you identified quirks to loas uas with to mitigate the issue - this
might help others being affected.
But until I have a local reproducer to debug in-depth I'm not sure I can
do more on the libvirt side (and even then no promises if it ends up to
be very HW/FW specific).
I'll add a kernel tasks just in case this might be known over there from
the USB storage POV.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: bot-stop-nagginf
** Tags removed: bot-stop-nagginf
** Tags added: bot-stop-nagging
--
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/1815588
Title:
speed mismatch trying to attach usb device to guest vm
Status in libvirt package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Distro: 18.04.02, just recently upgraded from 16.04
MachineType: LENOVO 20J7S02N00
All of the machines USB ports are USB 3.0
I added the USB drive from virt-managers UI. Trying to start the guest
vm results in:
Error starting domain: internal error: process exited while connecting to
monitor: 2019-02-12T11:12:16.334471Z qemu-system-x86_64: -device
usb-host,hostbus=2,hostaddr=2,id=hostdev0,bus=usb.0,port=1: Warning: speed
mismatch trying to attach usb device "Porsche Desktop" (super speed) to bus
"usb.0", port "1" (full+high speed)
2019-02-12T11:12:16.485645Z qemu-system-x86_64: -device
usb-host,hostbus=2,hostaddr=2,id=hostdev0,bus=usb.0,port=1: failed to open host
usb device 2:2
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in
newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1508, in startup
self._backend.create()
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1062, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor:
2019-02-12T11:12:16.334471Z qemu-system-x86_64: -device
usb-host,hostbus=2,hostaddr=2,id=hostdev0,bus=usb.0,port=1: Warning: speed
mismatch trying to attach usb device "Porsche Desktop" (super speed) to bus
"usb.0", port "1" (full+high speed)
2019-02-12T11:12:16.485645Z qemu-system-x86_64: -device
usb-host,hostbus=2,hostaddr=2,id=hostdev0,bus=usb.0,port=1: failed to open host
usb device 2:2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1815588/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867656] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-03-31 07:30 EDT--- IBM Bugzilla status-> closed, Fix Released with 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/1867656 Title: Remove linux-firmware dependency from kernel meta packages for s390x Status in Ubuntu on IBM z Systems: Fix Released Status in linux-meta package in Ubuntu: Fix Released Bug description: As far as we understand all firmware upgrades (and the firmware itself) is coming from the HMC on case of IBM Z and LinuxONE. This not only incl. the CEC code, but also all the firmware for the different cards and adapters. If this is the case (and will be in future), it would make sense for us to get rid of the linux-firmware package for s390x - this would make things leaner, reduce size and eventually increase (installation) performance ... So please IBM can you confirm that all firmware updates (MCLs) are always done via the HMC and that is therefore the linux-firmware package is obsolete on s390x? Thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: systemd (Ubuntu) Status: Invalid => Confirmed ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu) Status: Invalid => Incomplete -- 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 gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: 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 GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.n
[Kernel-packages] [Bug 1867109] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-03-31 07:44 EDT--- IBM Buzgilla status-> closed, Fix Released with 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/1867109 Title: [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: virtio-blk disks can go dissfunctional when swiotlb fills up virtio-blk hw queue gets possibly permanently stopped when swiotlb full For example, with a PV guest choose a small swiotlb (30MB) and create IO load on several virtio-blk disks simultaneously. It actually should not matter what causes the swiotlb pressure (can be virtio-net as well). Fixes posted upstream: https://lkml.org/lkml/2020/2/13/306 We will need backports to support Protected Virtualization. IBM verified that the patches apply cleanly on focal/master-next, upstream commit ids for reference: commit bab7e6f05699a481787f7659c4f766dd87187dae Author: Halil Pasic Date: Thu Feb 13 13:37:27 2020 +0100 virtio-blk: fix hw_queue stopped on arbitrary error commit 24506976aec92052e9fe328146a2e574a1190986 Author: Halil Pasic Date: Thu Feb 13 13:37:28 2020 +0100 virtio-blk: improve virtqueue error to BLK_STS Also applies cleanly on 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1867109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835531] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-03-31 07:31 EDT--- IBM Bugzilla status->closed, Fix Released with 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/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859538] Re: Harrison Peak wifi / BT support
My last question is for TGL. -- 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/1859538 Title: Harrison Peak wifi / BT support Status in intel: Won't Fix Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: Description: HrP2 will be supported in CML/TGL platform. Target Release: 20.04 Target Kernel: 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1859538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867753] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-03-31 07:45 EDT--- IBM Bugzilla status-> closed, Fix Released with 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/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859538] Re: Harrison Peak wifi / BT support
Had BT been tested as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859538 Title: Harrison Peak wifi / BT support Status in intel: Won't Fix Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: Description: HrP2 will be supported in CML/TGL platform. Target Release: 20.04 Target Kernel: 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1859538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869823] Re: No sound after kernel update
*** This bug is a duplicate of bug 1869799 *** https://bugs.launchpad.net/bugs/1869799 some fixing patches are in the 5.3.0-43, but somehow they are not in the 5.3.0-45. I just checked the 5.3.0-46, those patches are in the -46 kernel. So please use -43 kernel or wait for -46 kernel. ** This bug has been marked a duplicate of bug 1869799 no sound driver since 5.3.0.42 kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869823 Title: No sound after kernel update Status in linux package in Ubuntu: Confirmed Bug description: With the -45 kernel, sound output and input are unavailable. Output shows a Dummy device, no Input devices. This is a regression from the -40 kernel where the Output was working (no Input though). Attempted to use SOF, i.e. the fix mentioned in https://github.com/thesofproject/linux/issues/1877 This results in system freezes, failed boots, and failure to wake from sleep. Edit: I have now noticed that it fails to wake from sleep in general with this kernel. Even without the SOF driver. Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 lspci: https://pastebin.com/6ft2qvTT dmesg: https://pastebin.com/4DLg6wy4 Thanks, Matt --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-03-17 (13 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: gpd0 no wireless extensions. wlp0s20f3 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Inspiron 7591 2n1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=df0d1f5a-7ff4-440f-bac3-f31750947cd4 ro quiet splash acpi_osi=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-45-generic N/A linux-backports-modules-5.3.0-45-generic N/A linux-firmware1.187 Tags: tricia Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0NNW5N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd12/24/2019:svnDellInc.:pnInspiron75912n1:pvr:rvnDellInc.:rn0NNW5N:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 2n1 dmi.product.sku: 0950 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
some fixing patches are in the 5.3.0-43, but somehow they are not in the 5.3.0-45. I just checked the 5.3.0-46, those patches are in the -46 kernel. So please use -43 kernel or wait for -46 kernel. -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel
some fixing patches are in the 5.3.0-43, but somehow they are not in the 5.3.0-45. I just checked the 5.3.0-46, those patches are in the -46 kernel. So please use -43 kernel or wait for -46 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869799 Title: no sound driver since 5.3.0.42 kernel Status in linux package in Ubuntu: Incomplete Bug description: no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the problem. i have only a dummy soundcard. no sound. 5.3.0.42 kernel works fine. my sound card is intel 100 / c230 hd audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 711397] Re: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade due to unsupported hardware
** Changed in: b43-fwcutter (Ubuntu) Assignee: (unassigned) => barman (barman-v) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/711397 Title: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade due to unsupported hardware Status in b43-fwcutter package in Ubuntu: Fix Released Bug description: All of the bug reports collected here deal with the package installation failing due to unsupported hardware. Binary package hint: b43-fwcutter it failed ProblemType: PackageDistroRelease: Ubuntu 11.04 Package: firmware-b43legacy-installer 4.178.10.4-5 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Tue Feb 1 11:55:39 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: allSourcePackage: b43-fwcutter Title: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/711397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856900] Re: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
I've manually re-run the tests on 5.4.0-18-generic on modoc several times and can't trip this issue. Is it possible to re-run all tests again to see if it fails when run from the test infrastructure? -- 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/1856900 Title: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12 Status in linux package in Ubuntu: Incomplete Bug description: During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops. 16:20:34 DEBUG| [stdout] sysinfo STARTING 16:20:39 DEBUG| [stdout] sysinfo RETURNED 0 16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed) 16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c000c25ffce0) - exploit attempt? (uid: 0) 16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch 16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1] 16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries 16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_virtio_transport_common vsock zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) userio zcommon(PO) znvpair(PO) cuse spl(O) kvm_pr kvm snd_seq snd_seq_device snd_timer snd soundcore hci_vhci bluetooth ecdh_generic ecc uhid hid vhost_net vhost tap atm algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher aufs sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat ip6_tables iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 algif_hash af_alg ip_vti ip6_vti fou6 sit ipip tunnel4 fou geneve act_mirred cls_basic esp6 authenc echainiv 16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk] 16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5.4.0-9-generic #12-Ubuntu 16:20:39 DEBUG| [stdout] [ 6521.209457] NIP: c000c25ffce0 LR: c063f058 CTR: c000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.209528] REGS: c00109703810 TRAP: 0400 Tainted: P OE (5.4.0-9-generic) 16:20:39 DEBUG| [stdout] [ 6521.209608] MSR: 800010009033 CR: 88002440 XER: 2000 16:20:39 DEBUG| [stdout] [ 6521.209681] CFAR: c063f054 IRQMASK: 0 16:20:39 DEBUG| [stdout]GPR00: c063f034 c00109703aa0 c1a4bb00 c0007cef3000 16:20:39 DEBUG| [stdout]GPR04: c000c25ffc18 16:20:39 DEBUG| [stdout]GPR08: 16:20:39 DEBUG| [stdout]GPR12: c000c25ffce0 c0003fffee00 79b6987b4410 16:20:39 DEBUG| [stdout]GPR16: 79b698b3 79b6987b0320 79b69771f240 79b6987b4420 16:20:39 DEBUG| [stdout]GPR20: 79b6880010a0 79b698a4d3a0 16:20:39 DEBUG| [stdout]GPR24: c00109d56cc0 c001fde0cd8c c000c25ffce0 c00109d56ca0 16:20:39 DEBUG| [stdout]GPR28: c00109d56cc0 c0007cef3000 c00109d56c90 16:20:39 DEBUG| [stdout] [ 6521.210276] NIP [c000c25ffce0] 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.210355] LR [c063f058] fuse_request_end+0x128/0x2f0 16:20:39 DEBUG| [stdout] [ 6521.210423] Call Trace: 16:20:39 DEBUG| [stdout] [ 6521.210448] [c00109703aa0] [c063f034] fuse_request_end+0x104/0x2f0 (unreliable) 16:20:39 DEBUG| [stdout] [ 6521.210520] [c00109703af0] [c0642ebc] fuse_dev_do_write+0x2cc/0x5c0 16:20:39 DEBUG| [stdout] [ 6521.210591] [c00109703b70] [c0643654] fuse_dev_write+0x74/0xd0 16:20:39 DEBUG| [stdout
[Kernel-packages] [Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
I am testing with Linux Kernel 5.5.13-050513-generic from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.13/ as older kernels (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954817#17 ** Bug watch added: Debian Bug tracker #954817 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954817 -- 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/1868551 Title: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4 Status in linux package in Ubuntu: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmid
[Kernel-packages] [Bug 1239459]
Download Apps and Games on your PC Windows and Mac https://www.newsforpc.com/ If you want to download and watch movies and tv shows free than click this https://www.helpsforpc.com/ and download all your favorite movies. -- 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/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago) dmi.bios.date: 09/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1239459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859538] Re: Harrison Peak wifi / BT support
only wifi is checked. -- 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/1859538 Title: Harrison Peak wifi / BT support Status in intel: Won't Fix Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: Description: HrP2 will be supported in CML/TGL platform. Target Release: 20.04 Target Kernel: 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1859538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856900] Re: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
I don't see that the sysinfo stressor runs at all in the logs for 5.4.0-21: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/ppc64el/l/linux/20200331_002447_e28f4@/log.gz -- 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/1856900 Title: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12 Status in linux package in Ubuntu: Incomplete Bug description: During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops. 16:20:34 DEBUG| [stdout] sysinfo STARTING 16:20:39 DEBUG| [stdout] sysinfo RETURNED 0 16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed) 16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c000c25ffce0) - exploit attempt? (uid: 0) 16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch 16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1] 16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries 16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_virtio_transport_common vsock zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) userio zcommon(PO) znvpair(PO) cuse spl(O) kvm_pr kvm snd_seq snd_seq_device snd_timer snd soundcore hci_vhci bluetooth ecdh_generic ecc uhid hid vhost_net vhost tap atm algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher aufs sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat ip6_tables iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 algif_hash af_alg ip_vti ip6_vti fou6 sit ipip tunnel4 fou geneve act_mirred cls_basic esp6 authenc echainiv 16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk] 16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5.4.0-9-generic #12-Ubuntu 16:20:39 DEBUG| [stdout] [ 6521.209457] NIP: c000c25ffce0 LR: c063f058 CTR: c000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.209528] REGS: c00109703810 TRAP: 0400 Tainted: P OE (5.4.0-9-generic) 16:20:39 DEBUG| [stdout] [ 6521.209608] MSR: 800010009033 CR: 88002440 XER: 2000 16:20:39 DEBUG| [stdout] [ 6521.209681] CFAR: c063f054 IRQMASK: 0 16:20:39 DEBUG| [stdout]GPR00: c063f034 c00109703aa0 c1a4bb00 c0007cef3000 16:20:39 DEBUG| [stdout]GPR04: c000c25ffc18 16:20:39 DEBUG| [stdout]GPR08: 16:20:39 DEBUG| [stdout]GPR12: c000c25ffce0 c0003fffee00 79b6987b4410 16:20:39 DEBUG| [stdout]GPR16: 79b698b3 79b6987b0320 79b69771f240 79b6987b4420 16:20:39 DEBUG| [stdout]GPR20: 79b6880010a0 79b698a4d3a0 16:20:39 DEBUG| [stdout]GPR24: c00109d56cc0 c001fde0cd8c c000c25ffce0 c00109d56ca0 16:20:39 DEBUG| [stdout]GPR28: c00109d56cc0 c0007cef3000 c00109d56c90 16:20:39 DEBUG| [stdout] [ 6521.210276] NIP [c000c25ffce0] 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.210355] LR [c063f058] fuse_request_end+0x128/0x2f0 16:20:39 DEBUG| [stdout] [ 6521.210423] Call Trace: 16:20:39 DEBUG| [stdout] [ 6521.210448] [c00109703aa0] [c063f034] fuse_request_end+0x104/0x2f0 (unreliable) 16:20:39 DEBUG| [stdout] [ 6521.210520] [c00109703af0] [c0642ebc] fuse_dev_do_write+0x2cc/0x5c0 16:20:39 DEBUG| [stdout] [ 6521.210591] [c00109703b70] [c0643654] fuse_dev_wri
[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
** Summary changed: - Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4 + Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire -- 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether intel_cstate in
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856900] Re: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
@Seth looking at the log it is run: 23:52:22 INFO | START timestamp=1585612342localtime=Mar 30 23:52:22 23:52:22 DEBUG| Persistent state client._record_indent now set to 1 23:52:22 INFO | START ubuntu_stress_smoke_test.setup ubuntu_stress_smoke_test.setup timestamp=1585612342localtime=Mar 30 23:52:22 23:52:22 DEBUG| Persistent state client._record_indent now set to 2 .. .. .. 00:08:23 DEBUG| [stdout] 00:08:23 DEBUG| [stdout] Summary: 00:08:23 DEBUG| [stdout] Stressors run: 191 00:08:23 DEBUG| [stdout] Skipped: 1, binderfs 00:08:23 DEBUG| [stdout] Failed: 0, 00:08:23 DEBUG| [stdout] Oopsed: 0, 00:08:23 DEBUG| [stdout] Oomed: 1, dev-shm 00:08:23 DEBUG| [stdout] Passed: 189, access af-alg affinity aio aiol bad-altstack bigheap branch brk cache cap chattr chdir chmod chown chroot clock close context cpu crypt cyclic daemon dccp dentry dev dir dirdeep dnotify dup dynlib enosys env epoll eventfd fallocate fanotify fault fcntl fiemap fifo file-ioctl filename flock fork fp-error fstat full funcret futex get getdent getrandom handle hdd hrtimers icache icmp-flood inode-flags inotify io iomix ioprio ipsec-mb itimer judy key kill klog lease link locka lockbus lockf lockofd loop madvise malloc mcontend membarrier memfd memhotplug memrate memthrash mergesort mincore mknod mlock mmap mmapaddr mmapfixed mmapfork mmapmany mq mremap msg msync netdev netlink-proc netlink-task nice null open personality physpage pidfd pipe pipeherd pkey poll prctl procfs pthread ptrace pty radixsort ramfs rawdev rawsock readahead reboot rename revio rlimit rmap rtc schedpolicy sctp seal seccomp seek sem sem-sysv sendfile set shellsort shm shm-sysv sigfd sigfpe sigio sigpending sigpipe sigq sigrt sigsegv sigsuspend skiplist sleep sock sockabuse sockdiag sockmany softlockup splice stackmmap stream swap switch symlink sync-file sysbadaddr sysfs tee timer timerfd tlb-shootdown tmpfs tree tsearch tun udp udp-flood unshare urandom userfaultfd utime vdso vfork vm vm-addr vm-rw vm-segv vm-splice wait x86syscall yield zero zombie 00:08:23 DEBUG| [stdout] Badret: 0, 00:08:23 DEBUG| [stdout] -- 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/1856900 Title: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12 Status in linux package in Ubuntu: Incomplete Bug description: During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops. 16:20:34 DEBUG| [stdout] sysinfo STARTING 16:20:39 DEBUG| [stdout] sysinfo RETURNED 0 16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed) 16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c000c25ffce0) - exploit attempt? (uid: 0) 16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch 16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1] 16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries 16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_virtio_transport_common vsock zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) userio zcommon(PO) znvpair(PO) cuse spl(O) kvm_pr kvm snd_seq snd_seq_device snd_timer snd soundcore hci_vhci bluetooth ecdh_generic ecc uhid hid vhost_net vhost tap atm algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher aufs sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat ip6_tables iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 algif_hash af_alg ip_vti ip6_vti fou6 sit ipip tunnel4 fou geneve act_mirred cls_basic esp6 authenc echainiv 16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk] 16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5
[Kernel-packages] [Bug 1856900] Re: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
So I think we're in good condition now for 5.4.0-21 on ppc64el. -- 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/1856900 Title: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12 Status in linux package in Ubuntu: Incomplete Bug description: During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops. 16:20:34 DEBUG| [stdout] sysinfo STARTING 16:20:39 DEBUG| [stdout] sysinfo RETURNED 0 16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed) 16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c000c25ffce0) - exploit attempt? (uid: 0) 16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch 16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1] 16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries 16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_virtio_transport_common vsock zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) userio zcommon(PO) znvpair(PO) cuse spl(O) kvm_pr kvm snd_seq snd_seq_device snd_timer snd soundcore hci_vhci bluetooth ecdh_generic ecc uhid hid vhost_net vhost tap atm algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher aufs sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat ip6_tables iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 algif_hash af_alg ip_vti ip6_vti fou6 sit ipip tunnel4 fou geneve act_mirred cls_basic esp6 authenc echainiv 16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk] 16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5.4.0-9-generic #12-Ubuntu 16:20:39 DEBUG| [stdout] [ 6521.209457] NIP: c000c25ffce0 LR: c063f058 CTR: c000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.209528] REGS: c00109703810 TRAP: 0400 Tainted: P OE (5.4.0-9-generic) 16:20:39 DEBUG| [stdout] [ 6521.209608] MSR: 800010009033 CR: 88002440 XER: 2000 16:20:39 DEBUG| [stdout] [ 6521.209681] CFAR: c063f054 IRQMASK: 0 16:20:39 DEBUG| [stdout]GPR00: c063f034 c00109703aa0 c1a4bb00 c0007cef3000 16:20:39 DEBUG| [stdout]GPR04: c000c25ffc18 16:20:39 DEBUG| [stdout]GPR08: 16:20:39 DEBUG| [stdout]GPR12: c000c25ffce0 c0003fffee00 79b6987b4410 16:20:39 DEBUG| [stdout]GPR16: 79b698b3 79b6987b0320 79b69771f240 79b6987b4420 16:20:39 DEBUG| [stdout]GPR20: 79b6880010a0 79b698a4d3a0 16:20:39 DEBUG| [stdout]GPR24: c00109d56cc0 c001fde0cd8c c000c25ffce0 c00109d56ca0 16:20:39 DEBUG| [stdout]GPR28: c00109d56cc0 c0007cef3000 c00109d56c90 16:20:39 DEBUG| [stdout] [ 6521.210276] NIP [c000c25ffce0] 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.210355] LR [c063f058] fuse_request_end+0x128/0x2f0 16:20:39 DEBUG| [stdout] [ 6521.210423] Call Trace: 16:20:39 DEBUG| [stdout] [ 6521.210448] [c00109703aa0] [c063f034] fuse_request_end+0x104/0x2f0 (unreliable) 16:20:39 DEBUG| [stdout] [ 6521.210520] [c00109703af0] [c0642ebc] fuse_dev_do_write+0x2cc/0x5c0 16:20:39 DEBUG| [stdout] [ 6521.210591] [c00109703b70] [c0643654] fuse_dev_write+0x74/0xd0 16:20:39 DEBUG| [stdout] [ 6521.210660] [c00109703c00] [c04707c0] do_iter_readv_writev+0x240/0x290 16:20:39 DEBUG| [stdout] [ 6521.210735] [c000
[Kernel-packages] [Bug 1868113] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-03-31 09:58 EDT--- IBM Bugzilla status-> closed, Fix Released with 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/1868113 Title: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4 Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: ello, Within our Network Performance runs in the RoCE Express 2(.1) area, we noticed a performance regression with streaming workloads which could be mitigated by using an ethtool setting. The Commit which switched the default value from "Striding RQ" to "Legacy RQ" for ConnectX-4 devices (RoCE Express 2(.1)) is attached here: commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad) Author: Tariq Toukan Date: Tue Feb 20 15:17:54 2018 +0200 net/mlx5e: RX, Always prefer Linear SKB configuration Prefer the linear SKB configuration of Legacy RQ over the non-linear one of Striding RQ. This implies that ConnectX-4 LX now uses legacy RQ by default, as it does not support the linear configuration of Striding RQ. Signed-off-by: Tariq Toukan Signed-off-by: Saeed Mahameed diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c index 2c634e50d051..333d4ed52b94 100644 --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c @@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev, MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, params->rx_cqe_compress_def); /* RQ */ - if (mlx5e_striding_rq_possible(mdev, params)) - MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, - !slow_pci_heuristic(mdev)); + /* Prefer Striding RQ, unless any of the following holds: +* - Striding RQ configuration is not possible/supported. +* - Slow PCI heuristic. +* - Legacy RQ would use linear SKB while Striding RQ would use non-linear. +*/ + if (!slow_pci_heuristic(mdev) && + mlx5e_striding_rq_possible(mdev, params) && + (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) || +!mlx5e_rx_is_linear_skb(mdev, params))) + MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true); mlx5e_set_rq_type(mdev, params); mlx5e_init_rq_type_params(mdev, params); We have modified the upstream-kernel to allow us running of measurements and compare differences between Legacy RQ vs Striding RQ. Here is an example below: Kernel used: 5.4.0-rc7 The measurements run on a dedicated machine (z14) using uperf with streaming profiles (MTU size 1500). Example throughput drop: (traffic via a shared card, i.e. client and server using VFs from the same ConnectX-4) -- | |Legacy RQ| Striding RQ | -- |str-writex30k (1 connection) |24.62Gb/s| 33.47Gb/s| -- Additionaly, two tests with transactional workload using the ethtool proposed switch: -- | |Legacy RQ| Striding RQ | -- | rr1c-200x30k---1 | 4.12Gb/s|5.66Gb/s| -- | rr1c-200x30k--10 |15.10Gb/s| 20.77Gb/s| -- As concluded in the communication with Mellanox, there is a possibility to use a simple ethtool command to switch between the queuing methods, allowing us to avoid kernel code changes: ethtool --set-priv-flags DEVNAME rx_striding_rq on (To list the available settings you may use: ethtool --show-priv-flags DEVNAME) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1868113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I have a X1C7, Ubuntu 19.10 (Kernel 5.3.0-45), and only get a "dummy output" in the gnome settings. If I boot with boot parameter snd_hda_intel.dmic_detect=0 I get a working soundcard (hda intel pch, only stereo) but no mic support. Also the mute LED does not work (but did a few kernel updates before as did the 4.0 support). Any hints? Wait for 46-kernel? Maybe my specific model is not in the ucm files? -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu
The optiplex-7060 I was testing on is in the office, I'm working from home and can't test at the moment unfortunately. On Tue, Mar 31, 2020 at 9:25 AM Kai-Heng Feng wrote: > > Can you please test 5.3.0-45.37? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1861294 > > Title: > Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 > intel gpu > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell > Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630 > (Coffeelake 3x8 GT2). > > I had chrome, slack and vmware-player running in Gnome. While doing > some git clone, screen+mouse+keyboard froze for 2 minutes after which > xorg and everything else recovered. I saw this in dmesg: > > kernel: show_signal_msg: 2 callbacks suppressed > kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp > 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000] > kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 > a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 > 00 00 00 00 37 13 00 00 c6 05 c1 6d > kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting > kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting > kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting > kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting > kernel: nvme nvme0: Abort status: 0x0 > kernel: nvme nvme0: Abort status: 0x0 > kernel: nvme nvme0: Abort status: 0x0 > kernel: nvme nvme0: Abort status: 0x0 > kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller > kernel: nvme nvme0: 12/0/0 default/read/poll queues > > While writing this bug report, the system froze again, and this time > it didn't recover. After a cold reset I didn't see any other > GpuWatchdog messages in journalctl. > > Ubuntu applied a BIOS firmware update before the first freeze, so my > BIOS was updated as part of the cold reset I did. Not sure if this is > relevant to reproducing the freeze. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+subscriptions -- 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/1861294 Title: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu Status in linux package in Ubuntu: Incomplete Bug description: Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630 (Coffeelake 3x8 GT2). I had chrome, slack and vmware-player running in Gnome. While doing some git clone, screen+mouse+keyboard froze for 2 minutes after which xorg and everything else recovered. I saw this in dmesg: kernel: show_signal_msg: 2 callbacks suppressed kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000] kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller kernel: nvme nvme0: 12/0/0 default/read/poll queues While writing this bug report, the system froze again, and this time it didn't recover. After a cold reset I didn't see any other GpuWatchdog messages in journalctl. Ubuntu applied a BIOS firmware update before the first freeze, so my BIOS was updated as part of the cold reset I did. Not sure if this is relevant to reproducing the freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856900] Re: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1856900 Title: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12 Status in linux package in Ubuntu: Fix Released Bug description: During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops. 16:20:34 DEBUG| [stdout] sysinfo STARTING 16:20:39 DEBUG| [stdout] sysinfo RETURNED 0 16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed) 16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c000c25ffce0) - exploit attempt? (uid: 0) 16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch 16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1] 16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries 16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_virtio_transport_common vsock zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) userio zcommon(PO) znvpair(PO) cuse spl(O) kvm_pr kvm snd_seq snd_seq_device snd_timer snd soundcore hci_vhci bluetooth ecdh_generic ecc uhid hid vhost_net vhost tap atm algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher aufs sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat ip6_tables iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 algif_hash af_alg ip_vti ip6_vti fou6 sit ipip tunnel4 fou geneve act_mirred cls_basic esp6 authenc echainiv 16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk] 16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5.4.0-9-generic #12-Ubuntu 16:20:39 DEBUG| [stdout] [ 6521.209457] NIP: c000c25ffce0 LR: c063f058 CTR: c000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.209528] REGS: c00109703810 TRAP: 0400 Tainted: P OE (5.4.0-9-generic) 16:20:39 DEBUG| [stdout] [ 6521.209608] MSR: 800010009033 CR: 88002440 XER: 2000 16:20:39 DEBUG| [stdout] [ 6521.209681] CFAR: c063f054 IRQMASK: 0 16:20:39 DEBUG| [stdout]GPR00: c063f034 c00109703aa0 c1a4bb00 c0007cef3000 16:20:39 DEBUG| [stdout]GPR04: c000c25ffc18 16:20:39 DEBUG| [stdout]GPR08: 16:20:39 DEBUG| [stdout]GPR12: c000c25ffce0 c0003fffee00 79b6987b4410 16:20:39 DEBUG| [stdout]GPR16: 79b698b3 79b6987b0320 79b69771f240 79b6987b4420 16:20:39 DEBUG| [stdout]GPR20: 79b6880010a0 79b698a4d3a0 16:20:39 DEBUG| [stdout]GPR24: c00109d56cc0 c001fde0cd8c c000c25ffce0 c00109d56ca0 16:20:39 DEBUG| [stdout]GPR28: c00109d56cc0 c0007cef3000 c00109d56c90 16:20:39 DEBUG| [stdout] [ 6521.210276] NIP [c000c25ffce0] 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.210355] LR [c063f058] fuse_request_end+0x128/0x2f0 16:20:39 DEBUG| [stdout] [ 6521.210423] Call Trace: 16:20:39 DEBUG| [stdout] [ 6521.210448] [c00109703aa0] [c063f034] fuse_request_end+0x104/0x2f0 (unreliable) 16:20:39 DEBUG| [stdout] [ 6521.210520] [c00109703af0] [c0642ebc] fuse_dev_do_write+0x2cc/0x5c0 16:20:39 DEBUG| [stdout] [ 6521.210591] [c00109703b70] [c0643654] fuse_dev_write+0x74/0xd0 16:20:39 DEBUG| [stdout] [ 6521.210660] [c00109703c00] [c04707c0] do_iter_readv_writev+0x240/0x290 16:20:39 DEBUG| [stdout] [ 6521.210
[Kernel-packages] [Bug 1443924]
Download Apps and Games on your PC Windows and Mac https://www.newsforpc.com/ If you want to download and watch movies and tv shows free than click this https://www.helpsforpc.com/ and download all your favorite movies. -- 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/1443924 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity after installing 15.04 Beta. The system did work correctly with older Ubuntu versions (like 12.04) and had this problem show up after upgrading to Trusty (as I already reported in bug #1318837). Using Trusty the problem went away when switching from the stock 3.13.0-XX-generic kernel to builds of newer kernels (like 3.14.1-031401). Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=61621 Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation: - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot) - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1997 F pulseaudio CurrentDesktop: LXDE Date: Tue Apr 14 14:19:19 2015 HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132 MachineType: Freeline Freeline Series ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: Freeline Series dmi.board.vendor: Freeline dmi.board.version: Ver1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr: dmi.product.name: Freeline Series dmi.product.version: Ver1.0 dmi.sys.vendor: Freeline To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1443924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Please wait for -46 or install -43, the mute led problem will be fixed in the -46 since I just checked the patch is in the -46 kernel. And if the ucm doesn't cover your machine, please install 1.1.9-0ubuntu1.2testucm from https://launchpad.net/~hui.wang/+archive/ubuntu/audio-master before the 1.3 is ready. -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868442] Re: Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan
Kernel 5.3.0-46 fixed the problem. -- 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/1868442 Title: Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: I updated to latest kernel: initrd.img-5.3.0-43-generic and find that bluetooth is enabled and no wireless connection. When I stop bluetooth I go into airplane mode. I cannot find any wireless connection in network or wireless connection setup in settings. ifconfig shows there is no wireless interface setup. When I go back to kernel 5.3.0-42 everything is working correctly. I am using an HP laptop. I can see the wireless network controller with lshw: lshw -C network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: eno1 version: 15 serial: b4:b6:86:e7:67:29 size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.108 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s resources: irq:38 ioport:e000(size=256) memory:fe904000-fe904fff memory:fe90-fe903fff *-network description: Network controller product: Dual Band Wireless-AC 3168NGW [Stone Peak] vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 version: 10 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=iwlwifi latency=0 resources: irq:43 memory:fe80-fe801fff lspci |grep Network 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) iwconfig lo no wireless extensions. eno1 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-43-generic 5.3.0-43.36 ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18 Uname: Linux 5.3.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rustin 1684 F pulseaudio Date: Sun Mar 22 05:43:04 2020 InstallationDate: Installed on 2018-11-30 (478 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: HP HP Pavilion Laptop 17-ar0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-43-generic root=UUID=29898130-1fa9-464b-88cf-ed44cfd58f76 ro pcie_aspm=force acpi_backlight=vendor PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-43-generic N/A linux-backports-modules-5.3.0-43-generic N/A linux-firmware1.183.5 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8357 dmi.board.vendor: HP dmi.board.version: 37.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.22:bd01/12/2018:svnHP:pnHPPavilionLaptop17-ar0xx:pvr:rvnHP:rn8357:rvr37.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 17-ar0xx dmi.product.sku: 1KU52UA#ABA dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rustin 1600 F pulseaudio /dev/snd/controlC0: rustin 1600 F pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-11-30 (480 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono
[Kernel-packages] [Bug 1868442] Re: Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan
Kernel 5.3.0-46 fixed the problem. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1868442 Title: Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: I updated to latest kernel: initrd.img-5.3.0-43-generic and find that bluetooth is enabled and no wireless connection. When I stop bluetooth I go into airplane mode. I cannot find any wireless connection in network or wireless connection setup in settings. ifconfig shows there is no wireless interface setup. When I go back to kernel 5.3.0-42 everything is working correctly. I am using an HP laptop. I can see the wireless network controller with lshw: lshw -C network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: eno1 version: 15 serial: b4:b6:86:e7:67:29 size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.108 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s resources: irq:38 ioport:e000(size=256) memory:fe904000-fe904fff memory:fe90-fe903fff *-network description: Network controller product: Dual Band Wireless-AC 3168NGW [Stone Peak] vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 version: 10 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=iwlwifi latency=0 resources: irq:43 memory:fe80-fe801fff lspci |grep Network 03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) iwconfig lo no wireless extensions. eno1 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-43-generic 5.3.0-43.36 ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18 Uname: Linux 5.3.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rustin 1684 F pulseaudio Date: Sun Mar 22 05:43:04 2020 InstallationDate: Installed on 2018-11-30 (478 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: HP HP Pavilion Laptop 17-ar0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-43-generic root=UUID=29898130-1fa9-464b-88cf-ed44cfd58f76 ro pcie_aspm=force acpi_backlight=vendor PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-43-generic N/A linux-backports-modules-5.3.0-43-generic N/A linux-firmware1.183.5 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8357 dmi.board.vendor: HP dmi.board.version: 37.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.22:bd01/12/2018:svnHP:pnHPPavilionLaptop17-ar0xx:pvr:rvnHP:rn8357:rvr37.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 17-ar0xx dmi.product.sku: 1KU52UA#ABA dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rustin 1600 F pulseaudio /dev/snd/controlC0: rustin 1600 F pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-11-30 (480 days ago) InstallationMedia: Ubuntu 18.
