[Kernel-packages] [Bug 1228263] Re: Volume control doesn't work automatically when connecting Bluetooth device.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] Re: Volume control doesn't work automatically when connecting Bluetooth device.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947364] Re: mt76 module disagrees on a lot
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947364 Title: mt76 module disagrees on a lot Status in linux package in Ubuntu: Invalid Bug description: I had a 20.10 beta live cd with working wifi and bluetooth. (both use the same chipset) I upgraded to 20.10 and wifi is not working. bluetooth is. Description:Ubuntu 21.10 Release:21.10 after a modprobe mt76. the system returns: modprobe: ERROR: could not insert 'mt76': Invalid argument there is a lot of disagreeing in dmesg. [ 212.499500] mt76: disagrees about version of symbol ieee80211_sta_register_airtime [ 212.499506] mt76: Unknown symbol ieee80211_sta_register_airtime (err -22) [ 212.499550] mt76: disagrees about version of symbol __ieee80211_schedule_txq [ 212.499551] mt76: Unknown symbol __ieee80211_schedule_txq (err -22) [ 212.499609] mt76: disagrees about version of symbol ieee80211_free_hw [ 212.499610] mt76: Unknown symbol ieee80211_free_hw (err -22) [ 212.499661] mt76: disagrees about version of symbol ieee80211_txq_schedule_start [ 212.499664] mt76: Unknown symbol ieee80211_txq_schedule_start (err -22) [ 212.499685] mt76: disagrees about version of symbol ieee80211_tx_status_ext [ 212.499687] mt76: Unknown symbol ieee80211_tx_status_ext (err -22) [ 212.499714] mt76: disagrees about version of symbol ieee80211_register_hw [ 212.499716] mt76: Unknown symbol ieee80211_register_hw (err -22) [ 212.499794] mt76: disagrees about version of symbol __ieee80211_create_tpt_led_trigger [ 212.499797] mt76: Unknown symbol __ieee80211_create_tpt_led_trigger (err -22) [ 212.499828] mt76: disagrees about version of symbol ieee80211_sta_eosp [ 212.499829] mt76: Unknown symbol ieee80211_sta_eosp (err -22) [ 212.499841] mt76: disagrees about version of symbol ieee80211_get_hdrlen_from_skb [ 212.499842] mt76: Unknown symbol ieee80211_get_hdrlen_from_skb (err -22) [ 212.499900] mt76: disagrees about version of symbol ieee80211_get_tx_rates [ 212.499901] mt76: Unknown symbol ieee80211_get_tx_rates (err -22) [ 212.499907] mt76: disagrees about version of symbol ieee80211_send_bar [ 212.499908] mt76: Unknown symbol ieee80211_send_bar (err -22) [ 212.499925] mt76: disagrees about version of symbol ieee80211_sta_uapsd_trigger [ 212.499926] mt76: Unknown symbol ieee80211_sta_uapsd_trigger (err -22) [ 212.499976] mt76: disagrees about version of symbol ieee80211_queue_delayed_work [ 212.499977] mt76: Unknown symbol ieee80211_queue_delayed_work (err -22) [ 212.52] mt76: disagrees about version of symbol ieee80211_calc_rx_airtime [ 212.53] mt76: Unknown symbol ieee80211_calc_rx_airtime (err -22) [ 212.500012] mt76: disagrees about version of symbol ieee80211_find_sta_by_ifaddr [ 212.500013] mt76: Unknown symbol ieee80211_find_sta_by_ifaddr (err -22) [ 212.500019] mt76: disagrees about version of symbol ieee80211_next_txq [ 212.500020] mt76: Unknown symbol ieee80211_next_txq (err -22) [ 212.500032] mt76: disagrees about version of symbol ieee80211_beacon_cntdwn_is_complete [ 212.500034] mt76: Unknown symbol ieee80211_beacon_cntdwn_is_complete (err -22) [ 212.500041] mt76: disagrees about version of symbol ieee80211_sta_pspoll [ 212.500042] mt76: Unknown symbol ieee80211_sta_pspoll (err -22) [ 212.500061] mt76: disagrees about version of symbol ieee80211_free_txskb [ 212.500062] mt76: Unknown symbol ieee80211_free_txskb (err -22) [ 212.500075] mt76: disagrees about version of symbol ieee80211_alloc_hw_nm [ 212.500076] mt76: Unknown symbol ieee80211_alloc_hw_nm (err -22) [ 212.500086] mt76: disagrees about version of symbol ieee80211_tx_dequeue [ 212.500087] mt76: Unknown symbol ieee80211_tx_dequeue (err -22) [ 212.500092] mt76: disagrees about version of symbol ieee80211_rx_list [ 212.500093] mt76: Unknown symbol ieee80211_rx_list (err -22) [ 212.500116] mt76: disagrees about version of symbol ieee80211_tx_status [ 212.500117] mt76: Unknown symbol ieee80211_tx_status (err -22) [ 212.500141] mt76: disagrees about version of symbol ieee80211_iterate_active_interfaces_atomic [ 212.500143] mt76: Unknown symbol ieee80211_iterate_active_interfaces_atomic (err -22) [ 212.500158] mt76: disagrees about version of symbol ieee80211_unregister_hw [ 212.500159] mt76: Unknown symbol ieee80211_unregister_hw (err -22) [ 212.500177] mt76: disagrees about version of symbol ieee80211_sta_ps_transition [ 212.500179] mt76: Unknown symbol ieee80211_sta_ps_transition (err -22) [ 212.500193] mt76: disagrees about version of symbol ieee80211_csa_finish [ 212.500194] mt76: Unknown symbol ieee80211_csa_finish (err -22) lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne
[Kernel-packages] [Bug 1932378] Re: My CPU fan in max speed after ubuntu unsuspended
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932378 Title: My CPU fan in max speed after ubuntu unsuspended Status in linux package in Ubuntu: Expired Bug description: My CPU fan in max speed after ubuntu unsuspended: When I put ubuntu to suspend mode, and come back to it to unsuspend, the fan runs at max "noisy" and I have to restart to get things back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 13:40:00 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-03-14 (95 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931300] Re: Nautilus mounts Google-drive while the Internet is down.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931300 Title: Nautilus mounts Google-drive while the Internet is down. Status in linux package in Ubuntu: Expired Bug description: This bug report is produced with a working internet of course. The problem occurred when my local network was still working fine, but the connection to the Internet was lost due to a failing Ethernet cable from my local network router to the ISP router. I mount the Google Drive at each login as follows: sh -c "rclone --vfs-cache-mode writes mount Google-drive: /media/Google-drive". Always it works fine, except with the failing cable. The Google drive has been shown after 25 seconds of by Nautilus, despite a completely missing connection with the Internet. It took Nautilus 25 seconds to display its window the first time. My Google drive has according to Conky now 1 PiB :) and it is impossible to dismount the Google Drive, for details see the screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 8 15:35:16 2021 InstallationDate: Installed on 2019-11-30 (556 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-03-24 (75 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931508] Re: ubuntu_kernel_selftests net linux ADT test failure with linux/5.11.0-20.21(unavailability of vmlinux)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931508 Title: ubuntu_kernel_selftests net linux ADT test failure with linux/5.11.0-20.21(unavailability of vmlinux) Status in linux package in Ubuntu: Expired Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-20.21 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210607_172050_4f1dc@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210609_182341_08ee8@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210607_180458_58645@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210607_180455_68857@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933141] Re: USB Headset stopped working in Ubuntu Impish
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933141 Title: USB Headset stopped working in Ubuntu Impish Status in linux package in Ubuntu: Expired Bug description: I follow Ubuntu Impish/development on my laptop (Lenovo ideapad 5-15IIL05/81YK00QYRA). I have all recent Impish updates and kernel linux-image-generic 5.11.0.18.19+21.10.1 into which I rebooted on Jun 5th. Once I tried to plug into it an USB headset Jabra Evolve 20 MS and found that it is visible in lsusb as device 0b0e:0300 but not in audio devices. In dmesg -w, I see two lines Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7 appearing immediately after plugging this device. I compared this hardware support with Ubuntu Focal LTS on the nearby Asus X302LA and found that its modules are loaded as expected, and it becomes visible, usable and manageable to all audio utilities (alsamixer, pavucontrol, firefox, vlc, whatever) Can this please be checked with Impish and fixed in some way ? I could not determine what module it deems unsigned. Ready to collect and provide additional required information on your request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930783] Re: integrity: Problem loading X.509 certificate
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930783 Title: integrity: Problem loading X.509 certificate Status in linux package in Ubuntu: Expired Bug description: Following error shows on Acer machines while booting when UEFI boot is enabled. integrity: Problem loading X.509 certificate -65 The issue is discussed at https://bugzilla.opensuse.org/show_bug.cgi?id=1129471 and a patch is available at https://lkml.org/lkml/2019/7/16/23. Seems like this patch is not included in Ubuntu as I'm still getting this error. I'm using Linux Mint 20, which is based on Ubuntu 20.04. This error comes while live booting Ubuntu 20.04 and Ubuntu 18.04 also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926552] Re: [Lenovo IdeaPad 5 14IIL05] trackpad not detected upon first install of Ubuntu 20.04 LTS
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926552 Title: [Lenovo IdeaPad 5 14IIL05] trackpad not detected upon first install of Ubuntu 20.04 LTS Status in linux package in Ubuntu: Expired Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 Expected to be able to go into settings and enable trackpad. I ran 'cat /proc/bus/input/devices' to see if it was even being detected, and no trackpad appeared under the listings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 21:47:08 2021 InstallationDate: Installed on 2021-04-29 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931767] Re: Ubuntu 20.04 freezes when I connect external monitor through USB-C
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931767 Title: Ubuntu 20.04 freezes when I connect external monitor through USB-C Status in linux package in Ubuntu: Expired Bug description: When I connect an external monitor through USB-C my system freezes completely and the fans start spinning full speed and I can't do anything. It was working before but now all of the sudden it has stopped working. I used to be able to connect 2 extra external monitors (through HDMI and USB-C) *P.S. When I connect the monitor and then turn on the computer then it hangs at the splash loading screen.* Here is my setup: Laptop - Lenovo Legion 5 (1 HDMI port and 1 USB-C port) Intel i5 10th gen NVIDIA GeForce GTX 1650 (with NVIDIA proprietary driver installed) What I have tried so far but did not help `apt update && apt upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923087] Re: [Lenovo Ideapad 5 15ARE05] touchpad not detected
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923087 Title: [Lenovo Ideapad 5 15ARE05] touchpad not detected Status in linux package in Ubuntu: Expired Bug description: My touchpad is not recognized at all in xinput or libinput list- devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-48-generic 5.8.0-48.54~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 21:17:34 2021 InstallationDate: Installed on 2021-04-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933106] Re: Qualcomm QCA6390 Wireless Network Adapter AX500-DBS ath11k_pci: cannot connect
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933106 Title: Qualcomm QCA6390 Wireless Network Adapter AX500-DBS ath11k_pci: cannot connect Status in linux package in Ubuntu: Expired Bug description: I have a fresh Ubuntu 21.04, installed last friday (2021-06-18). During the installation I can connect to my enterprise wifi. But today no way to connect to a new wifi (I'm working at home today). I always have connection failed. I've found "solutions" but they are talking about Ubuntu 20.04 I want to know if there is solution. Some information about my system: https://paste.ubuntu.com/p/ZDpzD6zCmt/ (I have updated to kernel 5.12.12-051212-generic). Thank, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931021] Re: Focal (20.04): IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931021 Title: Focal (20.04): IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 Status in linux package in Ubuntu: Expired Bug description: The bug reported at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926030 affects Focal (20.04). I use an IR remote with the ir-keytable package. Everything was working fine until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu 20.04.2. When any key is pressed on the remote, the key is repeated about 500 times. The kernel is now 5.8.0-50, and the problem persists. Other users on the MythTV mailing list are reporting the issue, and it appears that the problem is related to changes in the following files: drivers/media/rc/ir-mce_kbd-decoder.c drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c drivers/media/rc/serial_ir.c It has been reported that reverting the ir-mce_kbd-decoder.c and rc- main.c files to the older versions fixes the problem. /proc/version_signature > version.log: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 lspci -vnvn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:590f] (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:8694] 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: skl_uncore ir-keytable -V: IR keytable control version 1.18.0 lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 uname -r: 5.8.0-55-generic This test F-hwe-5.8 / G-5.8 kernel works: https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933126] Re: Error on 'apt update' on Ubuntu 20.10 (Groovy)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933126 Title: Error on 'apt update' on Ubuntu 20.10 (Groovy) Status in linux package in Ubuntu: Expired Bug description: I'm getting this error when trying to refresh my repos: E: The repository 'http://ppa.launchpad.net/alexlarsson/flatpak/ubuntu groovy Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. This blocks me from updating the repo of other apps which makes this a security issue. Thx jc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931242] Re: linux-uc20-efi: make it easy to build derivative kernel.efi
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931242 Title: linux-uc20-efi: make it easy to build derivative kernel.efi Status in linux package in Ubuntu: Expired Bug description: linux-uc20-efi: make it easy to build derivative kernel.efi Currently debian/rules & debian.uc20-efi/control.stub are tightly coupled and hardcode the source package name (linux-uc20-efi), its relationship to linux-unsigned-image-* packages, and flavours to build kernel.efi apps for. Decouple those things a little bit, to make it easier to build derivative kernel.efi apps. 1) do not calculate KERNEL_SOURCE variable at all, as it is not needed 2) calculate flavours to build kernel.efi for, from build-deps This allows to create a derivative linux-blah-uc20-efi, and simply adjust debian.blah-uc20-efi/control.stub and produce correct signing tarballs for the correct required derivative flavour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933199] Re: Mainline builds for v5.10.37 to v5.10.45 contain packages for v5.11.0
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933199 Title: Mainline builds for v5.10.37 to v5.10.45 contain packages for v5.11.0 Status in linux package in Ubuntu: Expired Bug description: On the mainline kernel server, all folders for kernels v5.10.37 to v5.10.45 contain packages for kernel v5.11.0. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.37/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931129] Re: v5.13 net bpf selftests fail with older clang toolchains
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931129 Title: v5.13 net bpf selftests fail with older clang toolchains Status in linux package in Ubuntu: Expired Bug description: selftests/bpf: add ifdefs in tests for required Clang versions This codifies the clang version requirements from README.rst in the code, such that only expected working test cases are compiled for the expected clang version combinations. This insures that most tests are still executed, even when one doesn't have access to the latest clang toolchain. Also see internal v5.13 test results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930610] Re: Upgrade fails to boot with kernel 5.4
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930610 Title: Upgrade fails to boot with kernel 5.4 Status in linux package in Ubuntu: Expired Bug description: I tried to upgrade an Ubuntu 18.04 to 20.04 two weeks ago. The system is a server type installation running as a virtual machine on Hyper-V, primarily running letsencrypt and nginx. Actually I tried twice, both upgrades left me with a system that doesn´t boot by default. The first iteration was I tried to accept maintainer version for the boot/grub menu, and as that didn´t restart properly, I tried another time, this time keeping my own version. Both upgrades left me with a system that was not booting. With the second upgrade, I experimented a little more. When the system restarts, I am stuck with it doesn´t boot. When I then power off and power on again, I get a boot menu with the options Ubuntu, Advanced options for Ubuntu, and UEFI Firmware Settings. With Advanced I get Ubuntu with various kernel options, with Linux 5.4.0-73-generic w/o recovery mode, and Linux 4.15.0-143-generic w/o recovery mode. The variants with 4.15.0-143 actually work, whereas 5.4.0-73 doesn´t work. I do have some VMs that run 20.04 with kernel 5.4.0-something, thus I assume it is an issue caused by the upgrade or previous installation. Any idea what to look for? I asked this already at https://askubuntu.com/questions/1338236/ubuntu-fails-to-start-by- default-after-upgrade-18-04-to-20-04 and then https://answers.launchpad.net/ubuntu/+question/697332, but didn´t get a response that helped me to resolve the issue. Thanks, Joachim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933899] Re: Buzzing in Headphones (FireFox) When Fiverr is Opened After YouTube Is opened
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933899 Title: Buzzing in Headphones (FireFox) When Fiverr is Opened After YouTube Is opened Status in linux package in Ubuntu: Expired Bug description: Hello! Thank you for viewing. I would like to report this bug that I found that is appearing in the kernel 5.4.0.77 When YouTube is open in Firefox, the headphones start buzzing after Fiverr.com is opened (when a video is playing). This is definitely a kernel bug as I am currently using 5.8.0.53 with no issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930179] Re: Advantech CAN driver not recognized in Ubuntu Core 20
[Expired for snapd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: snapd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930179 Title: Advantech CAN driver not recognized in Ubuntu Core 20 Status in linux package in Ubuntu: Expired Status in snapd package in Ubuntu: Expired Bug description: CAN module is not built into the kernel source for Ubuntu Core 20, hence, the CAN interface did not show up. Purpose to include Advantech's CAN driver for board MIO5373. Please kindly consider and refer to the attachment for the CAN driver source code and instructions. I hope the driver can be included as part of the official kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930110] Re: Wake-up after suspend only on second keypress
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930110 Title: Wake-up after suspend only on second keypress Status in linux package in Ubuntu: Expired Bug description: My computer is a HP Z240 tower workstation, Ubuntu version: Description: Ubuntu 18.04.5 LTS Release: 18.04 I can and do suspend my computer by pressing Fn-Key + F1-key on the HP keyboard. The F1 key is marked with a crescent moon to indicate this functionality. The suspend state is indicated by a blinking led on the computer case. From 16.04 I was used, that in suspend state any keypress on the keyboard would wake up the computer again immediately: The screen would (if turned on) display what was last visible when suspend was executed through the abovementioned function key. The led on the computer case would light steadily. Now a keypress on the suspended computer leads to a short activation of the harddisk, the led on the computer case will light steadily but the monitor (also if on) remains dark. After about 2-5 seconds the harddisk stands still again, the computer becomes silent and the led on the computer case is blinking again, as in suspend mode. I presume the computer is now again in suspend mode. When this state is reached, a second keypress leads to a correct awake from suspend, the harddisk spins, the led on the case lights steadily and the monitor displays what is expected. The computer can then be used as expected. Note: I have 64 GByte of RAM and only 32GB Swap partition, so I presume (and hope) that hibernation (RAM to Disk) plays no role here, only suspend and wake-up from suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931044] Re: SynPS/2 Synaptics TouchPad choppy movement after suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931044 Title: SynPS/2 Synaptics TouchPad choppy movement after suspend Status in linux package in Ubuntu: Expired Bug description: Sometimes touchpad input becomes very laggy. It seems to be related to suspending the laptop. I think it also has to do with other mice being plugged in/out. Often, suspending and waking up immediately afterwards makes the pointer fluent again. This is not the only problem I see with this touchpad/driver: Sometimes the pointer stops moving horizontally as if it got stuck in a scrolling gesture. Sometimes the pointer (almost) stops moving completely. Suspending often but not always helps. I am not sure whether these problems are related. I am happy to debug the problem, but I don't know where to start. >> xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=10 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=9[slave keyboard (3)] ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=13 [slave keyboard (3)] >> lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal >> cat /proc/bus/input/devices ... I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931105] Re: Sleep issue on ubuntu 21.04, CPU AMD 5700u
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931105 Title: Sleep issue on ubuntu 21.04, CPU AMD 5700u Status in linux package in Ubuntu: Expired Bug description: System Info Dell Inspiron 5515 Operating System: Kubuntu 21.04 Kernel Version: 5.12.9-051209-generic OS Type: 64-bit Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 15,1 GiB of RAM Graphics Processor: AMD RENOIR If I suspend my pc, the screen, fans and keyboard backlight turn off. However if I try to wake up from suspension the screen stays black, while the keyboard backlight starts blinking. The only way to unlock it is to click the power button, and the pc will automatically restart (thus losing the data of the active session). Initially I had the 5.11 kernel, then to see if the problem was solved I tried to install the 5.12 kernel and the 5.12.9 kernel, but there were no improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930179] Re: Advantech CAN driver not recognized in Ubuntu Core 20
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930179 Title: Advantech CAN driver not recognized in Ubuntu Core 20 Status in linux package in Ubuntu: Expired Status in snapd package in Ubuntu: Expired Bug description: CAN module is not built into the kernel source for Ubuntu Core 20, hence, the CAN interface did not show up. Purpose to include Advantech's CAN driver for board MIO5373. Please kindly consider and refer to the attachment for the CAN driver source code and instructions. I hope the driver can be included as part of the official kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934191] Re: i40e 2.15.9 driver does not show rx_packets when xdp/ebpf is attached
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934191 Title: i40e 2.15.9 driver does not show rx_packets when xdp/ebpf is attached Status in linux package in Ubuntu: Expired Bug description: Intel driver for i40e, i40e-2.15.9.tar.gz does not display rx_packets from ethtool when any xdp/ebpf module is attached to the interface. This problem is seen even in version 2.10 of the i40e driver. The one that is packaged with the upstream kernel seems to be fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934112] Re: Intel 100G nic get call trace for sosreport on focal ga-kenel
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934112 Title: Intel 100G nic get call trace for sosreport on focal ga-kenel Status in linux package in Ubuntu: Expired Bug description: On Asus Server, when it run "sosreport -a" to the network step, the console would print below call trace and the 100G Nic port became unreachable. call trace on ga-kernel ( v5.4): https://paste.ubuntu.com/p/TC5Jn6hYGF/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935866] Re: r8169 not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935866 Title: r8169 not working Status in linux package in Ubuntu: Expired Bug description: Whenever I reboot my computer, I am unable to connect to my network via ethernet. After running journalctl -xe I found the culprit to be the r8169 driver. == Steps to reproduce: == - Reboot computer - Try to connect to network My linux-modules package is linux-modules-5.11.0-7620-generic The kernel logs give me this error: > r8169 :04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100) I uploaded a log of when I attempted to use modprobe r8169 here: https://pastebin.com/kPA1wM82 Here is the information about my network adapter from the output of lspci: > 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) And from ip link show: > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > 2: enp4s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 > link/ether 18:c0:4d:2f:b0:7d brd ff:ff:ff:ff:ff:ff == Notes == - I am not running vanilla ubuntu, but Pop!_OS 21.04. I was referred here after attempting to report this on this github issue: https://github.com/pop-os/linux/issues/56 - My motherboard is a Gigabyte B450M DS3H with a Ryzen 2600 - The only way I have found to solve this is to use the r8168-dkms package and blacklist r8169 or rebooting into my Windows partition and then reboot back into Pop!_OS (however when restarting and trying to go back into Pop!_OS, r8169 throws that error again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936958] Re: mlx5_core crash, taking down a bond
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936958 Title: mlx5_core crash, taking down a bond Status in linux package in Ubuntu: Expired Bug description: Jul 20 14:40:23 anonster kernel: [ 1716.692818] mlx5_core :03:00.0: assert_var[0] 0x Jul 20 14:40:23 anonster kernel: [ 1716.698541] mlx5_core :03:00.0: assert_var[1] 0x Jul 20 14:40:23 anonster kernel: [ 1716.704240] mlx5_core :03:00.0: assert_var[2] 0x Jul 20 14:40:23 anonster kernel: [ 1716.709945] mlx5_core :03:00.0: assert_var[3] 0x Jul 20 14:40:23 anonster kernel: [ 1716.715641] mlx5_core :03:00.0: assert_var[4] 0x Jul 20 14:40:23 anonster kernel: [ 1716.721343] mlx5_core :03:00.0: assert_exit_ptr 0x Jul 20 14:40:23 anonster kernel: [ 1716.727214] mlx5_core :03:00.0: assert_callra 0x Jul 20 14:40:23 anonster kernel: [ 1716.732917] mlx5_core :03:00.0: fw_ver 65535.65535.65535 Jul 20 14:40:23 anonster kernel: [ 1716.738617] mlx5_core :03:00.0: hw_id 0x Jul 20 14:40:23 anonster kernel: [ 1716.743620] mlx5_core :03:00.0: irisc_index 255 Jul 20 14:40:23 anonster kernel: [ 1716.748530] mlx5_core :03:00.0: synd 0xff: unrecognized error Jul 20 14:40:23 anonster kernel: [ 1716.754662] mlx5_core :03:00.0: ext_synd 0x Jul 20 14:40:23 anonster kernel: [ 1716.759578] mlx5_core :03:00.0: raw fw_ver 0x Jul 20 14:40:23 anonster kernel: [ 1716.765038] WARNING: CPU: 0 PID: 0 at /build/linux-hwe-EPHQQp/linux-hwe-4.15.0/kernel/time/timer.c:898 mod_timer+0x3e4/0x400 Jul 20 14:40:23 anonster kernel: [ 1716.765039] Modules linked in: binfmt_misc lkp_Ubuntu_4_15_0_142_146_generic_78(OEK) bonding nls_iso8859_1 xfs edac_mce_amd ipmi_ssif kvm_amd hpilo kvm i 2c_piix4 irqbypass ipmi_si Jul 20 14:40:23 anonster kernel: [ 1716.765051] mlx5_core :03:00.0: health_care:194:(pid 29045): handling bad device here Jul 20 14:40:23 anonster kernel: [ 1716.765052] ipmi_devintf ipmi_msghandler shpchp acpi_power_meter Jul 20 14:40:23 anonster kernel: [ 1716.765057] mlx5_core :03:00.0: mlx5_handle_bad_state:152:(pid 29045): Expected to see disabled NIC but it is has invalid value 3 Jul 20 14:40:23 anonster kernel: [ 1716.765058] k10temp mac_hid ib_iser Jul 20 14:40:23 anonster kernel: [ 1716.765062] mlx5_core :03:00.0: mlx5_pci_err_detected was called Jul 20 14:40:23 anonster kernel: [ 1716.765063] rdma_cm iw_cm ib_cm Jul 20 14:40:23 anonster kernel: [ 1716.765067] mlx5_core :03:00.0: mlx5_enter_error_state:121:(pid 29045): start Jul 20 14:40:23 anonster kernel: [ 1716.765067] ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async _pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear bcache ses enclosure crct10dif_pclmul crc32_pclmul mgag200 ghash_clmulni_intel pcbc ttm drm_kms_helper aesni_intel mlx5_core syscopyarea sysfillrect igb sysimgblt aes_x86_64 fb_sys_fops crypto_simd glue_helper mlxfw dca nvme cryptd drm devlink i2c_algo_bit smartpqi nvme_core ptp scsi_transport_sas pps_ core wmi Jul 20 14:40:23 anonster kernel: [ 1716.772598] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE K 4.15.0-142-generic #146~16.04.1-Ubuntu Jul 20 14:40:23 anonster kernel: [ 1716.772598] Hardware name: HPE ProLiant DL325 Gen10 Plus/ProLiant DL325 Gen10 Plus, BIOS A43 05/11/2020 Jul 20 14:40:23 anonster kernel: [ 1716.772600] RIP: 0010:mod_timer+0x3e4/0x400 Jul 20 14:40:23 anonster kernel: [ 1716.772601] RSP: 0018:91e55e603e30 EFLAGS: 00010093 Jul 20 14:40:23 anonster kernel: [ 1716.772603] RAX: 000100056792 RBX: 0001000567c4 RCX: 00010005678a Jul 20 14:40:23 anonster kernel: [ 1716.772603] RDX: 00010005678c RSI: 91e55e603e48 RDI: 91e55e61a700 Jul 20 14:40:23 anonster kernel: [ 1716.772604] RBP: 91e55e603e80 R08: 91e55e010800 R09: 91e55dc01ff0 Jul 20 14:40:23 anonster kernel: [ 1716.772605] R10: R11: 0040 R12: 91e54bb4d8d8 Jul 20 14:40:23 anonster kernel: [ 1716.772606] R13: 91e54bb4d8d8 R14: 91e55e61a700 R15: 91e54bb4d8d8 Jul 20 14:40:23 anonster kernel: [ 1716.772607] FS: () GS:91e55e60() knlGS: Jul 20 14:40:23 anonster kernel: [ 1716.772607] CS: 0010 DS: ES: CR0: 80050033 Jul 20 14:40:23 anonster kernel: [ 1716.772608] CR2: 7fd20bd2e000 CR3: 000816294000 CR4: 00340ef0 Jul 20 14:40:23 anonster kernel: [ 1716.772609] Call Trace: Jul 20 14:40:23 anonster kernel: [ 1716.772611] Jul 20 14:40:23
[Kernel-packages] [Bug 1936573] Re: logitech-djreceiver spams Dmesg
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936573 Title: logitech-djreceiver spams Dmesg Status in linux package in Ubuntu: Expired Bug description: the Logitech C537 spams dmesg specifically with: logitech-djreceiver 0003:046D:C537.0005: Unexpected input report number 128 fixed upstream: https://www.spinics.net/lists/linux-input/msg71897.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937872] Re: Bluetooth is not working in Ubuntu 20.04 (dual boot Windows)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937872 Title: Bluetooth is not working in Ubuntu 20.04 (dual boot Windows) Status in linux package in Ubuntu: Expired Bug description: I have dual OS in my Dell laptop, Bluetooth is working in Windows, but not working in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937893] Re: [HP Pavilion x360 Convertible] Touchscreen Misbehaving After Upgrading to Ubuntu 21.04
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937893 Title: [HP Pavilion x360 Convertible] Touchscreen Misbehaving After Upgrading to Ubuntu 21.04 Status in linux package in Ubuntu: Expired Bug description: I just upgraded from Ubuntu 20.10 to 21.04. After the upgrade, the touchscreen of my laptop has started registering random touch events when no touch input is actually being given by the user. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 12:54:15 2021 DistUpgraded: 2021-07-07 09:51:26,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81a9] InstallationDate: Installed on 2020-10-10 (286 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Pavilion x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=58c17d38-5a4a-455c-a288-fffc3bd115a2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-07 (17 days ago) dmi.bios.date: 06/25/2018 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.53 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 57.53 dmi.modalias: dmi:bvnInsyde:bvrF.35:bd06/25/2018:br15.35:efr57.53:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.53:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion x360 Convertible dmi.product.sku: Z4Q51PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938076] Re: sporadic system freeze after log in
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938076 Title: sporadic system freeze after log in Status in linux package in Ubuntu: Expired Bug description: With kernel Linux version 5.4.0-77-lowlatency (buildd@lgw01-amd64-028) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #86-Ubuntu SMP PREEMPT Thu Jun 17 03:26:36 UTC 2021 (Ubuntu 5.4.0-77.86-lowlatency 5.4.119) in Ubuntustudio I got two system freezes (video frozen, mouse and keyboard without function) some seconds after login in the last days. In the journal I see in both cases a kernel error referring to drm_kms: - Jul 26 20:26:21 marco-MS-7817 kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:42:pipe A] flip_done timed out Jul 26 20:26:22 marco-MS-7817 systemd[1]: systemd-fsckd.service: Succeeded. Jul 26 20:26:21 marco-MS-7817 systemd-timesyncd[667]: Initial synchronization to time server 91.189.94.4:123 (ntp.ubuntu.com). Jul 26 20:26:21 marco-MS-7817 systemd[1]: Starting Daily apt upgrade and clean activities... Jul 26 20:26:21 marco-MS-7817 systemd[1]: systemd-hostnamed.service: Succeeded. Jul 26 20:26:22 marco-MS-7817 systemd[1]: blueman-mechanism.service: Succeeded. Jul 26 20:26:23 marco-MS-7817 systemd[1]: apt-daily-upgrade.service: Succeeded. Jul 26 20:26:23 marco-MS-7817 systemd[1]: Finished Daily apt upgrade and clean activities. Jul 26 20:26:27 marco-MS-7817 autojack[2631]: JACK MIDI <-> ALSA sequencer MIDI bridge, version 9 built on Sun Oct 13 18:36:50 2019 Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Copyright 2006,2007 Dmitry S. Baikov Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Copyright 2007,2008,2009,2011,2012 Nedko Arnaudov Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Bridge starting... Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Using JACK server 'default' Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Hardware ports will be exported. Jul 26 20:26:32 marco-MS-7817 autojack[2631]: Cannot read socket fd = 6 err = Success Jul 26 20:26:32 marco-MS-7817 autojack[2631]: CheckRes error Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackSocketClientChannel read fail Jul 26 20:26:32 marco-MS-7817 autojack[2631]: Cannot open a2j client Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock Jul 26 20:26:32 marco-MS-7817 autojack[2631]: ERROR: a2j_jack_client_create: Cannot create jack client Jul 26 20:26:32 marco-MS-7817 autojack[2631]: ERROR: a2j_start: a2j_new() failed. Jul 26 20:27:04 marco-MS-7817 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU Jul 26 20:27:04 marco-MS-7817 kernel: rcu: 0-: (60004 ticks this GP) idle=7ca/1/0x4002 softirq=23094/23094 fqs=14881 Jul 26 20:27:04 marco-MS-7817 kernel: (t=6 jiffies g=11765 q=87882) Jul 26 20:27:04 marco-MS-7817 kernel: NMI backtrace for cpu 0 Jul 26 20:27:04 marco-MS-7817 kernel: CPU: 0 PID: 2446 Comm: jackdbus Tainted: G OE 5.4.0-77-lowlatency #86-Ubuntu Jul 26 20:27:04 marco-MS-7817 kernel: Hardware name: MSI MS-7817/H81M-E34 (MS-7817), BIOS V17.5 03/30/2015 Jul 26 20:27:04 marco-MS-7817 kernel: Call Trace: Jul 26 20:27:04 marco-MS-7817 kernel: Jul 26 20:27:04 marco-MS-7817 kernel: dump_stack+0x6d/0x8b Jul 26 20:27:04 marco-MS-7817 kernel: ? lapic_can_unplug_cpu+0x80/0x80 Jul 26 20:27:04 marco-MS-7817 kernel: nmi_cpu_backtrace.cold+0x14/0x53 Jul 26 20:27:04 marco-MS-7817 kernel: nmi_trigger_cpumask_backtrace+0xfa/0x110 Jul 26 20:27:04 marco-MS-7817 kernel: arch_trigger_cpumask_backtrace+0x19/0x20 Jul 26 20:27:04 marco-MS-7817 kernel: rcu_dump_cpu_stacks+0x99/0xcb Jul 26 20:27:04 marco-MS-7817 kernel: rcu_sched_clock_irq.cold+0x25e/0x4f0 Jul 26 20:27:04 marco-MS-7817 kernel: update_process_times+0x2c/0x60 Jul 26 20:27:04 marco-MS-7817 kernel: tick_sched_handle+0x29/0x60 Jul 26 20:27:04 marco-MS-7817 kernel: tick_sched_timer+0x3d/0x80 Jul 26 20:27:04 marco-MS-7817 kernel: __hrtimer_run_queues+0xf7/0x2c0 Jul 26 20:27:04 marco-MS-7817 kernel: ? tick_sched_do_timer+0x60/0x60 Jul 26 20:27:04 marco-MS-7817 kernel: hrtimer_interrupt+0x109/0x220 Jul 26 20:27:04 marco-MS-7817 kernel: smp_apic_timer_interrupt+0x71/0x170 Jul 26 20:27:04 marco-MS-7817 kernel: apic_timer_interrupt+0xf/0x20
[Kernel-packages] [Bug 1939045] Re: Extend ANDROID_BINDER_DEVICES
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939045 Title: Extend ANDROID_BINDER_DEVICES Status in linux package in Ubuntu: Expired Bug description: Would it be possible to extend ANDROID_BINDER_DEVICES to 'binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox- vndbinder' for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938669] Re: Epiphan framegrabbers stream only once then need unbinding/rebinding to uvcvideo to work again
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938669 Title: Epiphan framegrabbers stream only once then need unbinding/rebinding to uvcvideo to work again Status in linux package in Ubuntu: Expired Bug description: Video capture devices made by Epiphan Systems (vendor id 0x2b77) work once, but as soon as the video device is closed (or even if it is kept open but the application issues a VIDIOC_STREAMOFF ioctl) it won't work again - subsequent calls to VIDOC_DQBUF simply hang - until the device is unbound from and rebound to the uvcvideo module. (modprobe -r uvcvideo; modprobe uvcvideo also works). For example: ffplay /dev/video0 -- works fine and shows the captured stream. ffplay /dev/video0 -- when run a second time: hangs and does not capture anything modprobe -r uvcvideo ; modprobe uvcvideo; ffplay /dev/video -- works fine again. Experimenting with the device and the uvcvideo module source code reveals that problem is the device is expecting SET_INTERFACE(0) to be sent to return it to a state where it can accept control requests and start streaming again. The code in uvc_video.c has several comments stating that some bulk- transfer devices require a SET_INTERFACE(0) call to be made before any control commands, even though 0 is already the default and only valid interface value. And, the function uvc_video_init makes such a call (which is why the device starts working again after rebinding to the uvcvideo module). But no such call is made when streaming is stopped then restarted. Furthermore, SET_INTERFACE(0) is the mechanism by which isochronous devices are told to stop streaming, and the comments in uvc_video_stop_streaming state that the UVC specification is unclear on how a bulk-based device should be told to stop streaming, so it is reasonable to expect this particular bulk-based device might be expecting the same SET_INTERFACE(0) call that an isochronous device would get as means of being told to stop streaming. The attached patch fixes the problem for these Epiphan devices by adding a SET_INTERFACE(0) call in two places. Either one by itself is sufficient to resolve the symptoms but I think it is probably safest to include both. The first hunk adds a SET_INTERFACE(0) call in uvc_video_start_streaming, but only in the bulk-based case where 0 is the only possible interface value (it won't mess with an isochronous device that might be set to a different interface). The second hunk modifies the behaviour of uvc_video_stop_streaming to call SET_INTERFACE(0) unconditionally instead of only calling it for isochronous devices. Since interface 0 should already be set on non- isochronous devices, it should be safe to set it again, and this way devices that are expecting it as a signal to stop streaming will get it. The patch is against 5.4.137 in the vanilla kernel.org source tree, but also applies cleanly to the 5.8.63 kernel in Ubuntu 20.4 LTS and to the 5.14-rc3 release candidate kernel. Since this is clearly an upstream issue unrelated to any vendor modifications, should I also submit an upstream bug report directly to bugzilla.kernel.org? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939046] Re: Enable CONFIG_SW_SYNC_USER
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939046 Title: Enable CONFIG_SW_SYNC_USER Status in linux package in Ubuntu: Expired Bug description: Would it be possible to enable SYNC_USER for Waydroid (a new alternative to Anbox) to work OOTB on Ubuntu without having to recompile the kernel? Related to #1939045. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939164] Re: Samba fstab mount does not work
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939164 Title: Samba fstab mount does not work Status in linux package in Ubuntu: Expired Bug description: I use "Linux Mint 20.2 x86_64", since the kernel update to version 5.11.0-25, Samba share access no longer works, only when I start my system with kernel 5.8.0-63 does everything work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939311] Re: system freezes (kernel NULL pointer dereference)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939311 Title: system freezes (kernel NULL pointer dereference) Status in linux package in Ubuntu: Expired Bug description: Probably during linking (or building) of chromium the system froze. REISUB worked and the system rebooted. Looking in the syslog file the following line probably caused the freeze. `BUG: kernel NULL pointer dereference, address: 0018` more in the attachment. If you need anything more, let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 9 16:32:56 2021 InstallationDate: Installed on 2020-08-31 (343 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939845] Re: Kernal update 5.4.0-81 broke samba network
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939845 Title: Kernal update 5.4.0-81 broke samba network Status in linux package in Ubuntu: Expired Status in linux source package in Focal: Invalid Bug description: Introduction: I use Samba for linux/windows based network, this involves a shared, ext4 folder on linux mint pc and ntfs drive on router and ntfs folder on windows 7 pc. thereabouts: I had all previous updates, that were current before kernal 5.4.0-81, and my network worked fine. I used the update manager to install kernal 5.4.0-81, from the tray icons (or whatever they are called in linux), as well as updating the relating dependencies when that popped up. I restarted, and then, I cant, see or acces, the, router storage or windows 7 pc, likewise my windows 7 pc cant, see or access, the linux pc. I waited a good amount of time, and tried restarting, this didnt work. I reverted the kernal and dependencies to their earlier version, still same problem, even after several, restarts and waiting. I notice the modifications to the samba config are still present, that were required for samba to network correctly with, windows pc and router, shares. I then updated to the new kernal again, because it makes no difference, seems as previous kernal has broken share, therefore, fix will likely be same for both now. furthermore: I have asus rt-n65u router with latest firmware. I am using samba (maybe this, has been affected or needs its code updating?). the internet is still working, that are a usb dongle through router, to linux mint pc. System:Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 5.0.5 wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal Machine: Type: Desktop Mobo: MSI model: FM2-A55M-P33 (MS-7721) v: 3.0 serial: UEFI: American Megatrends v: 11.6 date: 02/12/2015 CPU: Topology: Quad Core model: AMD A10-6700 APU with Radeon HD Graphics bits: 64 type: MCP arch: Piledriver rev: 1 L2 cache: 2048 KiB flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 29546 Speed: 2350 MHz min/max: 1800/3700 MHz Core speeds (MHz): 1: 2321 2: 2310 3: 2207 4: 2156 Graphics: Device-1: AMD Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] vendor: PC Partner Limited driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6819 Display: x11 server: X.Org 1.20.11 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD PITCAIRN (DRM 2.50.0 5.4.0-81-generic LLVM 12.0.1) v: 4.5 Mesa 21.3.0-devel (git-513fb54 2021-08-12 focal-oibaf-ppa) direct render: Yes Audio: Device-1: AMD FCH Azalia vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:14.2 chip ID: 1022:780d Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] vendor: PC Partner Limited driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aab0 Device-3: Generalplus USB Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 7-2:2 chip ID: 1b3f:2008 Sound Server: ALSA v: k5.4.0-81-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 02:00.0 chip ID: 10ec:8168 IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 380.08 GiB used: 86.82 GiB (22.8%) ID-1: /dev/sda type: USB vendor: Micron model: MT-32 VLI size: 29.82 GiB speed: 3.0 Gb/s serial: ID-2: /dev/sdb model: BT58SSD10S size: 238.47 GiB speed: 3.0 Gb/s serial: temp: 40 C ID-3: /dev/sdc vendor: SanDisk model: SDSSDHII120G size: 111.79 GiB speed: 3.0 Gb/s serial: temp: 30 C Partition: ID-1: / size: 233.24 GiB used: 78.37 GiB (33.6%) fs: ext4 dev: /dev/sdb2 ID-2: swap-1 size: 55.89 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdc1 Sensors: System Temperatures: cpu: 20.5 C mobo: N/A gpu: radeon temp: 36 C Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 1: deb https: //dl.winehq.org/wine-builds/ubuntu/ bionic main Active apt repos in: /etc/apt/sources.list.d/cybermax-dexter-sdl2-backport-focal.list
[Kernel-packages] [Bug 1939976] Re: touchpad hp 17 4045 nf non reconnu avec noyau 5.4.86
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939976 Title: touchpad hp 17 4045 nf non reconnu avec noyau 5.4.86 Status in linux package in Ubuntu: Expired Bug description: Le touchpad du laptop hp 17 4045 nf n'est pas reconnu avec noyau 5.4.86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940470] Re: Function keys and keyboard backlight not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940470 Title: Function keys and keyboard backlight not working Status in linux package in Ubuntu: Expired Bug description: Samsung Chronos 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940482] Re: [thunderx2] Synchronous external abort: 96000610 [#1] SMP
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
Status in linux package in Ubuntu:
Expired
Status in linux source package in Focal:
Expired
Bug description:
[Impact]:
ThunderX2 will not deploy Focal, Arm64 Cloud Image - 20210811
focal": {"stable": {"content_id": "maas:v2:download", "kflavor": "generic",
"path": "ubuntu/arm64/ga-20.04/focal/20210811/boot-initrd", "product_name":
"maas:boot:ubuntu:arm64:ga-20.04:focal"
[ 286.968817] Internal error: synchronous external abort: 96000610 [#1] SMP
[ 286.975594] Modules linked in: nls_iso8859_1 bcache crc64 zfs(PO)
zunicode(PO) zlua(PO) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O)
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua overlay btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic
ast drm_vram_helper ttm usbhid drm_kms_helper crct10dif_ce hid syscopyarea
ghash_ce sysfillrect sha2_ce qede mpt3sas sha256_arm64 ipmi_ssif sysimgblt uas
sha1_ce fb_sys_fops qed ipmi_devintf igb raid_class drm ipmi_msghandler
scsi_transport_sas ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx usb_storage
aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
[ 287.040312] CPU: 1 PID: 1 Comm: shutdown Tainted: P O
5.4.0-80-generic #90-Ubuntu
[ 287.049083] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS
0ACKL030 06/04/2020
[ 287.057072] pstate: 6049 (nZCv daif +PAN -UAO)
[ 287.061864] pc : igb_rd32+0x30/0xd8 [igb]
[ 287.065865] lr : __igb_shutdown+0x84/0x1d8 [igb]
[ 287.070468] sp : 80001255bb90
[ 287.073769] x29: 80001255bb90 x28: 00bf5434e900
[ 287.079067] x27: x26: 009eef029130
[ 287.084365] x25: x24: 009ed603ce08
[ 287.089663] x23: 80001255bc37 x22: 009eef029000
[ 287.094960] x21: 009ed603ce08 x20: 0008
[ 287.100258] x19: 8000301c0008 x18:
[ 287.10] x17: x16: 0032
[ 287.110853] x15: 0004 x14: 0003
[ 287.116150] x13: x12: 009ed50f3530
[ 287.121448] x11: 009ed50f3478 x10:
[ 287.126745] x9 : 0001 x8 : 00210d00
[ 287.132043] x7 : x6 : 0001
[ 287.137340] x5 : x4 : fe027b2d5c20
[ 287.142638] x3 : 00bf5434e900 x2 :
[ 287.147935] x1 : 8000301c x0 : 890491c4
[ 287.153234] Call trace:
[ 287.155673] igb_rd32+0x30/0xd8 [igb]
[ 287.159326] __igb_shutdown+0x84/0x1d8 [igb]
[ 287.163586] igb_shutdown+0x38/0x90 [igb]
[ 287.167585] pci_device_shutdown+0x48/0x88
[ 287.171670] device_shutdown+0x14c/0x298
[ 287.175582] kernel_restart_prepare+0x48/0x58
[ 287.179925] kernel_restart+0x24/0x80
[ 287.183573] __do_sys_reboot+0x100/0x228
[ 287.187482] __arm64_sys_reboot+0x30/0x40
[ 287.191480] el0_svc_common.constprop.0+0xe4/0x1f0
[ 287.196256] el0_svc_handler+0x38/0xa8
[ 287.13] el0_svc+0x10/0x2c8
[ 287.203124] Code: d503201f f94006a1 b40002c1 8b344033 (b9400273)
[ 287.209320] ---[ end trace b2addffb79e92219 ]---
[ 287.214039] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[ 287.221755] Kernel Offset: disabled
[ 287.225231] CPU features: 0x6002,62000c38
[ 287.229226] Memory Limit: none
[ 287.232296] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b ]---
Rom...
CRC: len=0xf080, cal=0x27ff5de9, img=0x27ff5de9, match!
[Test Case]:
Deploy Focal/Arm64-Generic to a ThunderX2 in the MAAS (Metal As a Service)
provisioner. Using MAAS version: 2.9.3~beta1 (9197-g.afe92bb63) via a snap,
the daily focal image appears to be 20210811
From the kernel teams standpoint this kernel in the initrd, did pass
SRU testing before its release.
[Fix]:
N/A
[Regression]:
Probably No (From Kernel Viewpoint) this could possibly be caused by
something other than kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940482/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940482] Re: [thunderx2] Synchronous external abort: 96000610 [#1] SMP
[Expired for linux (Ubuntu Focal) because there has been no activity for
60 days.]
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940482
Title:
[thunderx2] Synchronous external abort: 96000610 [#1] SMP
Status in linux package in Ubuntu:
Expired
Status in linux source package in Focal:
Expired
Bug description:
[Impact]:
ThunderX2 will not deploy Focal, Arm64 Cloud Image - 20210811
focal": {"stable": {"content_id": "maas:v2:download", "kflavor": "generic",
"path": "ubuntu/arm64/ga-20.04/focal/20210811/boot-initrd", "product_name":
"maas:boot:ubuntu:arm64:ga-20.04:focal"
[ 286.968817] Internal error: synchronous external abort: 96000610 [#1] SMP
[ 286.975594] Modules linked in: nls_iso8859_1 bcache crc64 zfs(PO)
zunicode(PO) zlua(PO) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O)
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua overlay btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear i2c_smbus hid_generic
ast drm_vram_helper ttm usbhid drm_kms_helper crct10dif_ce hid syscopyarea
ghash_ce sysfillrect sha2_ce qede mpt3sas sha256_arm64 ipmi_ssif sysimgblt uas
sha1_ce fb_sys_fops qed ipmi_devintf igb raid_class drm ipmi_msghandler
scsi_transport_sas ahci i2c_algo_bit crc8 gpio_xlp i2c_xlp9xx usb_storage
aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
[ 287.040312] CPU: 1 PID: 1 Comm: shutdown Tainted: P O
5.4.0-80-generic #90-Ubuntu
[ 287.049083] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS
0ACKL030 06/04/2020
[ 287.057072] pstate: 6049 (nZCv daif +PAN -UAO)
[ 287.061864] pc : igb_rd32+0x30/0xd8 [igb]
[ 287.065865] lr : __igb_shutdown+0x84/0x1d8 [igb]
[ 287.070468] sp : 80001255bb90
[ 287.073769] x29: 80001255bb90 x28: 00bf5434e900
[ 287.079067] x27: x26: 009eef029130
[ 287.084365] x25: x24: 009ed603ce08
[ 287.089663] x23: 80001255bc37 x22: 009eef029000
[ 287.094960] x21: 009ed603ce08 x20: 0008
[ 287.100258] x19: 8000301c0008 x18:
[ 287.10] x17: x16: 0032
[ 287.110853] x15: 0004 x14: 0003
[ 287.116150] x13: x12: 009ed50f3530
[ 287.121448] x11: 009ed50f3478 x10:
[ 287.126745] x9 : 0001 x8 : 00210d00
[ 287.132043] x7 : x6 : 0001
[ 287.137340] x5 : x4 : fe027b2d5c20
[ 287.142638] x3 : 00bf5434e900 x2 :
[ 287.147935] x1 : 8000301c x0 : 890491c4
[ 287.153234] Call trace:
[ 287.155673] igb_rd32+0x30/0xd8 [igb]
[ 287.159326] __igb_shutdown+0x84/0x1d8 [igb]
[ 287.163586] igb_shutdown+0x38/0x90 [igb]
[ 287.167585] pci_device_shutdown+0x48/0x88
[ 287.171670] device_shutdown+0x14c/0x298
[ 287.175582] kernel_restart_prepare+0x48/0x58
[ 287.179925] kernel_restart+0x24/0x80
[ 287.183573] __do_sys_reboot+0x100/0x228
[ 287.187482] __arm64_sys_reboot+0x30/0x40
[ 287.191480] el0_svc_common.constprop.0+0xe4/0x1f0
[ 287.196256] el0_svc_handler+0x38/0xa8
[ 287.13] el0_svc+0x10/0x2c8
[ 287.203124] Code: d503201f f94006a1 b40002c1 8b344033 (b9400273)
[ 287.209320] ---[ end trace b2addffb79e92219 ]---
[ 287.214039] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[ 287.221755] Kernel Offset: disabled
[ 287.225231] CPU features: 0x6002,62000c38
[ 287.229226] Memory Limit: none
[ 287.232296] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b ]---
Rom...
CRC: len=0xf080, cal=0x27ff5de9, img=0x27ff5de9, match!
[Test Case]:
Deploy Focal/Arm64-Generic to a ThunderX2 in the MAAS (Metal As a Service)
provisioner. Using MAAS version: 2.9.3~beta1 (9197-g.afe92bb63) via a snap,
the daily focal image appears to be 20210811
From the kernel teams standpoint this kernel in the initrd, did pass
SRU testing before its release.
[Fix]:
N/A
[Regression]:
Probably No (From Kernel Viewpoint) this could possibly be caused by
something other than kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940482/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947432] Re: Display backlight and brightness controls are not working
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** Summary changed: - Display backlight and brightness controls are not working + [HP OMEN 846A] Display backlight and brightness controls are not working ** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1947432 Title: [HP OMEN 846A] Display backlight and brightness controls are not working Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: The screen brightness is stuck at 50% of the max output and the brightness controls/slider do nothing at all. This issue started happening with the nvidia-driver-470 package even before I upgraded from 21.04, and it doesn't happen with 460. The bug manifests in both X11 and Wayland. (and GDM itself before logging in) Setting nvidia-drm.modeset to 1 doesn't seem to affect it either. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14 Uname: Linux 5.13.0-19-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.74 Mon Sep 13 23:09:15 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 03:46:49 2021 DistUpgraded: 2021-10-16 03:03:33,254 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.11.0-37-generic, x86_64: installed acpi-call, 1.1.0, 5.11.0-37-lowlatency, x86_64: installed acpi-call, 1.1.0, 5.13.0-19-generic, x86_64: installed acpi-call, 1.1.0, 5.13.0-19-lowlatency, x86_64: installed nvidia, 470.74, 5.13.0-19-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP106BM [GeForce GTX 1060 Mobile 6GB] [103c:846a] InstallationDate: Installed on 2020-08-06 (436 days ago) InstallationMedia: MachineType: HP OMEN by HP Laptop ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-lowlatency root=UUID=4d38cd06-3a59-420a-be51-f664f12d213d ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 05/11/2018 dmi.bios.release: 15.3 dmi.bios.vendor: AMI dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 846A dmi.board.vendor: HP dmi.board.version: 68.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 68.19 dmi.modalias: dmi:bvnAMI:bvrF.03:bd05/11/2018:br15.3:efr68.19:svnHP:pnOMENbyHPLaptop:pvr:sku4PM48EA#ABV:rvnHP:rn846A:rvr68.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4PM48EA#ABV dmi.sys.vendor: HP nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1947432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947432] [NEW] Display backlight and brightness controls are not working
You have been subscribed to a public bug: The screen brightness is stuck at 50% of the max output and the brightness controls/slider do nothing at all. This issue started happening with the nvidia-driver-470 package even before I upgraded from 21.04, and it doesn't happen with 460. The bug manifests in both X11 and Wayland. (and GDM itself before logging in) Setting nvidia-drm.modeset to 1 doesn't seem to affect it either. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14 Uname: Linux 5.13.0-19-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.74 Mon Sep 13 23:09:15 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 03:46:49 2021 DistUpgraded: 2021-10-16 03:03:33,254 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.11.0-37-generic, x86_64: installed acpi-call, 1.1.0, 5.11.0-37-lowlatency, x86_64: installed acpi-call, 1.1.0, 5.13.0-19-generic, x86_64: installed acpi-call, 1.1.0, 5.13.0-19-lowlatency, x86_64: installed nvidia, 470.74, 5.13.0-19-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP106BM [GeForce GTX 1060 Mobile 6GB] [103c:846a] InstallationDate: Installed on 2020-08-06 (436 days ago) InstallationMedia: MachineType: HP OMEN by HP Laptop ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-lowlatency root=UUID=4d38cd06-3a59-420a-be51-f664f12d213d ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 05/11/2018 dmi.bios.release: 15.3 dmi.bios.vendor: AMI dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 846A dmi.board.vendor: HP dmi.board.version: 68.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 68.19 dmi.modalias: dmi:bvnAMI:bvrF.03:bd05/11/2018:br15.3:efr68.19:svnHP:pnOMENbyHPLaptop:pvr:sku4PM48EA#ABV:rvnHP:rn846A:rvr68.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4PM48EA#ABV dmi.sys.vendor: HP nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish possible-manual-nvidia-install ubuntu wayland-session -- Display backlight and brightness controls are not working https://bugs.launchpad.net/bugs/1947432 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946808] Re: zfs fails reverting to a previous snapshot on reboot when selected on grub
I did run an update of only one file and I did install another application. Rebooting and reverting back to the last snapshot did work as expected. The application has been removed and I could rerun the update again. According to the Internet the next commands would stop all autozsys snapshots systemctl --user stop zsys-user-savestate.timer systemctl --user disable zsys-user-savestate.timer sudo mv /etc/apt/apt.conf.d/90_zsys_system_autosnapshot /etc/apt/apt.conf.d /90_zsys_system_autosnapshot_disabled but I still have collected a lot of autozsys snapshots, see next list rpool/USERDATA/bertadmin_9ykbc6@211015-proposed 2.08M - 177M - rpool/USERDATA/bertadmin_9ykbc6@autozsys_h1yy2t 92K - 176M - rpool/USERDATA/bertadmin_9ykbc6@211017-proposed 84K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_6g35l0456K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_501rmb520K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_jr1n7t488K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_m29pbs480K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_4h79sx356K - 175M - rpool/USERDATA/root_9ykbc6@211015-proposed 72K - 812K - rpool/USERDATA/root_9ykbc6@211017-proposed 0B - 812K - Did I make an error or should I produce another bug-report? -- 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/1946808 Title: zfs fails reverting to a previous snapshot on reboot when selected on grub Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Impish: Fix Committed Bug description: [Impact] * zfs fails reverting to a previous snapshot on reboot when selected on grub * A miss-merge dropped initramfs hook changes, which result in failing to generate and use a new zfs uid. * Thus revert code to how it was before in https://launchpad.net/ubuntu/+source/zfs-linux/2.0.2-1ubuntu3 [Test Plan] * Create snapshot with $ zsysctl save test-sru --system * Reboot and attempt to boot into test-sru snapshot [Where problems could occur] * The change is to initramfs hook only, thus initrd generation and boot paths are affected. Only latest initrd is rebuilt, rather than old ones, meaning booting initrds of older kernel abis will not be resolved. [Other Info] * Original bug report After creating a snapshot with: zsysctl save 211012-linux13-19 -s the reboot fails as shown on the screenshot, the other screenshot shows the result of the snapshot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zsys 0.5.8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Oct 12 19:11:43 2021 InstallationDate: Installed on 2021-10-12 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Mounts: Error: [Errno 40] Too many levels of symbolic links: '/proc/mounts' ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zgtuq6@/vmlinuz-5.13.0-19-generic root=ZFS=rpool/ROOT/ubuntu_zgtuq6 ro quiet splash RelatedPackageVersions: zfs-initramfs 2.0.6-1ubuntu2 zfsutils-linux 2.0.6-1ubuntu2 SourcePackage: zsys SystemdFailedUnits: UpgradeStatus: No upgrade log present (probably fresh install) ZFSImportedPools: NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 768M 79.2M 689M- - 0%10% 1.00xONLINE - rpool14G 3.33G 10.7G- - 1%23% 1.00xONLINE - ZFSListcache-bpool: bpool/boot off on on off on off on off - none- - - - - - - - bpool/BOOT noneoff on on off on off on off - none- - - - - - - - bpool/BOOT/ubuntu_zgtuq6 /boot on on on off on off on off - none- - - - - - - - ZSYSJournal: -- Journal begins at Tue 2021-10-12 18:10:37 AST, ends at Tue 2021-10-12 19:11:52 AST. -- -- No entries -- modified.conffile..etc.apt.apt.conf.d.90_zsys_system_autosnapshot: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946808/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1899953] Re: Crackling audio on Raspberry Pi Desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu) Status: New => Confirmed -- 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/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in PulseAudio: Unknown Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1899953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899953] Re: Crackling audio on Raspberry Pi Desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed -- 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/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in PulseAudio: Unknown Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1899953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Hi Xinwei, I build kernel for testing on bug 1932117 and bug 1943301 with 4 patches backported. https://kernel.ubuntu.com/~ikepanhc/lp1943301.1/ d0228aeb4d65 crypto: hisilicon/sec2 - update SEC initialization and reset a13c97118749 crypto: hisilicon/sec2 - Add workqueue for SEC driver. 57ca81245f4d crypto: hisilicon - Use one workqueue per qm instead of per qp eaebf4c3b103 crypto: hisilicon - Unify hardware error init/uninit into QM Please test to see if there is any risk found. I will run full checkbox test too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947326] Re: [Dell Latitude 7320] Clipping and pointer lag after update to kernel 5.13 (fixed by i915.enable_psr=0)
** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947326 Title: [Dell Latitude 7320] Clipping and pointer lag after update to kernel 5.13 (fixed by i915.enable_psr=0) Status in linux package in Ubuntu: Triaged Bug description: Graphics were working perfectly until update to 21.10. Now I experience graphics lag when typing and moving the pointer, and clipping when scrolling or playing video. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 10:42:19 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-12 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1603715] Re: [Dell DW375] bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume
** Changed in: bluez
Status: Incomplete => Fix Released
--
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/1603715
Title:
[Dell DW375] bluetooth unavailable after rfkill hard (or soft)
unblocking and after suspend/resume
Status in Bluez Utilities:
Fix Released
Status in bluez package in Ubuntu:
Confirmed
Bug description:
DELL Latitude E5510 has a hardware switch to disable and enable
bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
terms of wifi, this works great: After hard unblocking, the device
resumes back to normal operation without any manual intervention. That
was also working with bluetooth as of ubuntu 14.04, kernel 4.2.
In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
is not working any more:
After hard blocking and unblocking
- bluetooth is not working at all
- the applet-indicator remains gray
- bluetooth cannot be enabled with the applet-indicator (see
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
Applet-indicator remains gray
- rfkill list tells me that the kernel knows about the hard unblocking (turns
from "yes" to "no"):
rfkill list bluetooth
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
8: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
The device is a
sudo lsusb
Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Workaround: After a
sudo service bluetooth restart
the bluetooth device turns back to normal operation and the applet-
indicator turns from gray to black (available).
Suggested fix: Make the workaround obsolete.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Jul 17 04:00:58 2016
InstallationDate: Installed on 2014-11-29 (595 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
MachineType: Dell Inc. Latitude E5510
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet
splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1603715/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947525] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1947525 Title: Accessibilty Zoom causes crash/logout Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: Set Zoom on and magnification to 2.0, and magnification pushes content around. Move mouse to side or up and screen will blank and be logged out. It will be extremely difficult to turn off zoom because every attempt to move mouse will cause you to log out. Getting control again: Use Super key, type accessibility, turn off zoom ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ndavie61853 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 19:56:49 2021 InstallationDate: Installed on 2021-10-08 (9 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=96f46122-babc-4e05-a5c6-c3fd6c68df3f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago) dmi.bios.date: 07/01/2021 dmi.bios.release: 3.2 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.02 dmi.board.asset.tag: * dmi.board.name: FRANBMCP06 dmi.board.vendor: Framework dmi.board.version: A6 dmi.chassis.asset.tag: FRANBMCPA6133200KQ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A6 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.02:bd07/01/2021:br3.2:svnFramework:pnLaptop:pvrA6:skuFRANBMCP06:rvnFramework:rnFRANBMCP06:rvrA6:cvnFramework:ct10:cvrA6: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP06 dmi.product.version: A6 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947525] [NEW] Accessibilty Zoom causes crash/logout
Public bug reported: How to reproduce: Set Zoom on and magnification to 2.0, and magnification pushes content around. Move mouse to side or up and screen will blank and be logged out. It will be extremely difficult to turn off zoom because every attempt to move mouse will cause you to log out. Getting control again: Use Super key, type accessibility, turn off zoom ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ndavie61853 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 19:56:49 2021 InstallationDate: Installed on 2021-10-08 (9 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=96f46122-babc-4e05-a5c6-c3fd6c68df3f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago) dmi.bios.date: 07/01/2021 dmi.bios.release: 3.2 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.02 dmi.board.asset.tag: * dmi.board.name: FRANBMCP06 dmi.board.vendor: Framework dmi.board.version: A6 dmi.chassis.asset.tag: FRANBMCPA6133200KQ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A6 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.02:bd07/01/2021:br3.2:svnFramework:pnLaptop:pvrA6:skuFRANBMCP06:rvnFramework:rnFRANBMCP06:rvrA6:cvnFramework:ct10:cvrA6: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP06 dmi.product.version: A6 dmi.sys.vendor: Framework ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947525 Title: Accessibilty Zoom causes crash/logout Status in linux package in Ubuntu: New Bug description: How to reproduce: Set Zoom on and magnification to 2.0, and magnification pushes content around. Move mouse to side or up and screen will blank and be logged out. It will be extremely difficult to turn off zoom because every attempt to move mouse will cause you to log out. Getting control again: Use Super key, type accessibility, turn off zoom ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ndavie61853 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 19:56:49 2021 InstallationDate: Installed on 2021-10-08 (9 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=96f46122-babc-4e05-a5c6-c3fd6c68df3f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago) dmi.bios.date: 07/01/2021 dmi.bios.release: 3.2 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.02 dmi.board.asset.tag: * dmi.board.name: FRANBMCP06 dmi.board.vendor: Framework dmi.board.version: A6 dmi.chassis.asset.tag: FRANBMCPA6133200KQ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A6 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.02:bd07/01/2021:br3.2:svnFramework:pnLaptop:pvrA6:skuFRANBMCP06:rvnFramework:rnFRANBMCP06:rvrA6:cvnFramework:ct10:cvrA6: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP06 dmi.product.version: A6 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
hi all, exactly the same issue here. this is on a Thinkpad E14 Gen 2 (AMD) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
This is still a bug in Ubuntu 21.04 and 21.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: AFter upgrade system shows graphic artefacts for a moment and then text cursor for about minute (it looks like hanged) and then starts. In 19.04 startup required 1 or 2 seconds. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 17:42:27 2019 InstallationDate: Installed on 2019-07-04 (104 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeLspcitxt: VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InstallationDate: Installed on 2019-07-04 (105 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: xorg-server (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash video=hyperv_fb:1900x900 elevator=noop vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 RfKill: Tags: eoan ubuntu Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/1848534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
*** This bug is a duplicate of bug 1945590 *** https://bugs.launchpad.net/bugs/1945590 After thinking more carefully I agree with y-ahmet that is bug IS urgent and should be fixed immediately. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (14 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
Tried some recent mainline kernels again. No luck with 5.13.19, but 5.14.13 is using both displays just fine. (Earlier I had tried 5.14.3 with no luck.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
The bugfix has been working as expected over the past 3 days on my 2 systems: Intel NUC (kernel 5.11.0-37-generic) GCP Instance (kernel 5.11.0-1020-gcp) None of my syncoid jobs have failed, I am no longer using the --no- resume (-s) flag as a workaround. -- 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/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
Still happens on 21.10's 5.13.16-051316-generic with a fairly new HP Pavilion 15. The workaround from Arch doesn't quite help -- internal monitor did work after that but external display is not detected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947453] Re: wayland black screen with white flashes, display corruption, kernel 5.13
I could not apply patches from freedesktop bugtracker as kernel revision in ubuntu is quite different from mainline resolved after I disabled secure boot and installed latest 5.14 mainline builds - https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.14.12/ also bug with brightness is gone in this build -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947453 Title: wayland black screen with white flashes, display corruption, kernel 5.13 Status in linux package in Ubuntu: Confirmed Bug description: After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black screen in wayland session and screen corruption in Xorg session ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 15:49:45 2021 DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1b70] InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA 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.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 2026 F pulseaudio /dev/snd/controlC0: eugene 2026 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag:
Re: [Kernel-packages] [Bug 1947188] Re: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted
Hi, Please find the mentioned details of the respective directories & their permissions. /lib/firmware: *drwxr-xr-x 90 root root 36864 Oct 14 22:58 firmware* /lib/firmware/r128: *drwxr-xr-x 2 root root4096 Oct 14 22:58 r128* Same permission for */lib* as well. On Sat, Oct 16, 2021 at 1:30 PM Juerg Haefliger <1947...@bugs.launchpad.net> wrote: > Hrm. Is /lib a read-only mount? What are the file permissions of > /lib/firmware and /lib/firmware/r128? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1947188 > > Title: > package linux-firmware 1.187.17 failed to install/upgrade: unable to > open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not > permitted > > Status in linux-firmware package in Ubuntu: > New > > Bug description: > this is encountered when I tried apt upgrade > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: linux-firmware 1.187.17 > ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 > Uname: Linux 5.11.0-37-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.20 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: kumaradepu 2858 F pulseaudio > CasperMD5CheckResult: skip > Date: Thu Oct 14 22:53:56 2021 > Dependencies: > > ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': > Operation not permitted > InstallationDate: Installed on 2021-09-24 (20 days ago) > InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 > (20210819) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. > Integrated_Webcam_HD >Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Dell Inc. Latitude 5300 > PackageArchitecture: all > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic > root=UUID=f7268264-7e38-446b-b987-ce6c36322ac6 ro quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged > RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 > SourcePackage: linux-firmware > Title: package linux-firmware 1.187.17 failed to install/upgrade: unable > to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/22/2021 > dmi.bios.release: 1.13 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.13.1 > dmi.board.name: 0932VT > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.13.1:bd01/22/2021:br1.13:svnDellInc.:pnLatitude5300:pvr:sku08B7:rvnDellInc.:rn0932VT:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: Latitude > dmi.product.name: Latitude 5300 > dmi.product.sku: 08B7 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1947188/+subscriptions > > -- 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/1947188 Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: this is encountered when I tried apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.17 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumaradepu 2858 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 14 22:53:56 2021 Dependencies: ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (20 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5300 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1942427] Re: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915
With relation to my previous comment here ^^^, just updated to Linux 5.11.0-37-generic today, and it's third monitor is still not working on there, only version working is Linux 5.11.0-25-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942427 Title: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915 Status in linux package in Ubuntu: Incomplete Bug description: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S30S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET60W(1.35):bd08/10/2020:br1.35:efr1.20:svnLENOVO:pn20L6S30S00:pvrThinkPadT480:rvnLENOVO:rn20L6S30S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S30S00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945136] Re: Broken audio capture subsystem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => 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/1945136 Title: Broken audio capture subsystem Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Bug description: In Impish the problem of capturing audio by discord (from app or browser does not matter) when broadcasting reappeared. The window is being captured or not - it doesn't matter. It looks like a regression. Webcamoid don't capture sound from micro too. If I set gstreamer method instead of ffmpeg 4.4 then sound appears, but very laggy Discord launched in a browser and streaming an adjacent tab does the same. I don't even know what to report on. Looks like a broken audio capture subsystem. ffmpeg -f alsa -i -t 30 out.wav and ffmpeg -f pulse -i -t 30 out.wav captures sound normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2083 F pulseaudio /dev/snd/controlC0: navycat2083 F pulseaudio /dev/snd/controlC1: navycat2083 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 27 05:06:06 2021 InstallationDate: Installed on 2021-05-28 (121 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210526) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=bc8287ed-7647-42ae-8f04-6297f1c30b1d ro nouveau.noaccel=1 nouveau.nofbaccel=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:skuPROJECT_SUB_TAG:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1945136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947498] [NEW] zfs/zpool encryption crash on server 21.10
Public bug reported: Hi, just installed a new HPE microserver with SSD and four harddisks with new 21.10 server and tried to create a zpool with zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd -O encryption=on -O keyformat=passphrase which reproducably crashed twice with the attached kernel message. The zpool then exists, but is not encrypted. zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd without the option works and a subsequent zfs create pool1/sub -o encryption=on -o keyformat=passphrase works as well. Which is, however, not a real workaround for a fully encrypted pool (which worked under 20.04). regards ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 17 12:44:15 2021 InstallationDate: Installed on 2021-10-17 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish uec-images ** Attachment added: "dmesg output of kernel crash" https://bugs.launchpad.net/bugs/1947498/+attachment/5533647/+files/dmesg -- 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/1947498 Title: zfs/zpool encryption crash on server 21.10 Status in zfs-linux package in Ubuntu: New Bug description: Hi, just installed a new HPE microserver with SSD and four harddisks with new 21.10 server and tried to create a zpool with zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd -O encryption=on -O keyformat=passphrase which reproducably crashed twice with the attached kernel message. The zpool then exists, but is not encrypted. zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd without the option works and a subsequent zfs create pool1/sub -o encryption=on -o keyformat=passphrase works as well. Which is, however, not a real workaround for a fully encrypted pool (which worked under 20.04). regards ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 17 12:44:15 2021 InstallationDate: Installed on 2021-10-17 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939628] Re: Fan goes full speed on resume from suspend (Lenovo ThinkPad T460)
Still a problem on latest 20.04 kernel, 5.11.0-38-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939628 Title: Fan goes full speed on resume from suspend (Lenovo ThinkPad T460) Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: On resume from suspend the fan goes full speed. Regression - this only happens intermittently on kernel 5.8.0-63, but happens every time on kernel 5.11.0-25. Running `sensors` after resume shows: ``` $ sensors thinkpad-isa- Adapter: ISA adapter fan1:4776 RPM temp1:N/A temp2:N/A temp3: +0.0°C temp4: +0.0°C temp5: +0.0°C temp6: +0.0°C temp7: +0.0°C temp8: +0.0°C coretemp-isa- Adapter: ISA adapter Package id 0: +30.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+29.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+28.0°C (high = +100.0°C, crit = +100.0°C) BAT0-acpi-0 Adapter: ACPI interface in0: 11.82 V iwlwifi_1-virtual-0 Adapter: Virtual device temp1:+31.0°C pch_skylake-virtual-0 Adapter: Virtual device temp1:+29.5°C BAT1-acpi-0 Adapter: ACPI interface in0: 11.06 V acpitz-acpi-0 Adapter: ACPI interface temp1:+48.0°C (crit = +128.0°C) ``` Using kernel 5.11.0-25, `thinkpad-isa- - temp1` shows a temperature prior to suspend, then it consistently shows `N/A` after resume. Using kernel 5.8.0-63, `thinkpad-isa- - temp1` shows a temperature when the fan control is working normally (which fails intermittently following suspend/resume) and shows `N/A` when it does not work. ``` $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 12 00:47:13 2021 InstallationDate: Installed on 2020-05-02 (466 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939628/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937004] Re: Add additional Mediatek MT7921 WiFi/BT device IDs
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1937004 Title: Add additional Mediatek MT7921 WiFi/BT device IDs Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Some Mediatek MT7921 Bluetooth doesn't work out of box. [Fix] One ID for Lite-On was included in upstream, but we need two additional more from different vendors. [Test Case] With firmware from bug 1936452, this will bring up MT7921 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. == original bug description == Mediatek MT7921 has been added to mainline kernel & firmware. Firmware part is being handled by bug 1936452, and WiFi fw loading failure in bug 1936790. This issue will focus on backport/add device IDs for MT7921: * Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device * Bus 002 Device 003: ID 13d3:3567 IMC Networks linux$ git log --graph --oneline korg/master -- \ drivers/bluetooth/ \ drivers/net/wireless/mediatek/mt76/mt7921/ linux-firmware$ git log --graph --oneline korg/master -- \ mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin \ mediatek/WIFI_RAM_CODE_MT7961_1.bin \ mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin * a7882719 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * 2fd5139f linux-firmware: update firmware for MT7921 WiFi device to 20210612122753 * 42a66e5b linux-firmware: update firmware for MT7921 WiFi device * 58fb90a0 linux-firmware: add frimware for mediatek bluetooth chip (MT7921) * 391fd50d linux-firmware: add firmware for MT7921 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1278 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X135 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-05 (16 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 192f:0616 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (5-button) Bus 001 Device 002: ID 03f0:344a HP, Inc HP USB Slim Keyboard Bus 001 Device 004: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3910 Package: linux-firmware 1.187.15+staging.9 [origin: LP-PPA-vicamo-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9009-oem root=UUID=6ae05750-3063-48a4-92af-626f62ff75fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9009.10+staging.2-oem 5.13.0 RelatedPackageVersions: linux-restricted-modules-5.13.0-9009-oem N/A linux-backports-modules-5.13.0-9009-oem N/A linux-firmware 1.187.15+staging.9 Tags: third-party-packages focal Uname: Linux 5.13.0-9009-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/12/2021 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.8.22 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.8.22:bd07/12/2021:br0.8:svnDellInc.:pnInspiron3910:pvr:sku0AD3:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: Inspiron 3910 dmi.product.sku: 0AD3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1947492] 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 1947492 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/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947492] Re: after update my laptop keyboard is not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: New Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947492] [NEW] after update my laptop keyboard is not working
You have been subscribed to a public bug: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- after update my laptop keyboard is not working https://bugs.launchpad.net/bugs/1947492 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947481] Re: Ubuntu 21.10: Unable to suspend
** Package changed: ubuntu => linux-meta (Ubuntu) -- 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/1947481 Title: Ubuntu 21.10: Unable to suspend Status in linux-meta package in Ubuntu: New Bug description: Device instantly wakes up again after suspend. Happens when suspending either manualy or via power settings. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 02:31:31 2021 InstallationDate: Installed on 2021-10-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1947481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947481] [NEW] Ubuntu 21.10: Unable to suspend
You have been subscribed to a public bug: Device instantly wakes up again after suspend. Happens when suspending either manualy or via power settings. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 02:31:31 2021 InstallationDate: Installed on 2021-10-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bot-comment impish kernel-bug -- Ubuntu 21.10: Unable to suspend https://bugs.launchpad.net/bugs/1947481 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946515] Re: impish provides no linux-modules-nvidia-*-server packages
This bug was fixed in the package linux-restricted-modules - 5.13.0-19.19+1 --- linux-restricted-modules (5.13.0-19.19+1) impish; urgency=medium * impish provides no linux-modules-nvidia-*-server packages (LP: #1946515) - [Packaging] Enable nvidia -server driver modules -- Andrea Righi Wed, 13 Oct 2021 19:55:29 +0200 ** Changed in: linux-restricted-modules (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1946515 Title: impish provides no linux-modules-nvidia-*-server packages Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Impish: Fix Committed Bug description: [Impact] Impish is missing the nvidia server drivers. [Test case] $ apt showsrc linux-restricted-modules | grep -e ^Version: -e server WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Version: 5.13.0-19.19 [Fix] Enable nvidia server in linux-restricted-modules package configuration. This will be considered a day 0 SRU fix. [Regression potential] We may see regressions in the nvidia-server packages, considering that were not enabled before also probably that they have not been tested properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1946515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946808] Re: zfs fails reverting to a previous snapshot on reboot when selected on grub
This bug was fixed in the package zfs-linux - 2.0.6-1ubuntu3 --- zfs-linux (2.0.6-1ubuntu3) jammy; urgency=medium * No-change rebuild to add python3.10. -- Matthias Klose Sat, 16 Oct 2021 22:01:03 +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/1946808 Title: zfs fails reverting to a previous snapshot on reboot when selected on grub Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Impish: Fix Committed Bug description: [Impact] * zfs fails reverting to a previous snapshot on reboot when selected on grub * A miss-merge dropped initramfs hook changes, which result in failing to generate and use a new zfs uid. * Thus revert code to how it was before in https://launchpad.net/ubuntu/+source/zfs-linux/2.0.2-1ubuntu3 [Test Plan] * Create snapshot with $ zsysctl save test-sru --system * Reboot and attempt to boot into test-sru snapshot [Where problems could occur] * The change is to initramfs hook only, thus initrd generation and boot paths are affected. Only latest initrd is rebuilt, rather than old ones, meaning booting initrds of older kernel abis will not be resolved. [Other Info] * Original bug report After creating a snapshot with: zsysctl save 211012-linux13-19 -s the reboot fails as shown on the screenshot, the other screenshot shows the result of the snapshot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zsys 0.5.8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Oct 12 19:11:43 2021 InstallationDate: Installed on 2021-10-12 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Mounts: Error: [Errno 40] Too many levels of symbolic links: '/proc/mounts' ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zgtuq6@/vmlinuz-5.13.0-19-generic root=ZFS=rpool/ROOT/ubuntu_zgtuq6 ro quiet splash RelatedPackageVersions: zfs-initramfs 2.0.6-1ubuntu2 zfsutils-linux 2.0.6-1ubuntu2 SourcePackage: zsys SystemdFailedUnits: UpgradeStatus: No upgrade log present (probably fresh install) ZFSImportedPools: NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 768M 79.2M 689M- - 0%10% 1.00xONLINE - rpool14G 3.33G 10.7G- - 1%23% 1.00xONLINE - ZFSListcache-bpool: bpool/boot off on on off on off on off - none- - - - - - - - bpool/BOOT noneoff on on off on off on off - none- - - - - - - - bpool/BOOT/ubuntu_zgtuq6 /boot on on on off on off on off - none- - - - - - - - ZSYSJournal: -- Journal begins at Tue 2021-10-12 18:10:37 AST, ends at Tue 2021-10-12 19:11:52 AST. -- -- No entries -- modified.conffile..etc.apt.apt.conf.d.90_zsys_system_autosnapshot: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
How to disable "CONFIG_UBSAN_TRAP" and check boot? Or need recompiled 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/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947484] Re: Ubuntu 21.10, 5.13.0-19. System freeze when power cable unplugged
** Description changed: I'm using KDE Plasma on Ubuntu 21.10 with kernel 5.13.0-19. Recently, my laptop has been freezing upon unplugging the power cord. The sysrq keys do not work when this occurs. - When I switch kernels, the problem does not occur. The following - kernels do not freeze when I unplug the power cable. + Previously, the problem appeared to resolve when switching kernels. + However, when I tried to obtain logs, the problem began to occur on all + installed kernels (5.14.12, 5.13.19, and 5.13.18 from + https://kernel.ubuntu.com/~kernel-ppa/mainline/). - * kernel 5.14.12 from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.12/ - * kernel 5.13.19 from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.19/ + Logs cannot be obtained because none appear to be saved to disk during + the crash. (journalctl -k -b -1) - When I boot back into the 5.13.0-19 kernel, the problem recurs. - - I had also tried changing various system settings, bios settings, and - packages, none of which made any difference, aside from switching + Since the problem appears kernel related, I tried removing potentially + problematic kernel options from /etc/default/grub. After removing all + acpi and i915 options (which I had enabled because they had previously + been needed to make the backlight work and reduce gpu crashes), the + problem again *appears* to have resolved with all of the aforementioned kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947484 Title: Ubuntu 21.10, 5.13.0-19. System freeze when power cable unplugged Status in linux package in Ubuntu: Incomplete Bug description: I'm using KDE Plasma on Ubuntu 21.10 with kernel 5.13.0-19. Recently, my laptop has been freezing upon unplugging the power cord. The sysrq keys do not work when this occurs. Previously, the problem appeared to resolve when switching kernels. However, when I tried to obtain logs, the problem began to occur on all installed kernels (5.14.12, 5.13.19, and 5.13.18 from https://kernel.ubuntu.com/~kernel-ppa/mainline/). Logs cannot be obtained because none appear to be saved to disk during the crash. (journalctl -k -b -1) Since the problem appears kernel related, I tried removing potentially problematic kernel options from /etc/default/grub. After removing all acpi and i915 options (which I had enabled because they had previously been needed to make the backlight work and reduce gpu crashes), the problem again *appears* to have resolved with all of the aforementioned kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
