[Kernel-packages] [Bug 1859569] Re: [hns3-0114]net: hns3: fix ETS bandwidth validation bug
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Impact] The corresponding ethernet interface could not be up again. [Fix] cherry picked from commit c2d56897819338eb0ba8b93184f7d10329b36653 net: hns3: fix ETS bandwidth validation bug [Test Case] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Steps to Reproduce] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Actual Results] up fail [Expected Results] up ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] This patch fixes it by calling hclge_buffer_alloc to reallocate buffer when pfc_en changes. c2d568978193 net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867087] Re: When I unplug belkin Thunderbolt 3 dock I get the following call stack dump. The problem doesn't exist in the 4.15.0-76-generic version
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc5/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867087 Title: When I unplug belkin Thunderbolt 3 dock I get the following call stack dump. The problem doesn't exist in the 4.15.0-76-generic version Status in linux package in Ubuntu: Confirmed Bug description: [ 1304.161060] usb 5-3: New USB device found, idVendor=045e, idProduct=07b2 [ 1304.161066] usb 5-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1304.161070] usb 5-3: Product: Microsoft® Nano Transceiver v1.0 [ 1304.161072] usb 5-3: Manufacturer: Microsoft [ 1304.166701] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci:00/:00:1b.0/:02:00.0/:03:01.0/:05:00.0/:06:00.0/:07:00.0/usb5/5-3/5-3:1.0/0003:045E:07B2.0007/input/input29 [ 1304.224536] hid-generic 0003:045E:07B2.0007: input,hidraw6: USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v1.0] on usb-:07:00.0-3/input0 [ 1304.229621] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci:00/:00:1b.0/:02:00.0/:03:01.0/:05:00.0/:06:00.0/:07:00.0/usb5/5-3/5-3:1.1/0003:045E:07B2.0008/input/input30 [ 1304.230277] hid-generic 0003:045E:07B2.0008: input,hidraw7: USB HID v1.11 Mouse [Microsoft Microsoft® Nano Transceiver v1.0] on usb-:07:00.0-3/input1 [ 1304.237060] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci:00/:00:1b.0/:02:00.0/:03:01.0/:05:00.0/:06:00.0/:07:00.0/usb5/5-3/5-3:1.2/0003:045E:07B2.0009/input/input31 [ 1304.280131] usb 1-5: Device not responding to setup address. [ 1304.296446] hid-generic 0003:045E:07B2.0009: input,hiddev1,hidraw8: USB HID v1.11 Device [Microsoft Microsoft® Nano Transceiver v1.0] on usb-:07:00.0-3/input2 [ 1304.487584] usb 1-5: device not accepting address 13, error -71 [ 1304.487624] usb usb1-port5: unable to enumerate USB device [ 1315.059560] pciehp :03:01.0:pcie204: Slot(1): Link Down [ 1315.060651] general protection fault: [#1] SMP NOPTI [ 1315.060658] Modules linked in: igb ptp pps_core dca rfcomm vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) cmac msr bnep snd_hda_codec_hdmi binfmt_misc nls_iso8859_1 hid_multitouch dell_wmi wmi_bmof mxm_wmi intel_wmi_thunderbolt dell_laptop dell_smbios intel_rapl x86_pkg_temp_thermal intel_powerclamp dell_wmi_descriptor dcdbas snd_usb_audio coretemp snd_hda_codec_realtek kvm_intel snd_hda_codec_generic snd_usbmidi_lib kvm snd_seq_midi snd_seq_midi_event irqbypass iwlmvm(OE) intel_cstate mac80211(OE) snd_rawmidi intel_rapl_perf iwlwifi(OE) snd_hda_intel serio_raw cfg80211(OE) snd_hda_codec snd_seq snd_hda_core snd_hwdep rtsx_pci_ms snd_pcm memstick compat(OE) snd_seq_device snd_timer btusb mei_me btrtl mei btbcm btintel snd bluetooth uvcvideo videobuf2_vmalloc ax88179_178a videobuf2_memops [ 1315.060722] idma64 videobuf2_v4l2 virt_dma videobuf2_core input_leds usbnet videodev intel_lpss_pci soundcore mii cdc_acm joydev media intel_lpss ecdh_generic int3403_thermal mac_hid wmi dell_smo8800 int3400_thermal acpi_thermal_rel intel_pch_thermal intel_hid sparse_keymap processor_thermal_device acpi_pad int340x_thermal_zone shpchp intel_soc_dts_iosf sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_microsoft hid_generic usbhid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit psmouse drm_kms_helper syscopyarea sysfillrect sysimgblt nvme fb_sys_fops nvme_core rtsx_pci ahci drm thunderbolt libahci i2c_hid hid video [ 1315.060784] CPU: 0 PID: 117 Comm: kworker/u12:2 Tainted: G OE 4.15.0-88-generic #88-Ubuntu [ 1315.060787] Hardware name: Dell Inc. XPS 15 7590/0T8KGX, BIOS 1.5.0 12/25/2019 [ 1315.060799] Workqueue: pciehp-1 pciehp_power_thread [ 1315.060808] RIP: 0010:remove_files.isra.1+0x24/0x70 [ 1315.060812] RSP: 0018:c0e8c3437b40 EFLAGS: 00010206 [ 1315.060817] RAX: 6b443b5b033b4c4e RBX: 9fc40acd4b00 RCX: [ 1315.060820] RDX: 9fc35b575488 RSI: 9fc40acd4b00 RDI: 9fc4d10a24c8 [ 1315.060823] RBP: c0e8c3437b58 R08: R09: 0001801e0014 [ 1315.060827] R10: R11: R12: 9fc4d10a24c8 [ 1315.060830] R13: 9fc35b575488 R14: R15: 0060 [ 1315.060834] FS: () GS:9fc4fc40() knlGS: [ 1315.060838] CS: 0010 DS: ES: CR0: 80050033 [ 1315.060842] CR2: 55da32bda8a0 CR3: 00047ca0a004 CR4: 003606f0 [ 1315.060845] DR0: DR1: DR2: [ 1315.060849] DR3:
[Kernel-packages] [Bug 1867087] 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/1867087 Title: When I unplug belkin Thunderbolt 3 dock I get the following call stack dump. The problem doesn't exist in the 4.15.0-76-generic version Status in linux package in Ubuntu: Confirmed Bug description: [ 1304.161060] usb 5-3: New USB device found, idVendor=045e, idProduct=07b2 [ 1304.161066] usb 5-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1304.161070] usb 5-3: Product: Microsoft® Nano Transceiver v1.0 [ 1304.161072] usb 5-3: Manufacturer: Microsoft [ 1304.166701] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci:00/:00:1b.0/:02:00.0/:03:01.0/:05:00.0/:06:00.0/:07:00.0/usb5/5-3/5-3:1.0/0003:045E:07B2.0007/input/input29 [ 1304.224536] hid-generic 0003:045E:07B2.0007: input,hidraw6: USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v1.0] on usb-:07:00.0-3/input0 [ 1304.229621] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci:00/:00:1b.0/:02:00.0/:03:01.0/:05:00.0/:06:00.0/:07:00.0/usb5/5-3/5-3:1.1/0003:045E:07B2.0008/input/input30 [ 1304.230277] hid-generic 0003:045E:07B2.0008: input,hidraw7: USB HID v1.11 Mouse [Microsoft Microsoft® Nano Transceiver v1.0] on usb-:07:00.0-3/input1 [ 1304.237060] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci:00/:00:1b.0/:02:00.0/:03:01.0/:05:00.0/:06:00.0/:07:00.0/usb5/5-3/5-3:1.2/0003:045E:07B2.0009/input/input31 [ 1304.280131] usb 1-5: Device not responding to setup address. [ 1304.296446] hid-generic 0003:045E:07B2.0009: input,hiddev1,hidraw8: USB HID v1.11 Device [Microsoft Microsoft® Nano Transceiver v1.0] on usb-:07:00.0-3/input2 [ 1304.487584] usb 1-5: device not accepting address 13, error -71 [ 1304.487624] usb usb1-port5: unable to enumerate USB device [ 1315.059560] pciehp :03:01.0:pcie204: Slot(1): Link Down [ 1315.060651] general protection fault: [#1] SMP NOPTI [ 1315.060658] Modules linked in: igb ptp pps_core dca rfcomm vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) cmac msr bnep snd_hda_codec_hdmi binfmt_misc nls_iso8859_1 hid_multitouch dell_wmi wmi_bmof mxm_wmi intel_wmi_thunderbolt dell_laptop dell_smbios intel_rapl x86_pkg_temp_thermal intel_powerclamp dell_wmi_descriptor dcdbas snd_usb_audio coretemp snd_hda_codec_realtek kvm_intel snd_hda_codec_generic snd_usbmidi_lib kvm snd_seq_midi snd_seq_midi_event irqbypass iwlmvm(OE) intel_cstate mac80211(OE) snd_rawmidi intel_rapl_perf iwlwifi(OE) snd_hda_intel serio_raw cfg80211(OE) snd_hda_codec snd_seq snd_hda_core snd_hwdep rtsx_pci_ms snd_pcm memstick compat(OE) snd_seq_device snd_timer btusb mei_me btrtl mei btbcm btintel snd bluetooth uvcvideo videobuf2_vmalloc ax88179_178a videobuf2_memops [ 1315.060722] idma64 videobuf2_v4l2 virt_dma videobuf2_core input_leds usbnet videodev intel_lpss_pci soundcore mii cdc_acm joydev media intel_lpss ecdh_generic int3403_thermal mac_hid wmi dell_smo8800 int3400_thermal acpi_thermal_rel intel_pch_thermal intel_hid sparse_keymap processor_thermal_device acpi_pad int340x_thermal_zone shpchp intel_soc_dts_iosf sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_microsoft hid_generic usbhid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit psmouse drm_kms_helper syscopyarea sysfillrect sysimgblt nvme fb_sys_fops nvme_core rtsx_pci ahci drm thunderbolt libahci i2c_hid hid video [ 1315.060784] CPU: 0 PID: 117 Comm: kworker/u12:2 Tainted: G OE 4.15.0-88-generic #88-Ubuntu [ 1315.060787] Hardware name: Dell Inc. XPS 15 7590/0T8KGX, BIOS 1.5.0 12/25/2019 [ 1315.060799] Workqueue: pciehp-1 pciehp_power_thread [ 1315.060808] RIP: 0010:remove_files.isra.1+0x24/0x70 [ 1315.060812] RSP: 0018:c0e8c3437b40 EFLAGS: 00010206 [ 1315.060817] RAX: 6b443b5b033b4c4e RBX: 9fc40acd4b00 RCX: [ 1315.060820] RDX: 9fc35b575488 RSI: 9fc40acd4b00 RDI: 9fc4d10a24c8 [ 1315.060823] RBP: c0e8c3437b58 R08: R09: 0001801e0014 [ 1315.060827] R10: R11: R12: 9fc4d10a24c8 [ 1315.060830] R13: 9fc35b575488 R14: R15: 0060 [ 1315.060834] FS: () GS:9fc4fc40() knlGS: [ 1315.060838] CS: 0010 DS: ES: CR0: 80050033 [ 1315.060842] CR2: 55da32bda8a0 CR3: 00047ca0a004 CR4: 003606f0 [ 1315.060845] DR0: DR1: DR2: [ 1315.060849] DR3:
[Kernel-packages] [Bug 1866523] Re: Kernel 5.6-rc4 wont compile with nvidia 440.64
*** This bug is a duplicate of bug 1866074 *** https://bugs.launchpad.net/bugs/1866074 ** This bug has been marked a duplicate of bug 1866074 440.59-0ubuntu0.19.10.2 DKMS Build Fail on Kernel 5.6-rc4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866523 Title: Kernel 5.6-rc4 wont compile with nvidia 440.64 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: According to Nvidia 440.64 should compile with kernel 5.6 Attempted kernel install with UKUU 19.12.1 make.log attached make[1]: Entering directory '/usr/src/linux-headers-5.6.0-050600rc4-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.8-050508-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-23ubuntu2) ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 7 21:31:57 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.5.8-050508-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU104BM [GeForce RTX 2080 Mobile] [1043:135f] InstallationDate: Installed on 2020-03-03 (4 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. ROG G703GXR_G703GXR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-050508-generic root=UUID=3fc82c83-da27-480b-a875-214d33bc18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G703GXR.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G703GXR 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.:bvrG703GXR.302:bd07/11/2019:svnASUSTeKCOMPUTERINC.:pnROGG703GXR_G703GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG703GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG G703GXR_G703GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+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/linux/+bug/1866523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867087] [NEW] When I unplug belkin Thunderbolt 3 dock I get the following call stack dump. The problem doesn't exist in the 4.15.0-76-generic version
Public bug reported: [ 1304.161060] usb 5-3: New USB device found, idVendor=045e, idProduct=07b2 [ 1304.161066] usb 5-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1304.161070] usb 5-3: Product: Microsoft® Nano Transceiver v1.0 [ 1304.161072] usb 5-3: Manufacturer: Microsoft [ 1304.166701] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci:00/:00:1b.0/:02:00.0/:03:01.0/:05:00.0/:06:00.0/:07:00.0/usb5/5-3/5-3:1.0/0003:045E:07B2.0007/input/input29 [ 1304.224536] hid-generic 0003:045E:07B2.0007: input,hidraw6: USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v1.0] on usb-:07:00.0-3/input0 [ 1304.229621] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci:00/:00:1b.0/:02:00.0/:03:01.0/:05:00.0/:06:00.0/:07:00.0/usb5/5-3/5-3:1.1/0003:045E:07B2.0008/input/input30 [ 1304.230277] hid-generic 0003:045E:07B2.0008: input,hidraw7: USB HID v1.11 Mouse [Microsoft Microsoft® Nano Transceiver v1.0] on usb-:07:00.0-3/input1 [ 1304.237060] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci:00/:00:1b.0/:02:00.0/:03:01.0/:05:00.0/:06:00.0/:07:00.0/usb5/5-3/5-3:1.2/0003:045E:07B2.0009/input/input31 [ 1304.280131] usb 1-5: Device not responding to setup address. [ 1304.296446] hid-generic 0003:045E:07B2.0009: input,hiddev1,hidraw8: USB HID v1.11 Device [Microsoft Microsoft® Nano Transceiver v1.0] on usb-:07:00.0-3/input2 [ 1304.487584] usb 1-5: device not accepting address 13, error -71 [ 1304.487624] usb usb1-port5: unable to enumerate USB device [ 1315.059560] pciehp :03:01.0:pcie204: Slot(1): Link Down [ 1315.060651] general protection fault: [#1] SMP NOPTI [ 1315.060658] Modules linked in: igb ptp pps_core dca rfcomm vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) cmac msr bnep snd_hda_codec_hdmi binfmt_misc nls_iso8859_1 hid_multitouch dell_wmi wmi_bmof mxm_wmi intel_wmi_thunderbolt dell_laptop dell_smbios intel_rapl x86_pkg_temp_thermal intel_powerclamp dell_wmi_descriptor dcdbas snd_usb_audio coretemp snd_hda_codec_realtek kvm_intel snd_hda_codec_generic snd_usbmidi_lib kvm snd_seq_midi snd_seq_midi_event irqbypass iwlmvm(OE) intel_cstate mac80211(OE) snd_rawmidi intel_rapl_perf iwlwifi(OE) snd_hda_intel serio_raw cfg80211(OE) snd_hda_codec snd_seq snd_hda_core snd_hwdep rtsx_pci_ms snd_pcm memstick compat(OE) snd_seq_device snd_timer btusb mei_me btrtl mei btbcm btintel snd bluetooth uvcvideo videobuf2_vmalloc ax88179_178a videobuf2_memops [ 1315.060722] idma64 videobuf2_v4l2 virt_dma videobuf2_core input_leds usbnet videodev intel_lpss_pci soundcore mii cdc_acm joydev media intel_lpss ecdh_generic int3403_thermal mac_hid wmi dell_smo8800 int3400_thermal acpi_thermal_rel intel_pch_thermal intel_hid sparse_keymap processor_thermal_device acpi_pad int340x_thermal_zone shpchp intel_soc_dts_iosf sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_microsoft hid_generic usbhid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit psmouse drm_kms_helper syscopyarea sysfillrect sysimgblt nvme fb_sys_fops nvme_core rtsx_pci ahci drm thunderbolt libahci i2c_hid hid video [ 1315.060784] CPU: 0 PID: 117 Comm: kworker/u12:2 Tainted: G OE 4.15.0-88-generic #88-Ubuntu [ 1315.060787] Hardware name: Dell Inc. XPS 15 7590/0T8KGX, BIOS 1.5.0 12/25/2019 [ 1315.060799] Workqueue: pciehp-1 pciehp_power_thread [ 1315.060808] RIP: 0010:remove_files.isra.1+0x24/0x70 [ 1315.060812] RSP: 0018:c0e8c3437b40 EFLAGS: 00010206 [ 1315.060817] RAX: 6b443b5b033b4c4e RBX: 9fc40acd4b00 RCX: [ 1315.060820] RDX: 9fc35b575488 RSI: 9fc40acd4b00 RDI: 9fc4d10a24c8 [ 1315.060823] RBP: c0e8c3437b58 R08: R09: 0001801e0014 [ 1315.060827] R10: R11: R12: 9fc4d10a24c8 [ 1315.060830] R13: 9fc35b575488 R14: R15: 0060 [ 1315.060834] FS: () GS:9fc4fc40() knlGS: [ 1315.060838] CS: 0010 DS: ES: CR0: 80050033 [ 1315.060842] CR2: 55da32bda8a0 CR3: 00047ca0a004 CR4: 003606f0 [ 1315.060845] DR0: DR1: DR2: [ 1315.060849] DR3: DR6: fffe0ff0 DR7: 0400 [ 1315.060851] Call Trace: [ 1315.060863] sysfs_remove_group+0x44/0x90 [ 1315.060870] sysfs_remove_groups+0x2e/0x50 [ 1315.060879] device_remove_attrs+0x47/0x80 [ 1315.060884] device_del+0x161/0x3b0 [ 1315.060890] cdev_device_del+0x1a/0x40 [ 1315.060897] posix_clock_unregister+0x26/0x50 [ 1315.060906] ptp_clock_unregister+0x72/0x80 [ptp] [ 1315.060925] igb_ptp_stop+0x23/0x50 [igb] [ 1315.060938] igb_remove+0x4b/0x170 [igb] [ 1315.060945]
[Kernel-packages] [Bug 1866523] 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/1866523 Title: Kernel 5.6-rc4 wont compile with nvidia 440.64 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: According to Nvidia 440.64 should compile with kernel 5.6 Attempted kernel install with UKUU 19.12.1 make.log attached make[1]: Entering directory '/usr/src/linux-headers-5.6.0-050600rc4-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.8-050508-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-23ubuntu2) ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 7 21:31:57 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.5.8-050508-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU104BM [GeForce RTX 2080 Mobile] [1043:135f] InstallationDate: Installed on 2020-03-03 (4 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. ROG G703GXR_G703GXR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-050508-generic root=UUID=3fc82c83-da27-480b-a875-214d33bc18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G703GXR.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G703GXR 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.:bvrG703GXR.302:bd07/11/2019:svnASUSTeKCOMPUTERINC.:pnROGG703GXR_G703GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG703GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG G703GXR_G703GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+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/linux/+bug/1866523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866745] 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 1866745 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/1866745 Title: Extreme slow Ubuntu startup Status in linux package in Ubuntu: Incomplete Bug description: With the latest live release, starting takes around 4:30 to get to the jingle and around 5:40 to get Ubuntu up and running. With the version of 24-01-2020 instead 0:47 and 1:08 respectively. The boot time with the latest releases is exaggerated. Please check and correct the problem. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865402] Re: Stop using get_scalar_status command in Dell AIO uart backlight driver
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865402 Title: Stop using get_scalar_status command in Dell AIO uart backlight driver Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: New Status in linux source package in Focal: Incomplete Bug description: [Impact] The get_scalar_status command was provided by ODM engineer and was newly introduced to determinate whether scalar is responsible for the backlight adjustment. That guy asked the scalar vendor to add this command and the command works as expected. But there is already a command in the Dell AIO scalar UART command spec. which can do the same thing since 2015, and the newly introduced get_scalar_status command is undocumented. To prevent from introducing regression in the future and to align with what Windows uses, replace this command with get_display_mode command. [Fix] Replace get_scalar_status command with get_display_mode command. [Test] Verified on new Dell AIO platforms. [Regression Potential] Low, the command is already in the spec. since 2015. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend
Ok, can you please run # echo 'file drivers/pci/* +p' > /sys/kernel/debug/dynamic_debug/control Then suspend and resume the system, and attach dmesg here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865471 Title: USB 3.1 Gen 1 not work after using suspend Status in linux package in Ubuntu: Incomplete Bug description: Good morning. There many months than I use "suspend" (settings -> energy -> When the shutdown button...) on Ubuntu 18.04 or 19.10. But at each wake up from my computer, the USB 3.1 Gen 1 ports (only motherboard back panel) no work after (loose use of webcam, keyboard...). No problems with USB 3.1 Gen 1 and USB 2.0/1.1 front panel (from internal USB header). No problems with USB 2.0/1.1 ports (motherboard back panel). I think my motherboard is not at fault because I did not reproduce this bug on Windows 10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christophe 1648 F pulseaudio /dev/snd/controlC2: christophe 1648 F pulseaudio /dev/snd/controlC0: christophe 1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-18 (14 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. A320M-S2H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.173.15 RfKill: Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: christophe 1565 F pulseaudio /dev/snd/controlC0: christophe 1565 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-18 (15 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. A320M-S2H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.173.15 RfKill: Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3
Should be picked up by later Stable update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866427] Re: bluetooth mouse wheel not working after suspend/reconnect
** Changed in: bluez (Ubuntu) Status: New => Invalid -- 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/1866427 Title: bluetooth mouse wheel not working after suspend/reconnect Status in bluez package in Ubuntu: Invalid Bug description: 1) Description: Ubuntu 18.04.4 LTS Release: 18.04 2) bluez: Installed: 5.50-0ubuntu0ppa1 Candidate: 5.50-0ubuntu0ppa1 Version table: *** 5.50-0ubuntu0ppa1 500 500 http://ppa.launchpad.net/bluetooth/bluez/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 5.48-0ubuntu3.3 500 500 http://ftp.daum.net/ubuntu bionic-updates/main amd64 Packages 5.48-0ubuntu3 500 500 http://ftp.daum.net/ubuntu bionic/main amd64 Packages 3) My bluetooth mouse(Surface Precision Mouse) wheel is not working after suspended. It's working fine at first. This phenomenon occurs after suspended. It's not only for pc suspended but also mouse power on/off. Both the mouse cursor and click are normal. Only the wheels do not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1866427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866523] Re: Kernel 5.6-rc4 wont compile with nvidia 440.64
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866523 Title: Kernel 5.6-rc4 wont compile with nvidia 440.64 Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: According to Nvidia 440.64 should compile with kernel 5.6 Attempted kernel install with UKUU 19.12.1 make.log attached make[1]: Entering directory '/usr/src/linux-headers-5.6.0-050600rc4-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.8-050508-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-23ubuntu2) ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 7 21:31:57 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.5.8-050508-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU104BM [GeForce RTX 2080 Mobile] [1043:135f] InstallationDate: Installed on 2020-03-03 (4 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. ROG G703GXR_G703GXR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-050508-generic root=UUID=3fc82c83-da27-480b-a875-214d33bc18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G703GXR.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G703GXR 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.:bvrG703GXR.302:bd07/11/2019:svnASUSTeKCOMPUTERINC.:pnROGG703GXR_G703GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG703GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG G703GXR_G703GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+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/linux/+bug/1866523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866745] Re: Extreme slow Ubuntu startup
** Package changed: gnome-shell (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/1866745 Title: Extreme slow Ubuntu startup Status in linux package in Ubuntu: New Bug description: With the latest live release, starting takes around 4:30 to get to the jingle and around 5:40 to get Ubuntu up and running. With the version of 24-01-2020 instead 0:47 and 1:08 respectively. The boot time with the latest releases is exaggerated. Please check and correct the problem. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866745] [NEW] Extreme slow Ubuntu startup
You have been subscribed to a public bug: With the latest live release, starting takes around 4:30 to get to the jingle and around 5:40 to get Ubuntu up and running. With the version of 24-01-2020 instead 0:47 and 1:08 respectively. The boot time with the latest releases is exaggerated. Please check and correct the problem. Thank you. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Extreme slow Ubuntu startup https://bugs.launchpad.net/bugs/1866745 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 1866523] [NEW] Kernel 5.6-rc4 wont compile with nvidia 440.64
You have been subscribed to a public bug: According to Nvidia 440.64 should compile with kernel 5.6 Attempted kernel install with UKUU 19.12.1 make.log attached make[1]: Entering directory '/usr/src/linux-headers-5.6.0-050600rc4-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.8-050508-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-23ubuntu2) ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 7 21:31:57 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.5.8-050508-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU104BM [GeForce RTX 2080 Mobile] [1043:135f] InstallationDate: Installed on 2020-03-03 (4 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. ROG G703GXR_G703GXR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-050508-generic root=UUID=3fc82c83-da27-480b-a875-214d33bc18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G703GXR.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G703GXR 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.:bvrG703GXR.302:bd07/11/2019:svnASUSTeKCOMPUTERINC.:pnROGG703GXR_G703GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG703GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG G703GXR_G703GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ubuntu -- Kernel 5.6-rc4 wont compile with nvidia 440.64 https://bugs.launchpad.net/bugs/1866523 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 1866427] Re: bluetooth mouse wheel not working after suspend/reconnect
'5.50-0ubuntu0ppa1' is not part of Ubuntu and is not supported. Please remove that PPA from your system and then if the problem persists open a new bug by running: ubuntu-bug bluez or ubuntu-bug linux ** Tags added: bionic -- 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/1866427 Title: bluetooth mouse wheel not working after suspend/reconnect Status in bluez package in Ubuntu: New Bug description: 1) Description: Ubuntu 18.04.4 LTS Release: 18.04 2) bluez: Installed: 5.50-0ubuntu0ppa1 Candidate: 5.50-0ubuntu0ppa1 Version table: *** 5.50-0ubuntu0ppa1 500 500 http://ppa.launchpad.net/bluetooth/bluez/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 5.48-0ubuntu3.3 500 500 http://ftp.daum.net/ubuntu bionic-updates/main amd64 Packages 5.48-0ubuntu3 500 500 http://ftp.daum.net/ubuntu bionic/main amd64 Packages 3) My bluetooth mouse(Surface Precision Mouse) wheel is not working after suspended. It's working fine at first. This phenomenon occurs after suspended. It's not only for pc suspended but also mouse power on/off. Both the mouse cursor and click are normal. Only the wheels do not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1866427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865269 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Wednesday, 11. March 2020 15:44 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Stalled -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865419 Title: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865269 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Wednesday, 11. March 2020 15:44 UTC reason: promote-signing-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865402] Re: Stop using get_scalar_status command in Dell AIO uart backlight driver
** Patch added: "0001-UBUNTU-SAUCE-platform-x86-dell-uart-backlight-add-ge.patch" https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1865402/+attachment/5335929/+files/0001-UBUNTU-SAUCE-platform-x86-dell-uart-backlight-add-ge.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865402 Title: Stop using get_scalar_status command in Dell AIO uart backlight driver Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: New Status in linux source package in Focal: Incomplete Bug description: [Impact] The get_scalar_status command was provided by ODM engineer and was newly introduced to determinate whether scalar is responsible for the backlight adjustment. That guy asked the scalar vendor to add this command and the command works as expected. But there is already a command in the Dell AIO scalar UART command spec. which can do the same thing since 2015, and the newly introduced get_scalar_status command is undocumented. To prevent from introducing regression in the future and to align with what Windows uses, replace this command with get_display_mode command. [Fix] Replace get_scalar_status command with get_display_mode command. [Test] Verified on new Dell AIO platforms. [Regression Potential] Low, the command is already in the spec. since 2015. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866712] Re: Graphic glitches with Nvidia 440 on Dell XPS 15 9570
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866712 Title: Graphic glitches with Nvidia 440 on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: I am experiencing intermittent graphical glitches. I couldn't find where this had been reported before so please excuse the duplicate if this is a known issue. I tried recording my screen to demonstrate what is happening but, although I am seeing the issue on the desktop, it does not show up in the video. I am using prime-select in intel mode. System:Host: rex Kernel: 5.5.7-050507-generic x86_64 bits: 64 Desktop: Gnome 3.35.91 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: XPS 15 9570 v: N/A serial: Mobo: Dell model: 0D0T05 v: A00 serial: UEFI: Dell v: 1.15.0 date: 12/25/2019 CPU: Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP L2 cache: 9216 KiB Speed: 2057 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 2112 2: 894 3: 1909 4: 2159 5: 2345 6: 1979 7: 1579 8: 2316 9: 1214 10: 988 11: 2344 12: 929 Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: N/A Display: x11 server: X.Org 1.20.7 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.0.0 Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel Device-2: Texas Instruments PCM2902 Audio Codec type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server: ALSA v: k5.5.7-050507-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.7-050507-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 13:20:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.4.0-14-generic, x86_64: installed nvidia, 440.59, 5.5.7-050507-generic, x86_64: installed v4l2loopback, 0.12.3, 5.5.7-050507-generic, x86_64: installed virtualbox, 6.1.4, 5.5.7-050507-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] InstallationDate: Installed on 2020-03-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.7-050507-generic root=UUID=5490caea-406b-4a4c-afee-178210995fe8 ro quiet splash mem_sleep_default=deep SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867060] Re: brightness
Please check if you have this folder: /sys/bus/acpi/devices/LNXVIDEO:00/physical_node/backlight. You specified acpi_backlight=video, but maybe it's not available from ACPI Video device. Please try removing acpi_backlight=video from boot parameters. ** Summary changed: - brightness + no brightness control support on Aspire A715-72G -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867060 Title: no brightness control support on Aspire A715-72G Status in linux package in Ubuntu: Confirmed Bug description: Brightness disappear, no entries in /sys/class/backlight ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brian 1822 F pulseaudio /dev/snd/controlC1: brian 1822 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 03:10:15 2020 InstallationDate: Installed on 2020-03-10 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c03 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A715-72G ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=405a07bf-f671-40e7-984b-b478fb7b70e3 ro quiet splash nomodeset acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmeleon_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnAspireA715-72G:pvrV1.28:rvnCFL:rnCharmeleon_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-72G dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866712] 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/1866712 Title: Graphic glitches with Nvidia 440 on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: I am experiencing intermittent graphical glitches. I couldn't find where this had been reported before so please excuse the duplicate if this is a known issue. I tried recording my screen to demonstrate what is happening but, although I am seeing the issue on the desktop, it does not show up in the video. I am using prime-select in intel mode. System:Host: rex Kernel: 5.5.7-050507-generic x86_64 bits: 64 Desktop: Gnome 3.35.91 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: XPS 15 9570 v: N/A serial: Mobo: Dell model: 0D0T05 v: A00 serial: UEFI: Dell v: 1.15.0 date: 12/25/2019 CPU: Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP L2 cache: 9216 KiB Speed: 2057 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 2112 2: 894 3: 1909 4: 2159 5: 2345 6: 1979 7: 1579 8: 2316 9: 1214 10: 988 11: 2344 12: 929 Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: N/A Display: x11 server: X.Org 1.20.7 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.0.0 Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel Device-2: Texas Instruments PCM2902 Audio Codec type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server: ALSA v: k5.5.7-050507-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.7-050507-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 13:20:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.4.0-14-generic, x86_64: installed nvidia, 440.59, 5.5.7-050507-generic, x86_64: installed v4l2loopback, 0.12.3, 5.5.7-050507-generic, x86_64: installed virtualbox, 6.1.4, 5.5.7-050507-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] InstallationDate: Installed on 2020-03-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.7-050507-generic root=UUID=5490caea-406b-4a4c-afee-178210995fe8 ro quiet splash mem_sleep_default=deep SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
FYI, the relevant changes are documented in:
https://launchpad.net/ubuntu/+source/alsa-lib/1.1.3-5ubuntu0.3
https://launchpad.net/ubuntu/+source/alsa-lib/1.1.3-5ubuntu0.4
** Package changed: pulseaudio (Ubuntu) => alsa-lib (Ubuntu)
** Changed in: alsa-lib (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in alsa-lib package in Ubuntu:
Fix Committed
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866712] [NEW] Graphic glitches with Nvidia 440 on Dell XPS 15 9570
You have been subscribed to a public bug: I am experiencing intermittent graphical glitches. I couldn't find where this had been reported before so please excuse the duplicate if this is a known issue. I tried recording my screen to demonstrate what is happening but, although I am seeing the issue on the desktop, it does not show up in the video. I am using prime-select in intel mode. System:Host: rex Kernel: 5.5.7-050507-generic x86_64 bits: 64 Desktop: Gnome 3.35.91 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: XPS 15 9570 v: N/A serial: Mobo: Dell model: 0D0T05 v: A00 serial: UEFI: Dell v: 1.15.0 date: 12/25/2019 CPU: Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP L2 cache: 9216 KiB Speed: 2057 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 2112 2: 894 3: 1909 4: 2159 5: 2345 6: 1979 7: 1579 8: 2316 9: 1214 10: 988 11: 2344 12: 929 Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: N/A Display: x11 server: X.Org 1.20.7 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.0.0 Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel Device-2: Texas Instruments PCM2902 Audio Codec type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server: ALSA v: k5.5.7-050507-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.7-050507-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 13:20:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.4.0-14-generic, x86_64: installed nvidia, 440.59, 5.5.7-050507-generic, x86_64: installed v4l2loopback, 0.12.3, 5.5.7-050507-generic, x86_64: installed virtualbox, 6.1.4, 5.5.7-050507-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] InstallationDate: Installed on 2020-03-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.7-050507-generic root=UUID=5490caea-406b-4a4c-afee-178210995fe8 ro quiet splash mem_sleep_default=deep SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal reproducible single-occurrence third-party-packages ubuntu -- Graphic glitches with Nvidia 440 on Dell XPS 15 9570 https://bugs.launchpad.net/bugs/1866712 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 1865499] [NEW] pulseaudio doesn't detect (new) USB headset
You have been subscribed to a public bug:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized, or
the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker and
the "multichannel" microphone are recognized, only one can be used -
either speaker or microphone. When selecting the speaker, the microphone
is switched back to any other device available, them same goes for the
microphone and the speaker - any other speaker is selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a second
headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282) and
it sounds somewhat very familiar, but instead of "env={}" in /usr/share
/ubuntu-drivers-common/detect/sl-modem.py there's "env=env". Removing
"env=env" doesn't resolve the problem.
Do you require additional information?
** Affects: alsa-lib (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Tags: bionic
--
pulseaudio doesn't detect (new) USB headset
https://bugs.launchpad.net/bugs/1865499
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to alsa-lib 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 1862835] Re: [Dell XPS 15 9570] Unable to change laptop screen brightness or keyboard backlighting
Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862835 Title: [Dell XPS 15 9570] Unable to change laptop screen brightness or keyboard backlighting Status in linux package in Ubuntu: Incomplete Bug description: I am running a Dell XPS 15. Updating to 20.04 means that the keyboard bindings for changing the brightness and keypad backlighting don't work. The icons appear on the screen, but the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 09:23:22 2020 DistUpgraded: 2020-02-08 14:25:17,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.2, 5.3.0-29-generic, x86_64: installed virtualbox, 6.1.2, 5.4.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2018-11-21 (447 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=78400725-c498-408a-af83-69891ddf09e4 ro quiet splash nouveau.modeset=0 acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-02-08 (3 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd11/08/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002011830.5c8ff5~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2002030730.a4e627~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2002030730.a4e627~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862835] Re: [Dell XPS 15 9570] Unable to change laptop screen brightness or keyboard backlighting
Someone experiencing this bug on a Dell 9570 please follow the steps in comment #8. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862835 Title: [Dell XPS 15 9570] Unable to change laptop screen brightness or keyboard backlighting Status in linux package in Ubuntu: Incomplete Bug description: I am running a Dell XPS 15. Updating to 20.04 means that the keyboard bindings for changing the brightness and keypad backlighting don't work. The icons appear on the screen, but the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 09:23:22 2020 DistUpgraded: 2020-02-08 14:25:17,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.2, 5.3.0-29-generic, x86_64: installed virtualbox, 6.1.2, 5.4.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2018-11-21 (447 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=78400725-c498-408a-af83-69891ddf09e4 ro quiet splash nouveau.modeset=0 acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-02-08 (3 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd11/08/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002011830.5c8ff5~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2002030730.a4e627~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2002030730.a4e627~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
Thank you Terry Your soloution was perfect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Invalid Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864188] Re: Intel Wireless-AC 9462 [8086:02f0] Subsystem [8086:42a4]: After the upgrade of 19.10 on 2020-02-18, wifi does not exist
*** This bug is a duplicate of bug 1865962 *** https://bugs.launchpad.net/bugs/1865962 Mark duplicate of bug 1865962 according to comment #16. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864188 Title: Intel Wireless-AC 9462 [8086:02f0] Subsystem [8086:42a4]: After the upgrade of 19.10 on 2020-02-18, wifi does not exist Status in linux package in Ubuntu: Confirmed Bug description: lsmod shows the the modules are on, but no wifi hardware seems available. That happened just after the kernel update I did on 18th of Feb. 2020, on Ubuntu 19.10. No other change. System is Dell Vostro 5490/i7 . mgrivas@Vostro:~$ lsmod | grep iwl iwlmvm401408 0 mac80211 851968 1 iwlmvm iwlwifi 348160 1 iwlmvm cfg80211 712704 3 iwlmvm,iwlwifi,mac80211 mgrivas@Vostro:~$ iwconfig no wireless extensions. - The wlan device does not appear. mgrivas@Vostro:~$ lspci | grep -i net 00:14.3 Network controller: Intel Corporation Device 02f0 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) mgrivas@Vostro:~$ cat /proc//version_signature Ubuntu 5.3.0-40.32-generic 5.3.18 mgrivas@Vostro:~$ lspci -vnvns 00:14.3 00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0] Subsystem: Intel Corporation Device [8086:42a4] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mgrivas3042 F pulseaudio /dev/snd/controlC0: mgrivas3042 F pulseaudio /dev/snd/controlC2: mgrivas3042 F pulseaudio Date: Fri Feb 21 11:36:58 2020 InstallationDate: Installed on 2019-12-23 (60 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 5490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=UUID=5107e080-d818-4651-b256-cbd6c7047a2f ro RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0YR1P7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5490:pvr:rvnDellInc.:rn0YR1P7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5490 dmi.product.sku: 0959 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864188] Re: Intel Wireless-AC 9462 [8086:02f0] Subsystem [8086:42a4]: After the upgrade of 19.10 on 2020-02-18, wifi does not exist
*** This bug is a duplicate of bug 1865962 *** https://bugs.launchpad.net/bugs/1865962 @Tiago, since you're on Bionic/Eoan, please go on to install kernel packages from https://people.canonical.com/~acelan/bugs/lp1865829/ directly and see if that also works for you. ** This bug has been marked a duplicate of bug 1865962 Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864188 Title: Intel Wireless-AC 9462 [8086:02f0] Subsystem [8086:42a4]: After the upgrade of 19.10 on 2020-02-18, wifi does not exist Status in linux package in Ubuntu: Confirmed Bug description: lsmod shows the the modules are on, but no wifi hardware seems available. That happened just after the kernel update I did on 18th of Feb. 2020, on Ubuntu 19.10. No other change. System is Dell Vostro 5490/i7 . mgrivas@Vostro:~$ lsmod | grep iwl iwlmvm401408 0 mac80211 851968 1 iwlmvm iwlwifi 348160 1 iwlmvm cfg80211 712704 3 iwlmvm,iwlwifi,mac80211 mgrivas@Vostro:~$ iwconfig no wireless extensions. - The wlan device does not appear. mgrivas@Vostro:~$ lspci | grep -i net 00:14.3 Network controller: Intel Corporation Device 02f0 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) mgrivas@Vostro:~$ cat /proc//version_signature Ubuntu 5.3.0-40.32-generic 5.3.18 mgrivas@Vostro:~$ lspci -vnvns 00:14.3 00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0] Subsystem: Intel Corporation Device [8086:42a4] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mgrivas3042 F pulseaudio /dev/snd/controlC0: mgrivas3042 F pulseaudio /dev/snd/controlC2: mgrivas3042 F pulseaudio Date: Fri Feb 21 11:36:58 2020 InstallationDate: Installed on 2019-12-23 (60 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 5490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=UUID=5107e080-d818-4651-b256-cbd6c7047a2f ro RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0YR1P7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5490:pvr:rvnDellInc.:rn0YR1P7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5490 dmi.product.sku: 0959 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867026] Re: wifi adapter is missing - wrong iwlwifi firmware
Please test kernel from https://people.canonical.com/~acelan/bugs/lp1865829/ . -- 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/1867026 Title: wifi adapter is missing - wrong iwlwifi firmware Status in linux-firmware package in Ubuntu: New Bug description: I managed fo fix the problem, so I'm going to state here my solution first: === The Solution === # sudo rmmod iwlmvm sudo rmmod iwlwifi sudo cp /lib/firmware/iwlwifi-QuZ-a0-jf-b0-48.ucode /lib/firmware/iwlwifi-Qu-b0-jf-b0-48.ucode sudo modprobe iwlwifi # === Bug Report === === 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:KDE neon User Edition 5.18 Release:18.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy linux-firmware linux-firmware: Installed: 1.173.16 Candidate: 1.173.16 Version table: *** 1.173.16 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.12 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu bionic/main i386 Packages 3) What you expected to happen Keep having wifi without any surprise 4) What happened instead surprise surprise: no wifi note: this was not the first time. It happened to me last month (sorry, I can't remember when exactly) === === The Problem === [1] After upgrading packages and reboot, I lost wifi. Actually, `/var/log/kern.log` says: # Mar 11 12:40:32 tc-wildebeest kernel: [0.00] microcode: microcode updated early to revision 0xca, date = 2019-10-03 Mar 11 12:40:32 tc-wildebeest kernel: [0.00] Linux version 5.3.0-40-generic (buildd@lcy01-amd64-024) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 (Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18) # [2] I believe the problem is related to an error on firmware (or choosing the wrong firmware) On `/var/log/kern` # Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997654] iwlwifi :00:14.3: Collecting data: trigger 15 fired. Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997773] iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 11 12:40:32 tc-wildebeest kernel: [ 11.99] iwlwifi :00:14.3: Status: 0x, count: -1355353588 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997780] iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997782] iwlwifi :00:14.3: 0xE439F61B | ADVANCED_SYSASSERT Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997784] iwlwifi :00:14.3: 0x46F73672 | trm_hw_status0 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997786] iwlwifi :00:14.3: 0x28C2A402 | trm_hw_status1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997787] iwlwifi :00:14.3: 0x9DAEAFF4 | branchlink2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997789] iwlwifi :00:14.3: 0x3AF3947B | interruptlink1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997790] iwlwifi :00:14.3: 0x423D8A25 | interruptlink2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997792] iwlwifi :00:14.3: 0x2030A0C5 | data1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997793] iwlwifi :00:14.3: 0xC74F825F | data2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997795] iwlwifi :00:14.3: 0x755A2DAF | data3 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997796] iwlwifi :00:14.3: 0x8C8FD806 | beacon time Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997798] iwlwifi :00:14.3: 0x234581B8 | tsf low Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997799] iwlwifi :00:14.3: 0x9767D27F | tsf hi Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997801] iwlwifi :00:14.3: 0xDEFDFBC2 | time gp1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997803] iwlwifi :00:14.3: 0x0808199E | time gp2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997804] iwlwifi :00:14.3: 0x80539983 | uCode revision type Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997806] iwlwifi :00:14.3: 0xCE7E6303 | uCode version major Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997807] iwlwifi
[Kernel-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
Ivan, Please open a new bug by running: ubuntu-bug linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1865988] Re: Performing function level reset of AMD onboard USB and audio devices causes system lockup
20.04 is a LTS and will be maintained until 2030, so you really don't have to worry about whether it will be shipped with 20.04 ultimately once it makes its way into mainline 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/1865988 Title: Performing function level reset of AMD onboard USB and audio devices causes system lockup Status in linux package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 [Impact] Devices affected: * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Despite advertising FLReset device capabilities, performing a function level reset of either of these devices causes the system to lock up. This is of particular issue where these devices appear in their own IOMMU groups and are well suited to VFIO passthrough. Issue was introduced in AMD's "AGESA Combo-AM4 1.0.0.4 Patch B" microcode update, and affects dozens of motherboard models across various vendors. Additional discussion of this issue: https://www.reddit.com/r/VFIO/comments/eba5mh/workaround_patch_for_passing_through_usb_and/ [Fix] Add a quirk to disable FLR on these devices. Sample patch attached. [Test Case] Peform the test on an impacted system: * B350, B450, X370, X470, X570 motherboards (practically anything with an AM4 socket); * Ryzen 3000-series CPU (2000-series possibly also affected); * BIOS/UEFI firmware that includes "AGESA Combo-AM4 1.0.0.4 Patch B" (check vendor release notes) In the above case where ':10:00.3' is the USB controller '1022:149c', issue a reset command $ echo 1 | sudo tee /sys/bus/pci/devices/\:10\:00.3/reset Impacted systems will not return successfully and become unstable, requiring a reboot. `/var/logs/syslog` will show something resembling the following Mar 4 14:51:26 bunty kernel: [ 1745.043914] xhci_hcd :10:00.3: not ready 1023ms after FLR; waiting Mar 4 14:51:28 bunty kernel: [ 1747.091910] xhci_hcd :10:00.3: not ready 2047ms after FLR; waiting Mar 4 14:51:32 bunty kernel: [ 1750.163972] xhci_hcd :10:00.3: not ready 4095ms after FLR; waiting Mar 4 14:51:37 bunty kernel: [ 1755.283933] xhci_hcd :10:00.3: not ready 8191ms after FLR; waiting Mar 4 14:51:46 bunty kernel: [ 1764.499943] xhci_hcd :10:00.3: not ready 16383ms after FLR; waiting Mar 4 14:52:04 bunty kernel: [ 1782.164126] xhci_hcd :10:00.3: not ready 32767ms after FLR; waiting Mar 4 14:52:39 bunty kernel: [ 1816.979432] xhci_hcd :10:00.3: not ready 65535ms after FLR; giving up Mar 4 14:52:39 bunty kernel: [ 1817.978790] clocksource: timekeeping watchdog on CPU14: Marking clocksource 'tsc' as unstable because the skew is too large: Mar 4 14:52:39 bunty kernel: [ 1817.978806] clocksource: 'hpet' wd_now: f63fcfe wd_last: d468894 mask: Mar 4 14:52:39 bunty kernel: [ 1817.978809] clocksource: 'tsc' cs_now: 60e67e17758 cs_last: 60d2a81ce24 mask: Mar 4 14:52:39 bunty kernel: [ 1817.978818] tsc: Marking TSC unstable due to clocksource watchdog Mar 4 14:52:40 bunty kernel: [ 1817.978892] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Mar 4 14:52:40 bunty kernel: [ 1817.978894] sched_clock: Marking unstable (1817664630139, 314261908)<-(1817981099530, -2209419) [Regression Risk] Unknown --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 19.10 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40+amdnoflr-generic root=UUID=f2f3748c-f017-47ae-aa38-943e5f5189e0 ro amd_iommu=on ProcVersionSignature: Ubuntu 5.3.0-40.32+amdnoflr-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40+amdnoflr-generic N/A linux-backports-modules-5.3.0-40+amdnoflr-generic N/A linux-firmware 1.183.3 Tags: eoan Uname: Linux 5.3.0-40+amdnoflr-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/issues/1377 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865988] Re: Performing function level reset of AMD onboard USB and audio devices causes system lockup
Thanks for the suggestions. I agree that that this patch would benefit the wider community, but I was hoping this particular fix would make it into 20.04. Is there a pathway for getting this patch into the kernel that ultimately ships with 20.04? If so, what does that path look like? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865988 Title: Performing function level reset of AMD onboard USB and audio devices causes system lockup Status in linux package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 [Impact] Devices affected: * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Despite advertising FLReset device capabilities, performing a function level reset of either of these devices causes the system to lock up. This is of particular issue where these devices appear in their own IOMMU groups and are well suited to VFIO passthrough. Issue was introduced in AMD's "AGESA Combo-AM4 1.0.0.4 Patch B" microcode update, and affects dozens of motherboard models across various vendors. Additional discussion of this issue: https://www.reddit.com/r/VFIO/comments/eba5mh/workaround_patch_for_passing_through_usb_and/ [Fix] Add a quirk to disable FLR on these devices. Sample patch attached. [Test Case] Peform the test on an impacted system: * B350, B450, X370, X470, X570 motherboards (practically anything with an AM4 socket); * Ryzen 3000-series CPU (2000-series possibly also affected); * BIOS/UEFI firmware that includes "AGESA Combo-AM4 1.0.0.4 Patch B" (check vendor release notes) In the above case where ':10:00.3' is the USB controller '1022:149c', issue a reset command $ echo 1 | sudo tee /sys/bus/pci/devices/\:10\:00.3/reset Impacted systems will not return successfully and become unstable, requiring a reboot. `/var/logs/syslog` will show something resembling the following Mar 4 14:51:26 bunty kernel: [ 1745.043914] xhci_hcd :10:00.3: not ready 1023ms after FLR; waiting Mar 4 14:51:28 bunty kernel: [ 1747.091910] xhci_hcd :10:00.3: not ready 2047ms after FLR; waiting Mar 4 14:51:32 bunty kernel: [ 1750.163972] xhci_hcd :10:00.3: not ready 4095ms after FLR; waiting Mar 4 14:51:37 bunty kernel: [ 1755.283933] xhci_hcd :10:00.3: not ready 8191ms after FLR; waiting Mar 4 14:51:46 bunty kernel: [ 1764.499943] xhci_hcd :10:00.3: not ready 16383ms after FLR; waiting Mar 4 14:52:04 bunty kernel: [ 1782.164126] xhci_hcd :10:00.3: not ready 32767ms after FLR; waiting Mar 4 14:52:39 bunty kernel: [ 1816.979432] xhci_hcd :10:00.3: not ready 65535ms after FLR; giving up Mar 4 14:52:39 bunty kernel: [ 1817.978790] clocksource: timekeeping watchdog on CPU14: Marking clocksource 'tsc' as unstable because the skew is too large: Mar 4 14:52:39 bunty kernel: [ 1817.978806] clocksource: 'hpet' wd_now: f63fcfe wd_last: d468894 mask: Mar 4 14:52:39 bunty kernel: [ 1817.978809] clocksource: 'tsc' cs_now: 60e67e17758 cs_last: 60d2a81ce24 mask: Mar 4 14:52:39 bunty kernel: [ 1817.978818] tsc: Marking TSC unstable due to clocksource watchdog Mar 4 14:52:40 bunty kernel: [ 1817.978892] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Mar 4 14:52:40 bunty kernel: [ 1817.978894] sched_clock: Marking unstable (1817664630139, 314261908)<-(1817981099530, -2209419) [Regression Risk] Unknown --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 19.10 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40+amdnoflr-generic root=UUID=f2f3748c-f017-47ae-aa38-943e5f5189e0 ro amd_iommu=on ProcVersionSignature: Ubuntu 5.3.0-40.32+amdnoflr-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40+amdnoflr-generic N/A linux-backports-modules-5.3.0-40+amdnoflr-generic N/A linux-firmware 1.183.3 Tags: eoan Uname: Linux 5.3.0-40+amdnoflr-generic x86_64
[Kernel-packages] [Bug 1864188] Re: Intel Wireless-AC 9462 [8086:02f0] Subsystem [8086:42a4]: After the upgrade of 19.10 on 2020-02-18, wifi does not exist
Well, is this the same problem I've described here today?: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1867026 I'm not sure how to test this solution (how to "DKMS package removed/deactivated while testing it"?) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864188 Title: Intel Wireless-AC 9462 [8086:02f0] Subsystem [8086:42a4]: After the upgrade of 19.10 on 2020-02-18, wifi does not exist Status in linux package in Ubuntu: Confirmed Bug description: lsmod shows the the modules are on, but no wifi hardware seems available. That happened just after the kernel update I did on 18th of Feb. 2020, on Ubuntu 19.10. No other change. System is Dell Vostro 5490/i7 . mgrivas@Vostro:~$ lsmod | grep iwl iwlmvm401408 0 mac80211 851968 1 iwlmvm iwlwifi 348160 1 iwlmvm cfg80211 712704 3 iwlmvm,iwlwifi,mac80211 mgrivas@Vostro:~$ iwconfig no wireless extensions. - The wlan device does not appear. mgrivas@Vostro:~$ lspci | grep -i net 00:14.3 Network controller: Intel Corporation Device 02f0 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) mgrivas@Vostro:~$ cat /proc//version_signature Ubuntu 5.3.0-40.32-generic 5.3.18 mgrivas@Vostro:~$ lspci -vnvns 00:14.3 00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0] Subsystem: Intel Corporation Device [8086:42a4] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mgrivas3042 F pulseaudio /dev/snd/controlC0: mgrivas3042 F pulseaudio /dev/snd/controlC2: mgrivas3042 F pulseaudio Date: Fri Feb 21 11:36:58 2020 InstallationDate: Installed on 2019-12-23 (60 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 5490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=UUID=5107e080-d818-4651-b256-cbd6c7047a2f ro RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0YR1P7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5490:pvr:rvnDellInc.:rn0YR1P7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5490 dmi.product.sku: 0959 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867026] Re: wifi adapter is missing - wrong iwlwifi firmware
** Description changed: I managed fo fix the problem, so I'm going to state here my solution first: - === The Solution === # - sudo rmmod iwlmvm + sudo rmmod iwlmvm sudo rmmod iwlwifi sudo cp /lib/firmware/iwlwifi-QuZ-a0-jf-b0-48.ucode /lib/firmware/iwlwifi-Qu-b0-jf-b0-48.ucode sudo modprobe iwlwifi # - - === Bug Report === === 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:KDE neon User Edition 5.18 Release:18.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - $ apt-cache policy linux-firmware + $ apt-cache policy linux-firmware linux-firmware: - Installed: 1.173.16 - Candidate: 1.173.16 - Version table: - *** 1.173.16 500 - 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages - 100 /var/lib/dpkg/status - 1.173.12 500 - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages - 1.173 500 - 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 500 http://br.archive.ubuntu.com/ubuntu bionic/main i386 Packages + Installed: 1.173.16 + Candidate: 1.173.16 + Version table: + *** 1.173.16 500 + 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages + 100 /var/lib/dpkg/status + 1.173.12 500 + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages + 1.173 500 + 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 500 http://br.archive.ubuntu.com/ubuntu bionic/main i386 Packages 3) What you expected to happen Keep having wifi without any surprise 4) What happened instead - surprise surprise: no wifi + surprise surprise: no wifi + + note: this was not the first time. It happened to me last month (sorry, + I can't remember when exactly) + === - - === The Problem === [1] After upgrading packages and reboot, I lost wifi. Actually, `/var/log/kern.log` says: # Mar 11 12:40:32 tc-wildebeest kernel: [0.00] microcode: microcode updated early to revision 0xca, date = 2019-10-03 Mar 11 12:40:32 tc-wildebeest kernel: [0.00] Linux version 5.3.0-40-generic (buildd@lcy01-amd64-024) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 (Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18) # [2] I believe the problem is related to an error on firmware (or choosing the wrong firmware) On `/var/log/kern` # Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997654] iwlwifi :00:14.3: Collecting data: trigger 15 fired. Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997773] iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 11 12:40:32 tc-wildebeest kernel: [ 11.99] iwlwifi :00:14.3: Status: 0x, count: -1355353588 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997780] iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 - Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997782] iwlwifi :00:14.3: 0xE439F61B | ADVANCED_SYSASSERT + Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997782] iwlwifi :00:14.3: 0xE439F61B | ADVANCED_SYSASSERT Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997784] iwlwifi :00:14.3: 0x46F73672 | trm_hw_status0 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997786] iwlwifi :00:14.3: 0x28C2A402 | trm_hw_status1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997787] iwlwifi :00:14.3: 0x9DAEAFF4 | branchlink2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997789] iwlwifi :00:14.3: 0x3AF3947B | interruptlink1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997790] iwlwifi :00:14.3: 0x423D8A25 | interruptlink2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997792] iwlwifi :00:14.3: 0x2030A0C5 | data1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997793] iwlwifi :00:14.3: 0xC74F825F | data2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997795] iwlwifi :00:14.3: 0x755A2DAF | data3 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997796] iwlwifi :00:14.3: 0x8C8FD806 | beacon time Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997798] iwlwifi :00:14.3: 0x234581B8 | tsf low Mar 11 12:40:32 tc-wildebeest kernel: [
[Kernel-packages] [Bug 1862835] Re: [Dell XPS 15 9570] Unable to change laptop screen brightness or keyboard backlighting
Same problem here. Found a mitigation that works: https://github.com/TillmannBerg/Ubuntu-Dell-XPS-15-2019#screen- brightness-oled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862835 Title: [Dell XPS 15 9570] Unable to change laptop screen brightness or keyboard backlighting Status in linux package in Ubuntu: Incomplete Bug description: I am running a Dell XPS 15. Updating to 20.04 means that the keyboard bindings for changing the brightness and keypad backlighting don't work. The icons appear on the screen, but the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 09:23:22 2020 DistUpgraded: 2020-02-08 14:25:17,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.2, 5.3.0-29-generic, x86_64: installed virtualbox, 6.1.2, 5.4.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2018-11-21 (447 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=78400725-c498-408a-af83-69891ddf09e4 ro quiet splash nouveau.modeset=0 acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-02-08 (3 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd11/08/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002011830.5c8ff5~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2002030730.a4e627~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2002030730.a4e627~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861925] Re: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255
I tried Ubuntu Mate 19.10 live on my testing system (AMD Ryzen 5 2500U with Radeon Vega Graphics - seems to be the same AMD CPU on your Acer), and brightness control works without any problems even though actual_brightness has a fixed and higher value. The below is the latest function can be ftrace'd before setting brightness on my AMD platform. https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/amd/display/dc/dce/dce_abm.c#L418 See result of using kprobe-perf (needs to be installed) with writing max (255) to brightness $ sudo kprobe-perf 'p:dce_abm_set_backlight_level_pwm $arg1 $arg2 $arg3 $arg4 $arg5 ' Tracing kprobe dce_abm_set_backlight_level_pwm. Ctrl-C to end. tee-2074 [001] 1009.569878: dce_abm_set_backlight_level_pwm: (dce_abm_set_backlight_level_pwm+0x0/0x410 [amdgpu]) arg1=0x9874e0928900 arg2=0x arg3=0x0 arg4=0x0 arg5=0x0 Note the arg2 = 0x (max brightness) and arg5 = 0 (no "use_smooth_brightness") If you observe the same behaiours but different results, the Acer hardware may have something special that needs attention either from Acer or from 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/1861925 Title: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I have a acer aspire a315-41 laptop, it has BIOS 1.15, Ubuntu 19.10, Kernel stock 5.3, and 5.5.0. I have a problem with the Backlight. I can not control. According to: https://wiki.ubuntu.com/Kernel/Debugging/Backlight It is : Backlight control does not work, but there are entries in /sys/class/backlight. The problem is as far I could find: sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat brightness 135 sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat actual_brightness 43500 sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat max_brightness 255 The brightness read from the HW is not in the range, and when I change the brightness by the keys the value in the brightness file changes too, but the actual_brightness is stuck at the value 43500... I have tried all the steps mentioned in https://wiki.ubuntu.com/Kernel/Debugging/Backlight Actually I have tried all these kernel startup parameter variants without luck: GRUB_CMDLINE_LINUX_DEFAULT="" #GRUB_CMDLINE_LINUX_DEFAULT="video.use_native_backlight=1" #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=" #GRUB_CMDLINE_LINUX_DEFAULT="video.use_bios_initial_backlight=0" #GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dcfeaturemask=0x4 amdgpu.abmlevel=2" #GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=video amdgpu.abmlevel=1" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=Linux acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=video" #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" I guess the fwts has found also this as an error: autobrightness: Automated LCD brightness test. Test 1 of 2: Test for maximum and actual brightness. PASSED: Test 1, Maximum brightness for amdgpu_bl0 is 255 which is sane. FAILED [HIGH] BrightnessOutofRange: Test 1, Actual brightness for amdgpu_bl0 not in range 0..255. Test 2 of 2: Change actual brightness. FAILED [MEDIUM] BrightnessMismatch: Test 2, 256 brightness levels did not match the brightnesss level just set for backlight amdgpu_bl0. The failed brightness levels were: 0-255. It would be great if someone could help set the HW brightness back to the normal range. If you need any more debug files please let me know! Thanks, Regards, Sandor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
Good to know, thanks. Maybe something in the reboot process is exporting
these extra pools, causing them to be removed from the cache.
Have you guys also tried editing /etc/default/zfs and listing your extra
pool(s) there? Specifically:
# List of pools that SHOULD be imported at boot by the initramfs
# instead of trying to import all available pools. If this is set
# then ZFS_POOL_EXCEPTIONS is ignored.
# Only applicable for Debian GNU/Linux {dkms,initramfs}.
# This is a semi-colon separated list.
#ZFS_POOL_IMPORT="pool1;pool2"
There is also ZPOOL_IMPORT_ALL_VISIBLE='no' with a big disclaimer on top
of it.
Not saying that the current behaviour isn't a bug: just investigating
options.
Might need an initramfs update after changing anything in that file,
tough.
--
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/1850130
Title:
zpools fail to import after reboot on fresh install of eoan
Status in zfs-linux package in Ubuntu:
Confirmed
Status in zfs-linux source package in Focal:
Confirmed
Bug description:
Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS.
System has existing zpools with data.
Installation is uneventful. First boot with no problems. Updates
applied. No other changes from fresh installation. Reboot.
External pool 'tank' imports with no errors. Reboot.
External pool has failed to import on boot. In contrast bpool and
rpool are ok. Manually re-import 'tank' with no issues. I can see both
'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache.
Reboot.
'tank' has failed to import on boot. It is also missing from
/etc/zfs/zpool.cache. Is it possible that the cache is being re-
generated on reboot, and the newly imported pools are getting erased
from it? I can re-import the pools again manually with no issues, but
they don't persist between re-boots.
Installing normally on ext4 this is not an issue and data pools import
automatically on boot with no further effort.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864188] Re: Intel Wireless-AC 9462 [8086:02f0] Subsystem [8086:42a4]: After the upgrade of 19.10 on 2020-02-18, wifi does not exist
These packages work, at least the wifi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864188 Title: Intel Wireless-AC 9462 [8086:02f0] Subsystem [8086:42a4]: After the upgrade of 19.10 on 2020-02-18, wifi does not exist Status in linux package in Ubuntu: Confirmed Bug description: lsmod shows the the modules are on, but no wifi hardware seems available. That happened just after the kernel update I did on 18th of Feb. 2020, on Ubuntu 19.10. No other change. System is Dell Vostro 5490/i7 . mgrivas@Vostro:~$ lsmod | grep iwl iwlmvm401408 0 mac80211 851968 1 iwlmvm iwlwifi 348160 1 iwlmvm cfg80211 712704 3 iwlmvm,iwlwifi,mac80211 mgrivas@Vostro:~$ iwconfig no wireless extensions. - The wlan device does not appear. mgrivas@Vostro:~$ lspci | grep -i net 00:14.3 Network controller: Intel Corporation Device 02f0 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) mgrivas@Vostro:~$ cat /proc//version_signature Ubuntu 5.3.0-40.32-generic 5.3.18 mgrivas@Vostro:~$ lspci -vnvns 00:14.3 00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0] Subsystem: Intel Corporation Device [8086:42a4] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mgrivas3042 F pulseaudio /dev/snd/controlC0: mgrivas3042 F pulseaudio /dev/snd/controlC2: mgrivas3042 F pulseaudio Date: Fri Feb 21 11:36:58 2020 InstallationDate: Installed on 2019-12-23 (60 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 5490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=UUID=5107e080-d818-4651-b256-cbd6c7047a2f ro RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0YR1P7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5490:pvr:rvnDellInc.:rn0YR1P7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5490 dmi.product.sku: 0959 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
@ahasenack: The disappearing pools were not exported. To reproduce: * Install with zfs on root option * Import a third pool * Reboot -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867060] 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/1867060 Title: brightness Status in linux package in Ubuntu: Confirmed Bug description: Brightness disappear, no entries in /sys/class/backlight ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brian 1822 F pulseaudio /dev/snd/controlC1: brian 1822 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 03:10:15 2020 InstallationDate: Installed on 2020-03-10 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c03 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A715-72G ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=405a07bf-f671-40e7-984b-b478fb7b70e3 ro quiet splash nomodeset acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmeleon_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnAspireA715-72G:pvrV1.28:rvnCFL:rnCharmeleon_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-72G dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867060] [NEW] brightness
Public bug reported: Brightness disappear, no entries in /sys/class/backlight ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brian 1822 F pulseaudio /dev/snd/controlC1: brian 1822 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 03:10:15 2020 InstallationDate: Installed on 2020-03-10 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c03 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A715-72G ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=405a07bf-f671-40e7-984b-b478fb7b70e3 ro quiet splash nomodeset acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmeleon_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnAspireA715-72G:pvrV1.28:rvnCFL:rnCharmeleon_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-72G dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867060 Title: brightness Status in linux package in Ubuntu: New Bug description: Brightness disappear, no entries in /sys/class/backlight ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brian 1822 F pulseaudio /dev/snd/controlC1: brian 1822 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 03:10:15 2020 InstallationDate: Installed on 2020-03-10 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c03 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A715-72G ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=405a07bf-f671-40e7-984b-b478fb7b70e3 ro quiet splash nomodeset acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmeleon_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnAspireA715-72G:pvrV1.28:rvnCFL:rnCharmeleon_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-72G dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867055] 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/1867055 Title: Regression: Lenovo Yoga C940 hangs while going to sleep Status in linux package in Ubuntu: Confirmed Bug description: With new linux-image-5.3.0-42-generic Lenovo Yoga C940 stopped going to sleep. Whn going to sleep the on/off LED keeps on (instead of blinking) and the laptop is unresponsive. Needs a 4 second power button shutdown. The problem is reproducible every time. linux-image-5.3.0-40-generic doesn't have this problem - laptop goes to sleep and resumes normally. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 21:26:43 2020 InstallationDate: Installed on 2019-11-29 (102 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash intel_pstate=disable vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.184 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-29 (102 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866984] Re: linux-5.4 regression: hibernate-disk resumes instantly
** Summary changed: - hibernate-disk resumes instantly + linux-5.4 regression: hibernate-disk resumes instantly -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1866984 Title: linux-5.4 regression: hibernate-disk resumes instantly Status in hibernate package in Ubuntu: Confirmed Status in linux-5.4 package in Ubuntu: New Bug description: Since upgrading from 19.10 (eoan) to 20.04 (focal), hibernate-disk fails to properly hibernate and shutdown the system; instead, Ubuntu resumes instantly. $ sudo hibernate-disk [sudo] password for xyz: hibernate-disk:Warning: Tuxonice binary signature file not found. $ (Note that this warning has been there earlier and is presumably not associated with this bug.) Expected: Switch to console, memory-page writeout progress indication, poweroff Observed: Switch to console, very quickly switch back to X11 Excerpt from dmesg: [ 418.377514] usbcore: deregistering interface driver uvcvideo [ 419.227465] Filesystems sync: 0.006 seconds [ 419.227468] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 419.229889] OOM killer disabled. [ 419.230429] PM: Marking nosave pages: [mem 0x-0x0fff] [ 419.230432] PM: Marking nosave pages: [mem 0x0009d000-0x000f] [ 419.230440] PM: Marking nosave pages: [mem 0x99438000-0x] [ 419.233760] PM: Basic memory bitmaps created [ 419.234176] PM: Preallocating image memory... done (allocated 1188843 pages) [ 420.040021] PM: Allocated 4755372 kbytes in 0.80 seconds (5944.21 MB/s) [ 420.040021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 420.041324] printk: Suspending console(s) (use no_console_suspend to debug) [ 420.041755] wlp3s0: deauthenticating from cc:ce:1e:61:2e:d0 by local choice (Reason: 3=DEAUTH_LEAVING) [ 421.278599] ACPI: EC: interrupt blocked [ 421.297107] ACPI: Preparing to enter system sleep state S4 [ 421.301832] ACPI: EC: event blocked [ 421.301833] ACPI: EC: EC stopped [ 421.301834] PM: Saving platform NVS memory [ 421.302557] Disabling non-boot CPUs ... [ 421.303996] smpboot: CPU 1 is now offline [ 421.307624] smpboot: CPU 2 is now offline [ 421.309904] IRQ 129: no longer affine to CPU3 [ 421.310921] smpboot: CPU 3 is now offline [ 421.314818] smpboot: CPU 4 is now offline [ 421.317033] IRQ 16: no longer affine to CPU5 [ 421.317040] IRQ 132: no longer affine to CPU5 [ 421.318049] smpboot: CPU 5 is now offline [ 421.320365] IRQ 126: no longer affine to CPU6 [ 421.320373] IRQ 130: no longer affine to CPU6 [ 421.321405] smpboot: CPU 6 is now offline [ 421.325743] smpboot: CPU 7 is now offline [ 421.330059] PM: Creating hibernation image: [ 422.045974] PM: Need to copy 1182218 pages [ 422.045977] PM: Normal pages needed: 1182218 + 1024, available pages: 7053219 [ 423.427947] PM: Hibernation image created (1182218 pages copied) [ 421.330504] PM: Restoring platform NVS memory [ 421.330638] ACPI: EC: EC started [ 421.331412] Enabling non-boot CPUs ... [ 421.331453] x86: Booting SMP configuration: [ 421.331454] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 421.332297] CPU1 is up [ 421.332327] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 421.333137] CPU2 is up [ 421.333164] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 421.333987] CPU3 is up [ 421.334013] smpboot: Booting Node 0 Processor 4 APIC 0x1 [ 421.334926] CPU4 is up [ 421.334956] smpboot: Booting Node 0 Processor 5 APIC 0x3 [ 421.335640] CPU5 is up [ 421.335666] smpboot: Booting Node 0 Processor 6 APIC 0x5 [ 421.336447] CPU6 is up [ 421.336469] smpboot: Booting Node 0 Processor 7 APIC 0x7 [ 421.337232] CPU7 is up [ 421.340095] ACPI: Waking up from system sleep state S4 [ 421.347884] ACPI: EC: interrupt unblocked [ 421.390488] ACPI: EC: event unblocked [ 421.391425] tpm tpm0: tpm_try_transmit: send(): error -5 [ 421.403775] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM [ 421.553049] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM [ 421.603306] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [ 421.634367] iwlwifi :03:00.0: FW already configured (0) - re-configuring [ 421.714565] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 421.715010] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 421.715012] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 421.715083] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded [ 421.715396] ata1.00: supports DRM functions and may not be fully accessible [ 421.716087] ata1.00: disabling queued TRIM support [
[Kernel-packages] [Bug 1866984] Re: hibernate-disk resumes instantly
This seems to be caused by Focal's 5.4 kernel: after booting Ubuntu 19.10's linux-image-5.3.0-40-generic (5.3.0-40.32), which remained on the system after upgrading to 20.04, hibernate-disk (and resume afterwards) works fine. ** Also affects: linux-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1866984 Title: linux-5.4 regression: hibernate-disk resumes instantly Status in hibernate package in Ubuntu: Confirmed Status in linux-5.4 package in Ubuntu: New Bug description: Since upgrading from 19.10 (eoan) to 20.04 (focal), hibernate-disk fails to properly hibernate and shutdown the system; instead, Ubuntu resumes instantly. $ sudo hibernate-disk [sudo] password for xyz: hibernate-disk:Warning: Tuxonice binary signature file not found. $ (Note that this warning has been there earlier and is presumably not associated with this bug.) Expected: Switch to console, memory-page writeout progress indication, poweroff Observed: Switch to console, very quickly switch back to X11 Excerpt from dmesg: [ 418.377514] usbcore: deregistering interface driver uvcvideo [ 419.227465] Filesystems sync: 0.006 seconds [ 419.227468] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 419.229889] OOM killer disabled. [ 419.230429] PM: Marking nosave pages: [mem 0x-0x0fff] [ 419.230432] PM: Marking nosave pages: [mem 0x0009d000-0x000f] [ 419.230440] PM: Marking nosave pages: [mem 0x99438000-0x] [ 419.233760] PM: Basic memory bitmaps created [ 419.234176] PM: Preallocating image memory... done (allocated 1188843 pages) [ 420.040021] PM: Allocated 4755372 kbytes in 0.80 seconds (5944.21 MB/s) [ 420.040021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 420.041324] printk: Suspending console(s) (use no_console_suspend to debug) [ 420.041755] wlp3s0: deauthenticating from cc:ce:1e:61:2e:d0 by local choice (Reason: 3=DEAUTH_LEAVING) [ 421.278599] ACPI: EC: interrupt blocked [ 421.297107] ACPI: Preparing to enter system sleep state S4 [ 421.301832] ACPI: EC: event blocked [ 421.301833] ACPI: EC: EC stopped [ 421.301834] PM: Saving platform NVS memory [ 421.302557] Disabling non-boot CPUs ... [ 421.303996] smpboot: CPU 1 is now offline [ 421.307624] smpboot: CPU 2 is now offline [ 421.309904] IRQ 129: no longer affine to CPU3 [ 421.310921] smpboot: CPU 3 is now offline [ 421.314818] smpboot: CPU 4 is now offline [ 421.317033] IRQ 16: no longer affine to CPU5 [ 421.317040] IRQ 132: no longer affine to CPU5 [ 421.318049] smpboot: CPU 5 is now offline [ 421.320365] IRQ 126: no longer affine to CPU6 [ 421.320373] IRQ 130: no longer affine to CPU6 [ 421.321405] smpboot: CPU 6 is now offline [ 421.325743] smpboot: CPU 7 is now offline [ 421.330059] PM: Creating hibernation image: [ 422.045974] PM: Need to copy 1182218 pages [ 422.045977] PM: Normal pages needed: 1182218 + 1024, available pages: 7053219 [ 423.427947] PM: Hibernation image created (1182218 pages copied) [ 421.330504] PM: Restoring platform NVS memory [ 421.330638] ACPI: EC: EC started [ 421.331412] Enabling non-boot CPUs ... [ 421.331453] x86: Booting SMP configuration: [ 421.331454] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 421.332297] CPU1 is up [ 421.332327] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 421.333137] CPU2 is up [ 421.333164] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 421.333987] CPU3 is up [ 421.334013] smpboot: Booting Node 0 Processor 4 APIC 0x1 [ 421.334926] CPU4 is up [ 421.334956] smpboot: Booting Node 0 Processor 5 APIC 0x3 [ 421.335640] CPU5 is up [ 421.335666] smpboot: Booting Node 0 Processor 6 APIC 0x5 [ 421.336447] CPU6 is up [ 421.336469] smpboot: Booting Node 0 Processor 7 APIC 0x7 [ 421.337232] CPU7 is up [ 421.340095] ACPI: Waking up from system sleep state S4 [ 421.347884] ACPI: EC: interrupt unblocked [ 421.390488] ACPI: EC: event unblocked [ 421.391425] tpm tpm0: tpm_try_transmit: send(): error -5 [ 421.403775] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM [ 421.553049] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM [ 421.603306] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [ 421.634367] iwlwifi :03:00.0: FW already configured (0) - re-configuring [ 421.714565] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 421.715010] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 421.715012] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 421.715083] ata1.00: ACPI cmd
[Kernel-packages] [Bug 1867055] [NEW] Regression: Lenovo Yoga C940 hangs while going to sleep
Public bug reported: With new linux-image-5.3.0-42-generic Lenovo Yoga C940 stopped going to sleep. Whn going to sleep the on/off LED keeps on (instead of blinking) and the laptop is unresponsive. Needs a 4 second power button shutdown. The problem is reproducible every time. linux-image-5.3.0-40-generic doesn't have this problem - laptop goes to sleep and resumes normally. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 21:26:43 2020 InstallationDate: Installed on 2019-11-29 (102 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash intel_pstate=disable vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.184 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-29 (102 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867055 Title: Regression: Lenovo Yoga C940 hangs while going to sleep Status in linux package in Ubuntu: New Bug description: With new linux-image-5.3.0-42-generic Lenovo Yoga C940 stopped going to sleep. Whn going to sleep the on/off LED keeps on (instead of blinking) and the laptop is unresponsive. Needs a 4 second power button shutdown. The problem is reproducible every time. linux-image-5.3.0-40-generic doesn't have this problem - laptop goes to sleep and resumes normally. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 21:26:43 2020 InstallationDate: Installed on 2019-11-29 (102 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash intel_pstate=disable vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.184 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-29 (102 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31
[Kernel-packages] [Bug 1864092] Re: quotactl07 from ubuntu_ltp_syscalls failed
** Tags removed: kqa-blocker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864092 Title: quotactl07 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: == SRU Justification == This quotactl07 is a new test case added in LTP test suite, The test will fail with: <<>> incrementing stop tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-38-generic' tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop4' tst_mkfs.c:90: INFO: Formatting /dev/loop4 with xfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 == Fix == * 3dd4d40b (xfs: Sanity check flags of Q_XQUOTARM call) Focal got this patch from stable update. This patch can be cherry- picked into all the other kernels. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1864092-quotactl07/ All patched kernels are working as expected, == Regression Potential == Low, change limited to quota on XFS, and it's just adding a check for the flags. == Original Bug Report == Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865198 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Sunday, 08. March 2020 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865197 Title: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865198 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Sunday, 08. March 2020 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker
SRU Bugs: https://bugs.launchpad.net/ubuntu-kernel-tests/+bugs?field.tag=sru-20200217+azure_combinator=ALL ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865197 Title: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865198 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Sunday, 08. March 2020 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865243] Re: xenial/linux-kvm: 4.4.0-1068.75 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865106 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Monday, 02. March 2020 08:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1865243 Title: xenial/linux-kvm: 4.4.0-1068.75 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865106 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Monday, 02. March 2020 08:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865193] Re: bionic/linux-azure: 5.0.0-1034.36 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865110 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 02. March 2020 16:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1865192 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865193 Title: bionic/linux-azure: 5.0.0-1034.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865110 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 02. March 2020 16:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1865192 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865247] Re: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Monday, 09. March 2020 13:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1865247 Title: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Monday, 09. March 2020 13:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865243] Re: xenial/linux-kvm: 4.4.0-1068.75 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1865243 Title: xenial/linux-kvm: 4.4.0-1068.75 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865106 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Monday, 02. March 2020 08:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
This failure is test related and not a regression in the kernel, removing the kqa-blocker tag. ** Tags removed: kqa-blocker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865967 Title: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: == SRU Justification == The fill_fs test for XFS in fallocate06 from ubuntu_ltp_syscalls will fail on X/B/D/E: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 8192) fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Fix == * e093c4be (xfs: Fix tail rounding in xfs_alloc_file_space()) This patch can be cherry-picked in D/E and needs some minor context adjustmest on X/B. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1865967-xfs-fallocate06/ All patched kernels are working as expected, this issue will no longer exist on XFS: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop5 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Regression Potential == Low, this ensures all the blocks
[Kernel-packages] [Bug 1865247] Re: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1865247 Title: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Monday, 09. March 2020 13:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 03. March 2020 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1865419 bionic/linux-aws/aws-kernel: bug 1865268 xenial/linux-aws-hwe: bug 1865421 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1865269 Title: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 03. March 2020 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1865419 bionic/linux-aws/aws-kernel: bug 1865268 xenial/linux-aws-hwe: bug 1865421 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865438] Re: eoan/linux-kvm: 5.3.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865111 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 10. March 2020 19:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1865438 Title: eoan/linux-kvm: 5.3.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865111 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 10. March 2020 19:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867051] [NEW] Eoan update: upstream stable patchset 2020-03-11
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2020-03-11
Ported from the following upstream stable releases:
v4.19.103, v5.4.19,
from git://git.kernel.org/
Revert "drm/sun4i: dsi: Change the start delay calculation"
ovl: fix lseek overflow on 32bit
kernel/module: Fix memleak in module_add_modinfo_attrs()
media: iguanair: fix endpoint sanity check
ocfs2: fix oops when writing cloned file
x86/cpu: Update cached HLE state on write to TSX_CTRL_CPUID_CLEAR
udf: Allow writing to 'Rewritable' partitions
printk: fix exclusive_console replaying
iwlwifi: mvm: fix NVM check for 3168 devices
sparc32: fix struct ipc64_perm type definition
cls_rsvp: fix rsvp_policy
gtp: use __GFP_NOWARN to avoid memalloc warning
l2tp: Allow duplicate session creation with UDP
net: hsr: fix possible NULL deref in hsr_handle_frame()
net_sched: fix an OOB access in cls_tcindex
net: stmmac: Delete txtimer in suspend()
bnxt_en: Fix TC queue mapping.
tcp: clear tp->total_retrans in tcp_disconnect()
tcp: clear tp->delivered in tcp_disconnect()
tcp: clear tp->data_segs{in|out} in tcp_disconnect()
tcp: clear tp->segs_{in|out} in tcp_disconnect()
rxrpc: Fix use-after-free in rxrpc_put_local()
rxrpc: Fix insufficient receive notification generation
rxrpc: Fix missing active use pinning of rxrpc_local object
rxrpc: Fix NULL pointer deref due to call->conn being cleared on disconnect
media: uvcvideo: Avoid cyclic entity chains due to malformed USB descriptors
mfd: dln2: More sanity checking for endpoints
ipc/msg.c: consolidate all xxxctl_down() functions
tracing: Fix sched switch start/stop refcount racy updates
rcu: Avoid data-race in rcu_gp_fqs_check_wake()
brcmfmac: Fix memory leak in brcmf_usbdev_qinit
usb: typec: tcpci: mask event interrupts when remove driver
usb: gadget: legacy: set max_speed to super-speed
usb: gadget: f_ncm: Use atomic_t to track in-flight request
usb: gadget: f_ecm: Use atomic_t to track in-flight request
ALSA: usb-audio: Fix endianess in descriptor validation
ALSA: dummy: Fix PCM format loop in proc output
mm/memory_hotplug: fix remove_memory() lockdep splat
mm: move_pages: report the number of non-attempted pages
media/v4l2-core: set pages dirty upon releasing DMA buffers
media: v4l2-core: compat: ignore native command codes
media: v4l2-rect.h: fix v4l2_rect_map_inside() top/left adjustments
lib/test_kasan.c: fix memory leak in kmalloc_oob_krealloc_more()
irqdomain: Fix a memory leak in irq_domain_push_irq()
platform/x86: intel_scu_ipc: Fix interrupt support
ALSA: hda: Add Clevo W65_67SB the power_save blacklist
KVM: arm64: Correct PSTATE on exception entry
KVM: arm/arm64: Correct CPSR on exception entry
KVM: arm/arm64: Correct AArch32 SPSR on exception entry
KVM: arm64: Only sign-extend MMIO up to register width
MIPS: fix indentation of the 'RELOCS' message
MIPS: boot: fix typo in 'vmlinux.lzma.its' target
s390/mm: fix dynamic pagetable upgrade for hugetlbfs
powerpc/xmon: don't access ASDR in VMs
powerpc/pseries: Advance pfn if section is not present in lmb_is_removable()
smb3: fix signing verification of large reads
PCI: tegra: Fix return value check of pm_runtime_get_sync()
mmc: spi: Toggle SPI polarity, do not hardcode it
ACPI: video: Do not export a non working backlight interface on MSI MS-7721
boards
ACPI / battery: Deal with design or full capacity being reported as -1
ACPI / battery: Use design-cap for capacity calculations if full-cap is not
available
ACPI / battery: Deal better with neither design nor full capacity not being
reported
alarmtimer: Unregister wakeup source when module get fails
ubifs: don't trigger assertion on invalid no-key filename
ubifs: Fix FS_IOC_SETFLAGS unexpectedly clearing encrypt flag
ubifs: Fix deadlock in concurrent bulk-read and writepage
PCI: keystone: Fix link training retries initiation
mmc: sdhci-of-at91: fix memleak on clk_get failure
hv_balloon: Balloon up according to request page number
mfd: axp20x: Mark AXP20X_VBUS_IPSOUT_MGMT as volatile
crypto: api - Check spawn->alg under lock in crypto_drop_spawn
crypto: ccree - fix backlog memory leak
crypto: ccree - fix pm wrongful error reporting
crypto: ccree - fix PM race condition
scripts/find-unused-docs: Fix massive false positives
scsi: qla2xxx: Fix mtcp dump collection failure
power: supply: ltc2941-battery-gauge: fix use-after-free
ovl: fix wrong WARN_ON() in ovl_cache_update_ino()
f2fs: choose hardlimit when softlimit is larger than hardlimit in
f2fs_statfs_project()
f2fs: fix miscounted block limit in f2fs_statfs_project()
[Kernel-packages] [Bug 1865193] Re: bionic/linux-azure: 5.0.0-1034.36 -proposed tracker
SRU Bugs: https://bugs.launchpad.net/ubuntu-kernel-tests/+bugs?field.tag=sru-20200217+azure_combinator=ALL ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865193 Title: bionic/linux-azure: 5.0.0-1034.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865110 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 02. March 2020 16:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1865192 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker
SRU Bugs: https://bugs.launchpad.net/ubuntu-kernel-tests/+bugs?field.tag=sru-20200217+aws_combinator=ALL ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1865269 Title: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 03. March 2020 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1865419 bionic/linux-aws/aws-kernel: bug 1865268 xenial/linux-aws-hwe: bug 1865421 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865438] Re: eoan/linux-kvm: 5.3.0-1012.13 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1865438 Title: eoan/linux-kvm: 5.3.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865111 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 10. March 2020 19:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867034] 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 1867034 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/1867034 Title: 18.04 LTS Status in linux package in Ubuntu: Incomplete Bug description: i couldnt turn on my keyboard light even i tried the xset command. My laptop is asus vivobook s14.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
I've never done that manually. Besides it's clear that the pools aren't imported by zfs-import-cache.service anyway. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867034] [NEW] 18.04 LTS
Public bug reported: i couldnt turn on my keyboard light even i tried the xset command. My laptop is asus vivobook s14.. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867034 Title: 18.04 LTS Status in linux package in Ubuntu: New Bug description: i couldnt turn on my keyboard light even i tried the xset command. My laptop is asus vivobook s14.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865199] Re: xenial/linux-fips: 4.4.0-1031.36 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865106 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Tuesday, 10. March 2020 20:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865199 Title: xenial/linux-fips: 4.4.0-1031.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865106 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Tuesday, 10. March 2020 20:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Here's the output to:
-dmesg
-dmidecode
-cat /sys/bus/acpi/devices/{ELAN,SYNA,CRQ}*/modalias
-cat /sys/bus/acpi/devices/{ELAN,SYNA,CRQ}*/status
-cat /sys/bus/i2c/devices/*/name
-ls /sys/bus/i2c/devices/*
Here's Synaptics Hardware Ids from Windows:
HID\VEN_SYNA_2B60
HID\SYNA2B60
HID\*SYNA2B60
HID\VID_06CB:0001_U:0002
HID_DEVICE_SYSTEM_MOUSE
HID_DEVICE_UP:0001_U:0002
HID_DEVICE
** Attachment added: "output of commands"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5335812/+files/output.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853277
Title:
Lenovo ThinkBook 14-IML Touchpad not showing up in
/proc/bus/input/devices
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is happening on a ThinkBook 14 IML 20RV.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1848 F pulseaudio
CasperVersion: 1.427
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 20 11:10:52 2019
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20RV
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.3.0-18-generic N/A
linux-backports-modules-5.3.0-18-generic N/A
linux-firmware1.183
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/10/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: CJCN21WW
dmi.board.name: LVA/LVAB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.modalias:
dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr:
dmi.product.family: ThinkBook 14-IML
dmi.product.name: 20RV
dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML
dmi.product.version: Lenovo ThinkBook 14-IML
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863341] Re: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker
*** This bug is a duplicate of bug 1865203 *** https://bugs.launchpad.net/bugs/1865203 ** This bug has been marked a duplicate of bug 1865203 bionic/linux-fips: 4.15.0-1025.30 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863341 Title: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1864753 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Friday, 21. February 2020 11:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865199] Re: xenial/linux-fips: 4.4.0-1031.36 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865199 Title: xenial/linux-fips: 4.4.0-1031.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865106 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Tuesday, 10. March 2020 20:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865203] Re: bionic/linux-fips: 4.15.0-1025.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 11. March 2020 15:42 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 11. March 2020 17:52 UTC reason: - promote-signing-to-proposed: Stalled -- another kernel is currently - pending in Proposed + promote-signing-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865203 Title: bionic/linux-fips: 4.15.0-1025.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Promote to Proposed phase-changed: Wednesday, 11. March 2020 17:52 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
Did you run "zpool export " before rebooting? IIRC that removes it from the cache file. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866545] Re: zpool missing after reboot
*** This bug is a duplicate of bug 1850130 *** https://bugs.launchpad.net/bugs/1850130 ** This bug has been marked a duplicate of bug 1850130 zpools fail to import after reboot on fresh install of eoan -- 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/1866545 Title: zpool missing after reboot Status in zfs-linux package in Ubuntu: New Bug description: I have installed Ubuntu 20.04 with the new ZFS root partition. This worked fine. However I then created a new volume / pool : zpool create data /dev/sdb Then I mounted it into my home. zfs set mountpoint=/home/peter/data data This worked fine, however after reboot the mount is not longer working. The issue seems to be on the zpool level though. Since the mount starts working right after I do zpool import data Not sure if I am doing something wrong, I have worked on Solaris for many years and thats how you mount stuff. Maybe something different on Ubuntu? Let me know if there are any log files to collect. I did find this in a log search though. syslog:Mar 8 10:20:36 smchome zpool[2656]: no pools available to import To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1866545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
In other words, boot, import the pool, and reboot without exporting it. Sorry if you did that already, I just skimmed the bug and jumped to the last comment. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
or something, the pools don't seem to be ready for import? maalis 11 12:31:59 bryant systemd[1]: Starting Import ZFS pools by cache file... -- Subject: A start job for unit zfs-import-cache.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit zfs-import-cache.service has begun execution. -- -- The job identifier is 15. maalis 11 12:31:59 bryant zpool[2141]: no pools available to import maalis 11 12:31:59 bryant systemd[1]: Started Import ZFS pools by cache file. -- Subject: A start job for unit zfs-import-cache.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit zfs-import-cache.service has finished successfully. -- -- The job identifier is 15. maalis 11 12:31:59 bryant systemd[1]: Reached target ZFS pool import target. -- Subject: A start job for unit zfs-import.target has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit zfs-import.target has finished successfully. -- -- The job identifier is 14. maalis 11 12:31:59 bryant systemd[1]: Mounting /home/tjaalton... -- Subject: A start job for unit home-tjaalton.mount has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit home-tjaalton.mount has begun execution. -- -- The job identifier is 61. maalis 11 12:31:59 bryant systemd[1]: Mounting /root... -- Subject: A start job for unit root.mount has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit root.mount has begun execution. . . . and so on, it mounts everything else during zfs-import but not my /data pool.. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
so I've looked at the cache file, and indeed it looks like it only has entries for both bpool and rpool after booting up, and after 'zpool import data' it gets updated to include that as well my guess is that it gets overwritten during bootup -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863989] Re: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM
Hello Colin, with disk space freed up to 8.3G free on /, this node became more stabilized. Failed once with bad-altstack out of 5 attempts. I think we can call this fixed for now. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863989 Title: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM Status in Stress-ng: Invalid Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Eoan zVM node kernel03 Test hung at bad-altstack test. Reproducible rate: 4 out of 4 attempts 02:36:12 DEBUG| [stdout] aiol STARTING 02:36:17 DEBUG| [stdout] aiol RETURNED 0 02:36:17 DEBUG| [stdout] aiol PASSED 02:36:17 DEBUG| [stdout] bad-altstack STARTING + ARCHIVE=/var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@kernel03:kernel-test-results /var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive dmesg only shows: [ 102.352136] Adding 1048572k swap on /home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/swap.img. Priority:-3 extents:95 across:26763272k SSFS [ 122.402895] NET: Registered protocol family 38 It looks like this is caused by OOM issue, x3270 console flushed with OOM error messages. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-41-generic 5.3.0-41.33 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.4 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Feb 20 06:06:04 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/mapper/kl03vg01-kl03root crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-5.3.0-41-generic N/A linux-backports-modules-5.3.0-41-generic N/A linux-firmware1.183.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-30 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1863989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866925] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1866925/+attachment/5335785/+files/ProcCpuinfoMinimal.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866925 Title: wrong gcc version for kernel prevents DKMS working Status in gcc-7 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of minimal LUbuntu 18.04, fully updated (with new kernel). Install of NVIDIA graphics card drivers from NVIDIA script. DKMS (needed for re-compile with new kernel versions) fails as the available gcc is 7.5.0 from 18.04 and the gcc used for compiling the kernel was 7.4.0 from 18.01. The gcc for the running kernel is no longer available for installation. This mismatch is the bug. There are two alternative solutions: 1. ensure the gcc versions used to compile the available kernels are also available. 2. ensure the kernels are always compiled with the latest available gcc. The former is probably a better solution as the latter may cause unnecessary kernel recompiles as the gcc versions change. The former may require multiple installed versions of gcc, one for each installed kernel version, which would need a method of picking the gcc version which matches the kernel. It would also be useful if one of the meta-packages ensured that the installed gcc matches the installed kernel's compiler. ``` $ uname -a Linux xx 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ``` ... I'm sorry, but the DKMS make.log with the error has been deleted by a later re-run attempt for the install. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gcc 4:7.4.0-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Tue Mar 10 22:40:51 2020 InstallationDate: Installed on 2020-03-10 (0 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-10 (1 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-7/+bug/1866925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866925] Re: wrong gcc version for kernel prevents DKMS working
apport information ** Tags added: apport-collected ** Description changed: Fresh install of minimal LUbuntu 18.04, fully updated (with new kernel). Install of NVIDIA graphics card drivers from NVIDIA script. DKMS (needed for re-compile with new kernel versions) fails as the available gcc is 7.5.0 from 18.04 and the gcc used for compiling the kernel was 7.4.0 from 18.01. The gcc for the running kernel is no longer available for installation. This mismatch is the bug. There are two alternative solutions: 1. ensure the gcc versions used to compile the available kernels are also available. 2. ensure the kernels are always compiled with the latest available gcc. The former is probably a better solution as the latter may cause unnecessary kernel recompiles as the gcc versions change. The former may require multiple installed versions of gcc, one for each installed kernel version, which would need a method of picking the gcc version which matches the kernel. It would also be useful if one of the meta-packages ensured that the installed gcc matches the installed kernel's compiler. ``` $ uname -a Linux xx 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ``` ... I'm sorry, but the DKMS make.log with the error has been deleted by a later re-run attempt for the install. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gcc 4:7.4.0-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Tue Mar 10 22:40:51 2020 InstallationDate: Installed on 2020-03-10 (0 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-03-10 (1 days ago) + InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_GB:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 + Tags: bionic + Uname: Linux 5.3.0-40-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1866925/+attachment/5335784/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866925 Title: wrong gcc version for kernel prevents DKMS working Status in gcc-7 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of minimal LUbuntu 18.04, fully updated (with new kernel). Install of NVIDIA graphics card drivers from NVIDIA script. DKMS (needed for re-compile with new kernel versions) fails as the available gcc is 7.5.0 from 18.04 and the gcc used for compiling the kernel was 7.4.0 from 18.01. The gcc for the running kernel is no longer available for installation. This mismatch is the bug. There are two alternative solutions: 1. ensure the gcc versions used to compile the available kernels are also available. 2. ensure the kernels are always compiled with the latest available gcc. The former is probably a better solution as the latter may cause unnecessary kernel recompiles as the gcc versions change. The former may require multiple installed versions of gcc, one for each installed kernel version, which would need a method of picking the gcc version which matches the kernel. It would also be useful if one of the meta-packages ensured that the installed gcc matches the installed kernel's compiler. ``` $ uname -a Linux xx 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ``` ... I'm sorry, but the DKMS make.log with the error has been deleted by a later re-run attempt for the install. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gcc 4:7.4.0-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Tue Mar 10 22:40:51 2020 InstallationDate: Installed on
[Kernel-packages] [Bug 1867026] [NEW] wifi adapter is missing - wrong iwlwifi firmware
Public bug reported: I managed fo fix the problem, so I'm going to state here my solution first: === The Solution === # sudo rmmod iwlmvm sudo rmmod iwlwifi sudo cp /lib/firmware/iwlwifi-QuZ-a0-jf-b0-48.ucode /lib/firmware/iwlwifi-Qu-b0-jf-b0-48.ucode sudo modprobe iwlwifi # === Bug Report === === 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:KDE neon User Edition 5.18 Release:18.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy linux-firmware linux-firmware: Installed: 1.173.16 Candidate: 1.173.16 Version table: *** 1.173.16 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.12 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu bionic/main i386 Packages 3) What you expected to happen Keep having wifi without any surprise 4) What happened instead surprise surprise: no wifi === === The Problem === [1] After upgrading packages and reboot, I lost wifi. Actually, `/var/log/kern.log` says: # Mar 11 12:40:32 tc-wildebeest kernel: [0.00] microcode: microcode updated early to revision 0xca, date = 2019-10-03 Mar 11 12:40:32 tc-wildebeest kernel: [0.00] Linux version 5.3.0-40-generic (buildd@lcy01-amd64-024) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 (Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18) # [2] I believe the problem is related to an error on firmware (or choosing the wrong firmware) On `/var/log/kern` # Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997654] iwlwifi :00:14.3: Collecting data: trigger 15 fired. Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997773] iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 11 12:40:32 tc-wildebeest kernel: [ 11.99] iwlwifi :00:14.3: Status: 0x, count: -1355353588 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997780] iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997782] iwlwifi :00:14.3: 0xE439F61B | ADVANCED_SYSASSERT Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997784] iwlwifi :00:14.3: 0x46F73672 | trm_hw_status0 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997786] iwlwifi :00:14.3: 0x28C2A402 | trm_hw_status1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997787] iwlwifi :00:14.3: 0x9DAEAFF4 | branchlink2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997789] iwlwifi :00:14.3: 0x3AF3947B | interruptlink1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997790] iwlwifi :00:14.3: 0x423D8A25 | interruptlink2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997792] iwlwifi :00:14.3: 0x2030A0C5 | data1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997793] iwlwifi :00:14.3: 0xC74F825F | data2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997795] iwlwifi :00:14.3: 0x755A2DAF | data3 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997796] iwlwifi :00:14.3: 0x8C8FD806 | beacon time Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997798] iwlwifi :00:14.3: 0x234581B8 | tsf low Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997799] iwlwifi :00:14.3: 0x9767D27F | tsf hi Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997801] iwlwifi :00:14.3: 0xDEFDFBC2 | time gp1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997803] iwlwifi :00:14.3: 0x0808199E | time gp2 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997804] iwlwifi :00:14.3: 0x80539983 | uCode revision type Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997806] iwlwifi :00:14.3: 0xCE7E6303 | uCode version major Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997807] iwlwifi :00:14.3: 0x79CDBF29 | uCode version minor Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997809] iwlwifi :00:14.3: 0x1024014F | hw version Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997810] iwlwifi :00:14.3: 0x08C6D4AE | board version Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997812] iwlwifi :00:14.3: 0xC19133C0 | hcmd Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997813] iwlwifi :00:14.3: 0xDAB3AE6C | isr0 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997815] iwlwifi :00:14.3: 0x4FCB7BEE | isr1 Mar 11 12:40:32 tc-wildebeest kernel: [ 11.997817]
[Kernel-packages] [Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 03. March 2020 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - bionic/linux-aws-fips: bug 1865419, bug 1864732 + bionic/linux-aws-fips: bug 1865419 bionic/linux-aws/aws-kernel: bug 1865268 xenial/linux-aws-hwe: bug 1865421 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1865269 Title: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 03. March 2020 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1865419 bionic/linux-aws/aws-kernel: bug 1865268 xenial/linux-aws-hwe: bug 1865421 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865201] Re: bionic/linux-ibm-gt: 4.15.0-1051.57 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Testing phase-changed: Tuesday, 03. March 2020 22:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865201 Title: bionic/linux-ibm-gt: 4.15.0-1051.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Testing phase-changed: Tuesday, 03. March 2020 22:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865201] Re: bionic/linux-ibm-gt: 4.15.0-1051.57 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865201 Title: bionic/linux-ibm-gt: 4.15.0-1051.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Testing phase-changed: Tuesday, 03. March 2020 22:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865269 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Promote to Proposed - phase-changed: Tuesday, 10. March 2020 14:21 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 11. March 2020 15:44 UTC reason: - build-packages-signing: Pending -- building in Signing signed:queued - promote-to-proposed: Stalled -- packages copying to Signing + promote-signing-to-proposed: Pending -- ready for review replaces: bug 1864732 variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865269 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Wednesday, 11. March 2020 15:44 UTC reason: promote-signing-to-proposed: Pending -- ready for review - replaces: bug 1864732 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865419 Title: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865269 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Wednesday, 11. March 2020 15:44 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864732] Re: bionic/linux-aws-fips: 4.15.0-2011.11 -proposed tracker
*** This bug is a duplicate of bug 1865419 *** https://bugs.launchpad.net/bugs/1865419 ** This bug has been marked a duplicate of bug 1865419 bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864732 Title: bionic/linux-aws-fips: 4.15.0-2011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865269 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Testing phase-changed: Friday, 28. February 2020 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863317] Re: bionic/linux-aws-fips: 4.15.0-2010.10 -proposed tracker
*** This bug is a duplicate of bug 1865419 *** https://bugs.launchpad.net/bugs/1865419 ** This bug is no longer a duplicate of bug 1864732 bionic/linux-aws-fips: 4.15.0-2011.11 -proposed tracker ** This bug has been marked a duplicate of bug 1865419 bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863317 Title: bionic/linux-aws-fips: 4.15.0-2010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1864734 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Testing phase-changed: Friday, 21. February 2020 17:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863317/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865203] Re: bionic/linux-fips: 4.15.0-1025.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Wednesday, 11. March 2020 11:41 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 11. March 2020 15:42 UTC reason: - build-packages-signing: Ongoing -- building in Signing - signed:building - promote-to-proposed: Stalled -- packages copying to Signing + promote-signing-to-proposed: Stalled -- another kernel is currently + pending in Proposed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865203 Title: bionic/linux-fips: 4.15.0-1025.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Wednesday, 11. March 2020 15:42 UTC reason: promote-signing-to-proposed: Stalled -- another kernel is currently pending in Proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859743] Re: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform
** Description changed: + [Impact] + No TPM eventlog information in sysfs + + [Fix] + d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform + + [Test] + ls -l /sys/kernel/security/tpm0/binary_bios_measurements + + [Regression Potential] + Only affect arm64 system with TPM. Lowest risk for other platform. + [Bug Description] this patch gets tpm eventlog information such as device boot status,event guid and so on, which will be from bios stage. it use "efi_retrieve_tpm2_eventlog" functions to get it for ARM64 platorm. [Steps to Reproduce] 1) ls -l /sys/kernel/security/tpm0/binary_bios_measurements 2) 3) [Actual Results] '/sys/kernel/security/tpm0/binary_bios_measurements' no such file or directory [Expected Results] ok [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] - - d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 - platform + d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859743 Title: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.10 series: In Progress Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] No TPM eventlog information in sysfs [Fix] d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform [Test] ls -l /sys/kernel/security/tpm0/binary_bios_measurements [Regression Potential] Only affect arm64 system with TPM. Lowest risk for other platform. [Bug Description] this patch gets tpm eventlog information such as device boot status,event guid and so on, which will be from bios stage. it use "efi_retrieve_tpm2_eventlog" functions to get it for ARM64 platorm. [Steps to Reproduce] 1) ls -l /sys/kernel/security/tpm0/binary_bios_measurements 2) 3) [Actual Results] '/sys/kernel/security/tpm0/binary_bios_measurements' no such file or directory [Expected Results] ok [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853964] Re: [hns-1126]net: hns3: make hclge_service use delayed workqueue
** Description changed:
+ [Impact]
+ System crashes when setting irq affinity and turning on/off on the interfaces
+
+ [Fix]
+ net: hns3: make hclge_service use delayed workqueue
+
+ [Test]
+ Writing smp_affinity_list and turning on/off in loop
+
+ [Regression Potential]
+ This patch only for hns3. Lowest risk for other platform/driver
+
"[Bug Description]
Currently, up/down port process may concurrently operate
timer(del_timer_sync/add_timer_on) with setting IRQ affinity, and cause system
breaking down.
[Steps to Reproduce]
set misc irp affinity of PF during up/down port by follow script:
while((1))
do
for i in {0..31}; do echo $i > /proc/irq/678/smp_affinity_list; done
done
while((1))
do
ifconfig eth4 down
ifconfig eth4 up
done
-
[Actual Results]
System break down.
kernel call trace
[Expected Results]
System run normally.
[Reproducibility]
Inevitably
[Additional information]
Hardware: D06
Firmware: NA
Kernel: NA
[Resolution]
This patch uses delayed work instead of using timers to trigger the
hclge_serive."
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853964
Title:
[hns-1126]net: hns3: make hclge_service use delayed workqueue
Status in kunpeng920:
In Progress
Status in kunpeng920 ubuntu-18.04 series:
Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
Fix Committed
Status in kunpeng920 ubuntu-19.10 series:
In Progress
Status in kunpeng920 ubuntu-20.04 series:
Fix Committed
Status in kunpeng920 upstream-kernel series:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
In Progress
Bug description:
[Impact]
System crashes when setting irq affinity and turning on/off on the interfaces
[Fix]
net: hns3: make hclge_service use delayed workqueue
[Test]
Writing smp_affinity_list and turning on/off in loop
[Regression Potential]
This patch only for hns3. Lowest risk for other platform/driver
"[Bug Description]
Currently, up/down port process may concurrently operate
timer(del_timer_sync/add_timer_on) with setting IRQ affinity, and cause system
breaking down.
[Steps to Reproduce]
set misc irp affinity of PF during up/down port by follow script:
while((1))
do
for i in {0..31}; do echo $i > /proc/irq/678/smp_affinity_list; done
done
while((1))
do
ifconfig eth4 down
ifconfig eth4 up
done
[Actual Results]
System break down.
kernel call trace
[Expected Results]
System run normally.
[Reproducibility]
Inevitably
[Additional information]
Hardware: D06
Firmware: NA
Kernel: NA
[Resolution]
This patch uses delayed work instead of using timers to trigger the
hclge_serive."
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1853964/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859744] Re: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error
** Description changed: + [Impact] + Sometimes, TPM fails because SPI data error + + [Fix] + bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error + + [Test] + Reboot system few times and no TPM error message + + [Regression Potential] + Only on SPI function. Already tested on focal kernel + [Bug Description] Because of out-of-order execution about some CPU architecture, In this debug stage we find Completing spi interrupt enable -> prodrucing TXEI interrupt -> running "interrupt_transfer" function will prior to set "dw->rx and dws->rx_end" data, so this patch add memory barrier to enable dw->rx and dw->rx_end to be visible and solve to send SPI data error. eg: it will fix to this following low possibility error in testing environment which using SPI control to connect TPM Modules kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Steps to Reproduce] 1) enable ima and tpm 2)reboot this system 3) [Actual Results] kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Expected Results] ok [Reproducibility] low probabilities [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859744 Title: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.10 series: In Progress Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Sometimes, TPM fails because SPI data error [Fix] bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error [Test] Reboot system few times and no TPM error message [Regression Potential] Only on SPI function. Already tested on focal kernel [Bug Description] Because of out-of-order execution about some CPU architecture, In this debug stage we find Completing spi interrupt enable -> prodrucing TXEI interrupt -> running "interrupt_transfer" function will prior to set "dw->rx and dws->rx_end" data, so this patch add memory barrier to enable dw->rx and dw->rx_end to be visible and solve to send SPI data error. eg: it will fix to this following low possibility error in testing environment which using SPI control to connect TPM Modules kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Steps to Reproduce] 1) enable ima and tpm 2)reboot this system 3) [Actual Results] kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Expected Results] ok [Reproducibility] low probabilities [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865198] Re: xenial/linux-azure: 4.15.0-1074.79 -proposed tracker
SRU Bugs: https://bugs.launchpad.net/ubuntu-kernel-tests/+bugs?field.tag=sru-20200217+azure_combinator=ALL ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865198 Title: xenial/linux-azure: 4.15.0-1074.79 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 03. March 2020 00:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1865197 xenial/linux-azure/azure-kernel: bug 1865196 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865198] Re: xenial/linux-azure: 4.15.0-1074.79 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 03. March 2020 00:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1865197 xenial/linux-azure/azure-kernel: bug 1865196 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865198 Title: xenial/linux-azure: 4.15.0-1074.79 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 03. March 2020 00:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1865197 xenial/linux-azure/azure-kernel: bug 1865196 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853993] Re: [hns-1126]scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device
** Description changed: + [Impact] + Disks will be lost on SAS interface reset + + [Fix] + scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device + + [Test] + Resetting SAS interfaces shall not lose any disks + + [Regression Potential] + Patch only for hisi_sas. Lowest risk for other platform/driver. + "[Steps to Reproduce] 1. Close all the PHYS; - 2. Inject error; - 3. Open one PHY; + 2. Inject error; + 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853993 Title: [hns-1126]scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Won't Fix Status in kunpeng920 ubuntu-19.10 series: In Progress Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: Fix Released Bug description: [Impact] Disks will be lost on SAS interface reset [Fix] scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device [Test] Resetting SAS interfaces shall not lose any disks [Regression Potential] Patch only for hisi_sas. Lowest risk for other platform/driver. "[Steps to Reproduce] 1. Close all the PHYS; 2. Inject error; 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Somehow you've got two modules to be loaded simultaneously:
elan_i2c 40960 0
[...]
synaptics_i2c 20480 0
dmesg mentions ELAN0632:
[9.706424] i2c_hid i2c-ELAN0632:00: i2c-ELAN0632:00 supply vdd not found,
using dummy regulator
[9.706437] i2c_hid i2c-ELAN0632:00: i2c-ELAN0632:00 supply vddl not found,
using dummy regulator
but I didn't find SYNA2B60
It is not relevant to the bug, but your laptop also has one more ELAN device on
USB bus (fingerprint sensor)
[1.492202] usb 1-5: new full-speed USB device number 2 using xhci_hcd
[1.644710] usb 1-5: New USB device found, idVendor=04f3, idProduct=0c4b,
bcdDevice= 1.74
[1.644711] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[1.644712] usb 1-5: Product: ELAN:Fingerprint
[1.644713] usb 1-5: Manufacturer: ELAN
So would you please share your logs for:
dmidecode
cat /sys/bus/acpi/devices/{ELAN,SYNA,CRQ}*/modalias
cat /sys/bus/acpi/devices/{ELAN,SYNA,CRQ}*/status
cat /sys/bus/i2c/devices/*/name
ls /sys/bus/i2c/devices/*
Could you also check VID/PID pair for your touchpad in Windows to check
whether it is supported by the kernel you are using?
You may want to build latest stable or even mainline kernel for test
purposes...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853277
Title:
Lenovo ThinkBook 14-IML Touchpad not showing up in
/proc/bus/input/devices
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is happening on a ThinkBook 14 IML 20RV.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1848 F pulseaudio
CasperVersion: 1.427
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 20 11:10:52 2019
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20RV
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.3.0-18-generic N/A
linux-backports-modules-5.3.0-18-generic N/A
linux-firmware1.183
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/10/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: CJCN21WW
dmi.board.name: LVA/LVAB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.modalias:
dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr:
dmi.product.family: ThinkBook 14-IML
dmi.product.name: 20RV
dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML
dmi.product.version: Lenovo ThinkBook 14-IML
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hi pavelcheto Could you remove i8042.nopnp in cmdline and try again? Please upload dmesg 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865203] Re: bionic/linux-fips: 4.15.0-1025.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Wednesday, 11. March 2020 11:41 UTC reason: - promote-to-proposed: Stalled -- review in progress + build-packages-signing: Ongoing -- building in Signing + signed:building + promote-to-proposed: Stalled -- packages copying to Signing variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865203 Title: bionic/linux-fips: 4.15.0-1025.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Wednesday, 11. March 2020 11:41 UTC reason: build-packages-signing: Ongoing -- building in Signing signed:building promote-to-proposed: Stalled -- packages copying to Signing variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865269 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Promote to Proposed phase-changed: Tuesday, 10. March 2020 14:21 UTC reason: - promote-to-proposed: Stalled -- review in progress + build-packages-signing: Pending -- building in Signing signed:queued + promote-to-proposed: Stalled -- packages copying to Signing replaces: bug 1864732 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865419 Title: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865269 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Promote to Proposed phase-changed: Tuesday, 10. March 2020 14:21 UTC reason: build-packages-signing: Pending -- building in Signing signed:queued promote-to-proposed: Stalled -- packages copying to Signing replaces: bug 1864732 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Monday, 09. March 2020 14:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1865200 Title: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Monday, 09. March 2020 14:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic
*** This bug is a duplicate of bug 1864992 *** https://bugs.launchpad.net/bugs/1864992 Im marking this bug as a duplicate of: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992 ** This bug has been marked a duplicate of bug 1864992 depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866012 Title: depmod ERROR during Setting up linux-modules-5.4.0-17-generic Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Deploy Focal on a KVM ndoe, enable proposed 2. Run sudo apt dist-upgrade The console will be flushed with: Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ... Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ... depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' Setting up apt-utils (1.9.12) ... Setting up libselinux1-dev:amd64 (3.0-1build2) ... Setting up libglib2.0-0:amd64 (2.64.0-1) ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 4 08:29 seq crw-rw 1 root audio 116, 33 Mar 4 08:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 4 09:06:42 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-5.4 StagingDrivers: exfat UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic
*** This bug is a duplicate of bug 1864992 *** https://bugs.launchpad.net/bugs/1864992 https://bugs.launchpad.net/curtin/+bug/1864992/comments/34 https://bugs.launchpad.net/curtin/+bug/1864992/comments/35 https://bugs.launchpad.net/curtin/+bug/1864992/comments/36 Issue is in verbosity level of kmod. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866012 Title: depmod ERROR during Setting up linux-modules-5.4.0-17-generic Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Deploy Focal on a KVM ndoe, enable proposed 2. Run sudo apt dist-upgrade The console will be flushed with: Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ... Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ... depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' Setting up apt-utils (1.9.12) ... Setting up libselinux1-dev:amd64 (3.0-1build2) ... Setting up libglib2.0-0:amd64 (2.64.0-1) ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 4 08:29 seq crw-rw 1 root audio 116, 33 Mar 4 08:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 4 09:06:42 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-5.4 StagingDrivers: exfat UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
Hi again Juerg and all, I want to mention that upstream Linux developers actually *do* care about ABI stability. For example, one of the commits broke ABI but it was quickly reverted and then fixed in a way that does not change the ABI: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41ddb7e1f79693d9 Please reconsider providing a public -dev package again. For applications that want to know information about CPUs, the only alternative is using libcpufreq. However that library is abandoned both upstream and in Debian, and recently I have seen it returning junk data. The affected applications are: $ reverse-depends -b libcpufreq-dev -r focal Reverse-Build-Depends * cpufreqd * gkrellm2-cpufreq * gnome-applets * mate-applets * xfce4-cpufreq-plugin -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1215411 Title: libcpupower.so is not installed from linux-tools Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: Invalid Status in linux source package in Eoan: In Progress Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
