[Kernel-packages] [Bug 1860144] Re: linux 5.4.0-11 fails to boot on arm64
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860144 Title: linux 5.4.0-11 fails to boot on arm64 Status in linux package in Ubuntu: Expired Bug description: Series: Focal Kernel: 5.4.0-11.14 Problem: Kernel Fails to boot on arm64 hardware. During preliminary the following failure was observed in a VM after the -proposed kernel was installed from ppa:canonical-kernel- team/proposed autopkgtest login: [ 44.923688] kernel BUG at arch/arm64/kernel/traps.c:406! [ 44.925735] Internal error: Oops - BUG: 0 [#1] SMP [ 44.927059] Modules linked in: iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_ce ofpart redboot cmdlinepart cfi_cmdset_0001 cfi_probe cfi_util gen_probe physmap qemu_fw_cfg uio_pdrv_genirq uio map_funcs chipreg mtd sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress raid6_pq libcrc32c virtio_net net_failover virtio_blk failover [ 44.943611] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.5.0-4-snapdragon #5-Ubuntu [ 44.948138] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 44.951579] pstate: 0045 (nzcv daif +PAN -UAO) [ 44.953905] pc : do_undefinstr+0x60/0x68 [ 44.955836] lr : do_undefinstr+0x34/0x68 [ 44.957695] sp : 800010013550 [ 44.959644] x29: 800010013550 x28: 0001fd173c00 [ 44.962107] x27: x26: c642935b [ 44.964652] x25: x24: 80001001379c [ 44.966750] x23: 8045 x22: 800010cdc2f8 [ 44.968930] x21: 41573000 x20: [ 44.970885] x19: 800010013580 x18: 1400 [ 44.973300] x17: 1c00 x16: 1000 [ 44.975899] x15: 0c00 x14: [ 44.978497] x13: 01d8 x12: 0001ec755428 [ 44.981178] x11: 503e2aa6 x10: [ 44.983809] x9 : 80001036b4d0 x8 : [ 44.986435] x7 : 0001fd174128 x6 : 800010013548 [ 44.988607] x5 : x4 : 800011f5e100 [ 44.990548] x3 : 800011cf5f10 x2 : db67b15ed7685100 [ 44.992687] x1 : x0 : 8045 [ 44.994456] Call trace: [ 44.995286] do_undefinstr+0x60/0x68 [ 44.996622] el1_sync_handler+0x8c/0xd8 [ 44.998434] el1_sync+0xb4/0x180 [ 44.999604] e843419@0b9d_0001182e_66f8+0x0/0xff8 [ 45.001407] tcp_ack+0x428/0x940 [ 45.002578] tcp_rcv_established+0x174/0x6b0 [ 45.003984] tcp_v4_do_rcv+0x168/0x250 [ 45.005235] tcp_v4_rcv+0xb9c/0xd08 [ 45.006437] ip_protocol_deliver_rcu+0x44/0x200 [ 45.008109] ip_local_deliver_finish+0x54/0x68 [ 45.009492] ip_local_deliver+0x104/0x110 [ 45.010596] ip_sublist_rcv_finish+0x48/0x68 [ 45.011732] ip_sublist_rcv+0x174/0x1e8 [ 45.012707] ip_list_rcv+0x108/0x168 [ 45.013561] __netif_receive_skb_list_core+0x18c/0x220 [ 45.014832] netif_receive_skb_list_internal+0x194/0x2a0 [ 45.016207] gro_normal_list.part.0+0x24/0x40 [ 45.017548] napi_gro_receive+0x1bc/0x1d8 [ 45.018773] receive_buf+0x1d4/0x498 [virtio_net] [ 45.019967] virtnet_poll+0x168/0x6f8 [virtio_net] [ 45.021161] net_rx_action+0x178/0x460 [ 45.022087] __do_softirq+0x130/0x32c [ 45.023019] irq_exit+0xa0/0xc8 [ 45.023796] __handle_domain_irq+0x6c/0xc0 [ 45.024805] gic_handle_irq+0x58/0xa8 [ 45.025692] el1_irq+0x104/0x1c0 [ 45.026488] arch_cpu_idle+0x38/0x1c8 [ 45.027412] default_idle_call+0x20/0x40 [ 45.028361] do_idle+0x20c/0x2b0 [ 45.029184] cpu_startup_entry+0x28/0x68 [ 45.030146] secondary_start_kernel+0x154/0x1e0 [ 45.031275] Code: 97b6 f9400bf3 a8c27bfd d65f03c0 (d421) [ 45.032751] ---[ end trace b0983b157b7a3c23 ]--- [ 45.033868] Kernel panic - not syncing: Fatal exception in interrupt [ 45.035609] SMP: stopping secondary CPUs [ 45.036876] Kernel Offset: disabled [ 45.037966] CPU features: 0x0,20802000 [ 45.039153] Memory Limit: none [ 45.039952] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- Focal was deployed on a Hisilicon D05, After installing the kernel on bare metal there were no console logs after the EFI Boot Stub Booting local disk... [ grub.cfg-02:0f:b7:04 527B 100% 2.25B/s ] EFI stub: Booting Linux Kernel...[ grubaa64.efi 1.70MiB 100% 7.45KiB/s ] EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... To manage notifications about this bug go t
[Kernel-packages] [Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic
Upgrade to 5.4.0-18-generic fixed this for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858844 Title: [Dell XPS 15 9575] Screen brightness stopped working with linux- image-5.4.0-9-generic Status in linux package in Ubuntu: Confirmed Bug description: I upgraded to Focal Fossa 3 days ago and nothing broke. At the time, it was still using linux 5.3 (linux-image-5.3.0-24-generic). Today, it updated to linux 5.4 (linux-image-5.4.0-9-generic) and after rebooting, the screen brightness does not work anymore - neither from keyboard keys nor from the slider in the gnome-shell panel. It works again when rebooting into the previous linux- image-5.3.0-24-generic kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 1892 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 20:23:31 2020 InstallationDate: Installed on 2018-09-13 (481 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-04 (3 days ago) dmi.bios.date: 07/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Hi Kai Heng Feng, Sorry for delaying this for long. I already check and it already enable but in log file still not. I think there is something not meet with the configuration. Please see log file. Thanks and regards, ** Attachment added: "prevboot4.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860754/+attachment/5339588/+files/prevboot4.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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU 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.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts
** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861446 Title: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Bug description: Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The issue was filed against linux-signed-5.4 (Ubuntu) rather than linux (Ubuntu), and none of the logs usually included with kernel bug reports were included. After the bug was changed from linux-signed-5.4 to linux, I was prompted to run apport-collect by the kernel team's triagebot and that worked successfully: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity My guess is that apport needs to be updated to understand a change in kernel packaging. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 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 ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashReports: 640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash 600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash 640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash Date: Thu Jan 30 18:44:47 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
@Akkana, I can't find any problems from your dmesg. Since -42 has regression, let us test -43 kernel, you could enable proposed then run apt-get update, you will find the -43 kernel. And please install the alsa-lib of #66 I mentioned. How to enable proposed, please refer to: https://bugs.launchpad.net/ubuntu/+source/alsa- lib/+bug/1859754/comments/49 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864061 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. In the -41 kernel, we introduced a patch from stable kernel, that make the sof driver crash, and there is a fix patch in the 5.6-rc1, and this fix patch is already in the stable and is merged to focal kernel, now we backport this patch to Eoan kernel if -42 doesn't introduce this fix patch from stable. The patch introduced the crash: commit 063821115e02229d5fd3de31bad270d5e30aeb41 Author: Dragos Tarcatu Date: Mon Dec 9 18:39:38 2019 -0600 ASoC: topology: Check return value for snd_soc_add_dai_link() BugLink: https://bugs.launchpad.net/bugs/1861929 [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] snd_soc_add_dai_link() might fail. This situation occurs for instance in a very specific use case where a PCM device and a Back End DAI link are given identical names in the topology. When this happens, soc_new_pcm_runtime() fails and then snd_soc_add_dai_link() returns -ENOMEM when called from soc_tplg_fe_link_create(). Because of that, the link will not get added into the card list, so any attempt to remove it later ends up in a panic. Fix that by checking the return status and free the memory in case of an error. Reviewed-by: Ranjani Sridharan Signed-off-by: Dragos Tarcatu Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously [Impact] During the boot, the sof driver crash because the hdmi_pcm_list is not initialized before it is used. [Fix] This bug is fixed in the mainline kernel v5.6-rc1, now backport this patch to ubuntu kernel [Test Case] Boot the -41 kernel with this patch added. blacklist the snd_soc_skl the kernel can boot successfully, and sof driver worked well [Regression Risk] Low, the patches are backported from upstream kernel, and I tested this patch on Lenovo and Dell dmic machines. Focal kernel already has this patch and works well. Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0
[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Eddie, "When I plug in a headset with a mic in the 3.5mm port, it still seems to use the internal mic instead of that of the headset." What happens if you manually select usb headset from gnome-sound- setting->input devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868134] Re: Headphones Audio Out Not Delivering Sound
I loathe messing with Python since it appears to govern quite a bit of functionality in LM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868134 Title: Headphones Audio Out Not Delivering Sound Status in linux package in Ubuntu: Incomplete Bug description: DELL M5510 ~ $ cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xddc28000 irq 128 4.15.0-91 Exhibits no sound via headphones 4.15.0-88 No issue with sound via headphones *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** Problem in linux-image-4.15.0-88-generic The problem cannot be reported: This is not an official Linux package. Please remove any third party package and try again. Press any key to continue... ^C ~ $ cat /proc/version_signature > version.log ~ $ sudo lspci -vnvn > lspci-vnvn.log [sudo] password: ~ $ Not sure why the above commands are not creating the required info. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868134] Re: Headphones Audio Out Not Delivering Sound
~ $ apport-collect 1868134 ERROR: The python3-launchpadlib package is not installed. This functionality is not available. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868134 Title: Headphones Audio Out Not Delivering Sound Status in linux package in Ubuntu: Incomplete Bug description: DELL M5510 ~ $ cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xddc28000 irq 128 4.15.0-91 Exhibits no sound via headphones 4.15.0-88 No issue with sound via headphones *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** Problem in linux-image-4.15.0-88-generic The problem cannot be reported: This is not an official Linux package. Please remove any third party package and try again. Press any key to continue... ^C ~ $ cat /proc/version_signature > version.log ~ $ sudo lspci -vnvn > lspci-vnvn.log [sudo] password: ~ $ Not sure why the above commands are not creating the required info. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863951] Re: [linux-azure] Missing user mode io driver - uio_pci_generic
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863951 Title: [linux-azure] Missing user mode io driver - uio_pci_generic Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Xenial: Fix Committed Status in linux-azure source package in Bionic: Fix Committed Status in linux-azure source package in Eoan: Fix Committed Status in linux-azure source package in Focal: Fix Committed Bug description: After creating a Lv2 VM (OS - ubuntu 18.04) it was found that uio_pci_generic is missing. It is needed to attach SPDK to nvme disk. The kernel build config file that Canonical provides in Ubuntu 18.04 images shows CONFIG_UIO_PCI_GENERIC=m, indicating that the module was built. However, the module is not included in the image. Is there a reason why the uio_pci_generic module is not included in the Azure Marketplace image? If not, can we get it added back in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1863951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868217] Re: Make Dell WD19 dock more reliable after suspend
** Changed in: linux (Ubuntu Focal) Status: Incomplete => 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/1868217 Title: Make Dell WD19 dock more reliable after suspend Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: Incomplete Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When Dell WD19 dock connects multiple USB3 storage devices, the USB Hub used internally may stop working after suspend. [Fix] Disable LPM on the Realtek USB Hub, and let xHCI controller make sure the link state transition is completed. [Test] After applying the patches, the Dell WD19 works reliably after thousand times for suspend/resume cycle. [Regression Potential] Low. This replaces the currently "msleep" way with more robust mechanism. I also test other systems and nothing breaks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. [FIXES] These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement All are clean cherry picks into the 5.4 branch and can be pulled from my branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1864484-smartpqi-to-1.2.10-025 [TESTING] modinfo for smartpqi should show: version:1.2.10-025 description:Driver for Microsemi Smart Family Controller version 1.2.10-025 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836030] Re: enable realtek ethernet device ASPM function
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836030 Title: enable realtek ethernet device ASPM function Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Bug description: = SRU for 5.4 Focal kernel === [Impact] The PC state stays at PC3 if r8169 driver doesn't enable ASPM. [Fix] Applied same series of patches from v5.5-rc1 and disable ASPM L1.1 only, instead of disable ASPM completely. [Test] Verified on machines with realtek Ethernet device, the Ethernet works well after S3 test 30 times and the system can enter PC10. [Regression Potential] Low, from realtek engineer, r8169 driver supports ASPM L0s and L1, and we only disable ASPM L1.1 which is pretty safe and should be disabled by default. == SRU for 5.0 OEM OSP1 kernel = [Impact] The PC state stays at PC3 if realtek ethernet doesn't enable ASPM. [Fix] Discussed with upstream and they would like to use sysfs to toggle the ASPM link states, but the patches didn't get merged yet, so we merger them as SAUCE patches. [Test] Verified on machines with realtek ethernet device, the ethernet works well and the system can enter PC10. [Regression Potential] High. From upstream maintainer, enable realtek ethernet ASPM may lead to some serious issue, so regression is expected. Those regression should come from old realtek chips, we'll make sure all new platforms with realtek NIC have no any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867790] Re: update-version-dkms doesn't add a BugLink
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1867790
Title:
update-version-dkms doesn't add a BugLink
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Status in linux source package in Focal:
Fix Committed
Bug description:
== Impact ==
When there are updates on the dkms versions used for a linux build,
'update-version-dkms' saves the new version(s) in 'debian/dkms-versions' and
commits it. The commit doesn't have any BugLink, so it gets added to the debian
changelog under "* Miscellaneous Ubuntu changes".
== Fix ==
Change 'update-version-dkms' to add a BugLink to
https://bugs.launchpad.net/bugs/1786013 ("Packaging resync"), which is the bug
report being used for all the other automated commits.
== Test Case ==
In one of the main kernels, run 'update-version-dkms' and make sure it adds a
valid BugLink.
== Regression Potential ==
Low. This only changes how the automated commits are generated and later
added to the changelog.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867790/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864442] Re: dmaengine: hisilicon: Add Kunpeng DMA engine support
** Changed in: kunpeng920/ubuntu-20.04 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/1864442 Title: dmaengine: hisilicon: Add Kunpeng DMA engine support Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] This patch adds a driver for HiSilicon Kunpeng DMA engine. This DMA engine which is an PCIe iEP offers 30 channels, each channel has a send queue, a complete queue and an interrupt to help to do tasks. This DMA engine can do memory copy between memory blocks or between memory and device buffer [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] e9f08b65250d dmaengine: hisilicon: Add Kunpeng DMA engine support https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/dma?h=v5.6-rc1&id=e9f08b65250d73ab70e79e194813f52b8d306784 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1864442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780590] Re: Add support for Realtek 8723DE wireless adapter
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1780590 Title: Add support for Realtek 8723DE wireless adapter Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux-firmware source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] There's no in-kernel support for Realtek 8723DE, so users need to use out-of-tree DKMS which is not from Ubuntu archive. This has security implication and should be avoided. Also this provides pretty bad user experience. [Fix] Add support to Realtek 8723DE. All commits are cherry-picked from Realtek maintained repo: https://github.com/rtlwifi-linux/rtw88_8723de [Test] With the patch series applied, 8723DE can scan and connect to APs succesfully. Also did some S3 smoke test, it continues to work. [Regression Potential] Low. The device in question was never supported, and if there's any regression, we can count on Realtek Wireless team, thy are now pretty responsive on upstream mailing list. === Original Bug Report === recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. Everything in the installation was fine until the moment to start session. The problem is that the wireless network card does not detect me and when entering the configuration I simply get an error message saying that no wireless adapter was found. I have already followed all the tutorials I found on the web. and update the driver of a github repository, and install how much program they told me to install and I still can not connect via wifi. I just do not know what to do. I have a laptop hp 14-bs004 came with windows 10 installed. The information on the network card is as follows: Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: d723] Subsystem: Hewlett-Packard Company Device [103c: 8319] Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort- SERR- Kernel modules: wl already install the most recent kernel, already intale driver driver realtek rtl8723be according to the instructions of the git repository. and nothing has worked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 22:57:40 2018 InstallationDate: Installed on 2018-07-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1780590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835531] Re: [20.04 FEAT] Base KVM setup for secure guests - kernel part
Patches applied for focal. ** Changed in: linux (Ubuntu) Status: Triaged => 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/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Committed Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867656] Re: Remove linux-firmware dependency from kernel meta packages for s390x
** Changed in: linux-meta (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1867656 Title: Remove linux-firmware dependency from kernel meta packages for s390x Status in Ubuntu on IBM z Systems: In Progress Status in linux-meta package in Ubuntu: Fix Committed Bug description: As far as we understand all firmware upgrades (and the firmware itself) is coming from the HMC on case of IBM Z and LinuxONE. This not only incl. the CEC code, but also all the firmware for the different cards and adapters. If this is the case (and will be in future), it would make sense for us to get rid of the linux-firmware package for s390x - this would make things leaner, reduce size and eventually increase (installation) performance ... So please IBM can you confirm that all firmware updates (MCLs) are always done via the HMC and that is therefore the linux-firmware package is obsolete on s390x? Thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867753] Re: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal
Config changes applied for focal. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Fix Committed Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867534] Re: Wifi requires interruption before timing out (and immediate reconnect attempt succeeds)
UPDATE: This wifi behavior happens with all the Ubuntu desktop distros. HOWEVER: I just installed 20.04 Ubuntu Server daily-image (20200320). It did NOT have this behavior. As I began the text-based install, I wondered how I would interrupt the connection in order to make it work. But, it just worked. I haven't seen any desktop do that. They all timeout. They all require some clicking on the access point to interrupt that timeout, causing it to connect. So, the problem seems to be specific to desktop distros. (If it were a driver problem, I think it would have happened with the server distro too.). -- 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/1867534 Title: Wifi requires interruption before timing out (and immediate reconnect attempt succeeds) Status in linux-5.4 package in Ubuntu: New Bug description: ISO testing 20.04 Lubuntu daily (20200315). From the Live desktop, I click my nm-tray access point, supply the password. nm-tray will timeout. Trying again will timeout. What works is clicking the same access point a couple times before it times out. This causes an immediate failure and successful connection (two balloon msgs). This problem is not specific to Lubuntu. It happens with Kubuntu, Budgie, Mate, Xubuntu. The common theme is: it appears to be out of sync in some manner. The wifi connection needs to be interrupted before timing out. Then an immediate attempt (within 2-3 seconds? I haven't tested how long it can wait) succeeds. This problem also happens after install and reboot. For example, with yesterday's daily image (20200314), I had to reboot Lubuntu twice after install before the wifi worked. (I haven't reached that point yet today. I'm creating this bug report from the Live desktop. I will update with more info about post-install.). Note: I don't know if this is acceptable wifi behavior. Good enough? I figured I should report it and let someone decide. It seems to be specific to this laptop (Lenovo Thinkpad E440 20C5) or it's Intel 7260 wifi card. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lubuntu1857 F pulseaudio /dev/snd/controlC0: lubuntu1857 F pulseaudio CasperVersion: 1.441 Date: Sun Mar 15 17:17:43 2020 LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20C5004YUS ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C5004YUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C5004YUS:pvrThinkPadEdgeE440:rvnLENOVO:rn20C5004YUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E440 dmi.product.name: 20C5004YUS dmi.product.sku: LENOVO_MT_20C5_BU_Think_FM_ThinkPad Edge E440 dmi.product.version: ThinkPad Edge E440 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1867534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866484] Re: focal/linux-azure: 5.4.0-1006.6 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
--
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/1866484
Title:
focal/linux-azure: 5.4.0-1006.6 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
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-release series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
Invalid
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Focal:
Fix Released
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: 1866488
packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
phase: Complete
phase-changed: Friday, 20. March 2020 21:56 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866484/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -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: 1860119
packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
phase: Complete
phase-changed: Tuesday, 04. February 2020 09:17 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
trackers:
bionic/linux-azure-5.3: bug 1859819
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/1859820
Title:
eoan/linux-azure: 5.3.0-1010.11 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
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:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Eoan:
Fix Released
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: 1860119
packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
phase: Complete
phase-changed: Tuesday, 04. February 2020 09:17 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-azure-5.3: bug 1859819
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859820/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866484] Re: focal/linux-azure: 5.4.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => 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: 1866488
packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Promote to Release
- phase-changed: Thursday, 19. March 2020 17:16 UTC
+ phase: Complete
+ phase-changed: Friday, 20. March 2020 21:56 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
- reason:
- promote-to-release: Pending -- ready to copy
+ reason: {}
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/1866484
Title:
focal/linux-azure: 5.4.0-1006.6 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
Fix Released
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-release series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
Invalid
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Focal:
Fix Released
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: 1866488
packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
phase: Complete
phase-changed: Friday, 20. March 2020 21:56 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866484/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844245] Re: Integrate Intel SGX driver into linux-azure
This bug was fixed in the package linux-azure - 5.4.0-1006.6 --- linux-azure (5.4.0-1006.6) focal; urgency=medium * focal/linux-azure: 5.4.0-1006.6 -proposed tracker (LP: #1866484) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * Miscellaneous Ubuntu changes - [Config] Update configs for 5.4 [ Ubuntu: 5.4.0-18.22 ] * focal/linux: 5.4.0-18.22 -proposed tracker (LP: #1866488) * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update helper scripts * Add sysfs attribute to show remapped NVMe (LP: #1863621) - SAUCE: ata: ahci: Add sysfs attribute to show remapped NVMe device count * [20.04 FEAT] Compression improvements in Linux kernel (LP: #1830208) - lib/zlib: add s390 hardware support for kernel zlib_deflate - s390/boot: rename HEAP_SIZE due to name collision - lib/zlib: add s390 hardware support for kernel zlib_inflate - s390/boot: add dfltcc= kernel command line parameter - lib/zlib: add zlib_deflate_dfltcc_enabled() function - btrfs: use larger zlib buffer for s390 hardware compression - [Config] Introducing s390x specific kernel config option CONFIG_ZLIB_DFLTCC * [UBUNTU 20.04] s390x/pci: increase CONFIG_PCI_NR_FUNCTIONS to 512 in kernel config (LP: #1866056) - [Config] Increase CONFIG_PCI_NR_FUNCTIONS from 64 to 512 starting with focal on s390x * CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set (LP: #1865332) - [Config] CONFIG_IP_MROUTE_MULTIPLE_TABLES=y * Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware (LP: #1865962) - iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560 - iwlwifi: 22000: fix some indentation - iwlwifi: pcie: rx: use rxq queue_size instead of constant - iwlwifi: allocate more receive buffers for HE devices - iwlwifi: remove some outdated iwl22000 configurations - iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg * [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled (LP: #1861521) - Revert "USUNTU: SAUCE: drm/i915: Force DPCD backlight mode on Dell Precision 4K sku" - Revert "UBUNTU: SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel" - SAUCE: drm/dp: Introduce EDID-based quirks - SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel - SAUCE: drm/i915: Force DPCD backlight mode for some Dell CML 2020 panels * [20.04 FEAT] Enable proper kprobes on ftrace support (LP: #1865858) - s390/ftrace: save traced function caller - s390: support KPROBES_ON_FTRACE * alsa/sof: load different firmware on different platforms (LP: #1857409) - ASoC: SOF: Intel: hda: use fallback for firmware name - ASoC: Intel: acpi-match: split CNL tables in three - ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names. * [UBUNTU 20.04] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal (LP: #1865452) - [Config] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal * Focal update: v5.4.24 upstream stable release (LP: #1866333) - io_uring: grab ->fs as part of async offload - EDAC: skx_common: downgrade message importance on missing PCI device - net: dsa: b53: Ensure the default VID is untagged - net: fib_rules: Correctly set table field when table number exceeds 8 bits - net: macb: ensure interface is not suspended on at91rm9200 - net: mscc: fix in frame extraction - net: phy: restore mdio regs in the iproc mdio driver - net: sched: correct flower port blocking - net/tls: Fix to avoid gettig invalid tls record - nfc: pn544: Fix occasional HW initialization failure - qede: Fix race between rdma destroy workqueue and link change event - Revert "net: dev: introduce support for sch BYPASS for lockless qdisc" - udp: rehash on disconnect - sctp: move the format error check out of __sctp_sf_do_9_1_abort - bnxt_en: Improve device shutdown method. - bnxt_en: Issue PCIe FLR in kdump kernel to cleanup pending DMAs. - bonding: add missing netdev_update_lockdep_key() - net: export netdev_next_lower_dev_rcu() - bonding: fix lockdep warning in bond_get_stats() - ipv6: Fix route replacement with dev-only route - ipv6: Fix nlmsg_flags when splitting a multipath route - ipmi:ssif: Handle a possible NULL pointer reference - drm/msm: Set dma maximum segment size for mdss - sched/core: Don't skip remote tick for idle CPUs - timers/nohz: Update NOHZ load in remote tick - sched/fair: Prevent unlimited runtime on throttled group - dax: pass NOWAIT flag to iomap_apply - mac80211: consider more elements in parsing CRC - cfg80211: check wiphy driver existence for drvinfo report - s390/zcrypt: fix card and queue total counter wrap - qmi_wwan: re-add DW5821e pre-production variant - qmi_wwan: unconditi
[Kernel-packages] [Bug 1864884] Re: focal/linux-azure: 5.4.0-1004.4 -proposed tracker
*** This bug is a duplicate of bug 1866484 *** https://bugs.launchpad.net/bugs/1866484 This bug was fixed in the package linux-azure - 5.4.0-1006.6 --- linux-azure (5.4.0-1006.6) focal; urgency=medium * focal/linux-azure: 5.4.0-1006.6 -proposed tracker (LP: #1866484) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * Miscellaneous Ubuntu changes - [Config] Update configs for 5.4 [ Ubuntu: 5.4.0-18.22 ] * focal/linux: 5.4.0-18.22 -proposed tracker (LP: #1866488) * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update helper scripts * Add sysfs attribute to show remapped NVMe (LP: #1863621) - SAUCE: ata: ahci: Add sysfs attribute to show remapped NVMe device count * [20.04 FEAT] Compression improvements in Linux kernel (LP: #1830208) - lib/zlib: add s390 hardware support for kernel zlib_deflate - s390/boot: rename HEAP_SIZE due to name collision - lib/zlib: add s390 hardware support for kernel zlib_inflate - s390/boot: add dfltcc= kernel command line parameter - lib/zlib: add zlib_deflate_dfltcc_enabled() function - btrfs: use larger zlib buffer for s390 hardware compression - [Config] Introducing s390x specific kernel config option CONFIG_ZLIB_DFLTCC * [UBUNTU 20.04] s390x/pci: increase CONFIG_PCI_NR_FUNCTIONS to 512 in kernel config (LP: #1866056) - [Config] Increase CONFIG_PCI_NR_FUNCTIONS from 64 to 512 starting with focal on s390x * CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set (LP: #1865332) - [Config] CONFIG_IP_MROUTE_MULTIPLE_TABLES=y * Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware (LP: #1865962) - iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560 - iwlwifi: 22000: fix some indentation - iwlwifi: pcie: rx: use rxq queue_size instead of constant - iwlwifi: allocate more receive buffers for HE devices - iwlwifi: remove some outdated iwl22000 configurations - iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg * [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled (LP: #1861521) - Revert "USUNTU: SAUCE: drm/i915: Force DPCD backlight mode on Dell Precision 4K sku" - Revert "UBUNTU: SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel" - SAUCE: drm/dp: Introduce EDID-based quirks - SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel - SAUCE: drm/i915: Force DPCD backlight mode for some Dell CML 2020 panels * [20.04 FEAT] Enable proper kprobes on ftrace support (LP: #1865858) - s390/ftrace: save traced function caller - s390: support KPROBES_ON_FTRACE * alsa/sof: load different firmware on different platforms (LP: #1857409) - ASoC: SOF: Intel: hda: use fallback for firmware name - ASoC: Intel: acpi-match: split CNL tables in three - ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names. * [UBUNTU 20.04] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal (LP: #1865452) - [Config] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal * Focal update: v5.4.24 upstream stable release (LP: #1866333) - io_uring: grab ->fs as part of async offload - EDAC: skx_common: downgrade message importance on missing PCI device - net: dsa: b53: Ensure the default VID is untagged - net: fib_rules: Correctly set table field when table number exceeds 8 bits - net: macb: ensure interface is not suspended on at91rm9200 - net: mscc: fix in frame extraction - net: phy: restore mdio regs in the iproc mdio driver - net: sched: correct flower port blocking - net/tls: Fix to avoid gettig invalid tls record - nfc: pn544: Fix occasional HW initialization failure - qede: Fix race between rdma destroy workqueue and link change event - Revert "net: dev: introduce support for sch BYPASS for lockless qdisc" - udp: rehash on disconnect - sctp: move the format error check out of __sctp_sf_do_9_1_abort - bnxt_en: Improve device shutdown method. - bnxt_en: Issue PCIe FLR in kdump kernel to cleanup pending DMAs. - bonding: add missing netdev_update_lockdep_key() - net: export netdev_next_lower_dev_rcu() - bonding: fix lockdep warning in bond_get_stats() - ipv6: Fix route replacement with dev-only route - ipv6: Fix nlmsg_flags when splitting a multipath route - ipmi:ssif: Handle a possible NULL pointer reference - drm/msm: Set dma maximum segment size for mdss - sched/core: Don't skip remote tick for idle CPUs - timers/nohz: Update NOHZ load in remote tick - sched/fair: Prevent unlimited runtime on throttled group - dax: pass NOWAIT flag to iomap_apply - mac80211: consider more elements in parsing CRC - cfg80211: check wiphy driver existence for drvinfo report - s390/zcrypt: fix card and queue total
[Kernel-packages] [Bug 1864081] Re: focal/linux-azure: 5.4.0-1003.3 -proposed tracker
*** This bug is a duplicate of bug 1866484 *** https://bugs.launchpad.net/bugs/1866484 This bug was fixed in the package linux-azure - 5.4.0-1006.6 --- linux-azure (5.4.0-1006.6) focal; urgency=medium * focal/linux-azure: 5.4.0-1006.6 -proposed tracker (LP: #1866484) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * Miscellaneous Ubuntu changes - [Config] Update configs for 5.4 [ Ubuntu: 5.4.0-18.22 ] * focal/linux: 5.4.0-18.22 -proposed tracker (LP: #1866488) * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update helper scripts * Add sysfs attribute to show remapped NVMe (LP: #1863621) - SAUCE: ata: ahci: Add sysfs attribute to show remapped NVMe device count * [20.04 FEAT] Compression improvements in Linux kernel (LP: #1830208) - lib/zlib: add s390 hardware support for kernel zlib_deflate - s390/boot: rename HEAP_SIZE due to name collision - lib/zlib: add s390 hardware support for kernel zlib_inflate - s390/boot: add dfltcc= kernel command line parameter - lib/zlib: add zlib_deflate_dfltcc_enabled() function - btrfs: use larger zlib buffer for s390 hardware compression - [Config] Introducing s390x specific kernel config option CONFIG_ZLIB_DFLTCC * [UBUNTU 20.04] s390x/pci: increase CONFIG_PCI_NR_FUNCTIONS to 512 in kernel config (LP: #1866056) - [Config] Increase CONFIG_PCI_NR_FUNCTIONS from 64 to 512 starting with focal on s390x * CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set (LP: #1865332) - [Config] CONFIG_IP_MROUTE_MULTIPLE_TABLES=y * Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware (LP: #1865962) - iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560 - iwlwifi: 22000: fix some indentation - iwlwifi: pcie: rx: use rxq queue_size instead of constant - iwlwifi: allocate more receive buffers for HE devices - iwlwifi: remove some outdated iwl22000 configurations - iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg * [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled (LP: #1861521) - Revert "USUNTU: SAUCE: drm/i915: Force DPCD backlight mode on Dell Precision 4K sku" - Revert "UBUNTU: SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel" - SAUCE: drm/dp: Introduce EDID-based quirks - SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel - SAUCE: drm/i915: Force DPCD backlight mode for some Dell CML 2020 panels * [20.04 FEAT] Enable proper kprobes on ftrace support (LP: #1865858) - s390/ftrace: save traced function caller - s390: support KPROBES_ON_FTRACE * alsa/sof: load different firmware on different platforms (LP: #1857409) - ASoC: SOF: Intel: hda: use fallback for firmware name - ASoC: Intel: acpi-match: split CNL tables in three - ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names. * [UBUNTU 20.04] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal (LP: #1865452) - [Config] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal * Focal update: v5.4.24 upstream stable release (LP: #1866333) - io_uring: grab ->fs as part of async offload - EDAC: skx_common: downgrade message importance on missing PCI device - net: dsa: b53: Ensure the default VID is untagged - net: fib_rules: Correctly set table field when table number exceeds 8 bits - net: macb: ensure interface is not suspended on at91rm9200 - net: mscc: fix in frame extraction - net: phy: restore mdio regs in the iproc mdio driver - net: sched: correct flower port blocking - net/tls: Fix to avoid gettig invalid tls record - nfc: pn544: Fix occasional HW initialization failure - qede: Fix race between rdma destroy workqueue and link change event - Revert "net: dev: introduce support for sch BYPASS for lockless qdisc" - udp: rehash on disconnect - sctp: move the format error check out of __sctp_sf_do_9_1_abort - bnxt_en: Improve device shutdown method. - bnxt_en: Issue PCIe FLR in kdump kernel to cleanup pending DMAs. - bonding: add missing netdev_update_lockdep_key() - net: export netdev_next_lower_dev_rcu() - bonding: fix lockdep warning in bond_get_stats() - ipv6: Fix route replacement with dev-only route - ipv6: Fix nlmsg_flags when splitting a multipath route - ipmi:ssif: Handle a possible NULL pointer reference - drm/msm: Set dma maximum segment size for mdss - sched/core: Don't skip remote tick for idle CPUs - timers/nohz: Update NOHZ load in remote tick - sched/fair: Prevent unlimited runtime on throttled group - dax: pass NOWAIT flag to iomap_apply - mac80211: consider more elements in parsing CRC - cfg80211: check wiphy driver existence for drvinfo report - s390/zcrypt: fix card and queue total
[Kernel-packages] [Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker
This bug was fixed in the package linux-azure - 5.4.0-1006.6 --- linux-azure (5.4.0-1006.6) focal; urgency=medium * focal/linux-azure: 5.4.0-1006.6 -proposed tracker (LP: #1866484) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * Miscellaneous Ubuntu changes - [Config] Update configs for 5.4 [ Ubuntu: 5.4.0-18.22 ] * focal/linux: 5.4.0-18.22 -proposed tracker (LP: #1866488) * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update helper scripts * Add sysfs attribute to show remapped NVMe (LP: #1863621) - SAUCE: ata: ahci: Add sysfs attribute to show remapped NVMe device count * [20.04 FEAT] Compression improvements in Linux kernel (LP: #1830208) - lib/zlib: add s390 hardware support for kernel zlib_deflate - s390/boot: rename HEAP_SIZE due to name collision - lib/zlib: add s390 hardware support for kernel zlib_inflate - s390/boot: add dfltcc= kernel command line parameter - lib/zlib: add zlib_deflate_dfltcc_enabled() function - btrfs: use larger zlib buffer for s390 hardware compression - [Config] Introducing s390x specific kernel config option CONFIG_ZLIB_DFLTCC * [UBUNTU 20.04] s390x/pci: increase CONFIG_PCI_NR_FUNCTIONS to 512 in kernel config (LP: #1866056) - [Config] Increase CONFIG_PCI_NR_FUNCTIONS from 64 to 512 starting with focal on s390x * CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set (LP: #1865332) - [Config] CONFIG_IP_MROUTE_MULTIPLE_TABLES=y * Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware (LP: #1865962) - iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560 - iwlwifi: 22000: fix some indentation - iwlwifi: pcie: rx: use rxq queue_size instead of constant - iwlwifi: allocate more receive buffers for HE devices - iwlwifi: remove some outdated iwl22000 configurations - iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg * [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled (LP: #1861521) - Revert "USUNTU: SAUCE: drm/i915: Force DPCD backlight mode on Dell Precision 4K sku" - Revert "UBUNTU: SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel" - SAUCE: drm/dp: Introduce EDID-based quirks - SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel - SAUCE: drm/i915: Force DPCD backlight mode for some Dell CML 2020 panels * [20.04 FEAT] Enable proper kprobes on ftrace support (LP: #1865858) - s390/ftrace: save traced function caller - s390: support KPROBES_ON_FTRACE * alsa/sof: load different firmware on different platforms (LP: #1857409) - ASoC: SOF: Intel: hda: use fallback for firmware name - ASoC: Intel: acpi-match: split CNL tables in three - ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names. * [UBUNTU 20.04] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal (LP: #1865452) - [Config] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal * Focal update: v5.4.24 upstream stable release (LP: #1866333) - io_uring: grab ->fs as part of async offload - EDAC: skx_common: downgrade message importance on missing PCI device - net: dsa: b53: Ensure the default VID is untagged - net: fib_rules: Correctly set table field when table number exceeds 8 bits - net: macb: ensure interface is not suspended on at91rm9200 - net: mscc: fix in frame extraction - net: phy: restore mdio regs in the iproc mdio driver - net: sched: correct flower port blocking - net/tls: Fix to avoid gettig invalid tls record - nfc: pn544: Fix occasional HW initialization failure - qede: Fix race between rdma destroy workqueue and link change event - Revert "net: dev: introduce support for sch BYPASS for lockless qdisc" - udp: rehash on disconnect - sctp: move the format error check out of __sctp_sf_do_9_1_abort - bnxt_en: Improve device shutdown method. - bnxt_en: Issue PCIe FLR in kdump kernel to cleanup pending DMAs. - bonding: add missing netdev_update_lockdep_key() - net: export netdev_next_lower_dev_rcu() - bonding: fix lockdep warning in bond_get_stats() - ipv6: Fix route replacement with dev-only route - ipv6: Fix nlmsg_flags when splitting a multipath route - ipmi:ssif: Handle a possible NULL pointer reference - drm/msm: Set dma maximum segment size for mdss - sched/core: Don't skip remote tick for idle CPUs - timers/nohz: Update NOHZ load in remote tick - sched/fair: Prevent unlimited runtime on throttled group - dax: pass NOWAIT flag to iomap_apply - mac80211: consider more elements in parsing CRC - cfg80211: check wiphy driver existence for drvinfo report - s390/zcrypt: fix card and queue total counter wrap - qmi_wwan: re-add DW5821e pre-production variant - qmi_wwan: unconditi
[Kernel-packages] [Bug 1866484] Re: focal/linux-azure: 5.4.0-1006.6 -proposed tracker
This bug was fixed in the package linux-azure - 5.4.0-1006.6 --- linux-azure (5.4.0-1006.6) focal; urgency=medium * focal/linux-azure: 5.4.0-1006.6 -proposed tracker (LP: #1866484) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * Miscellaneous Ubuntu changes - [Config] Update configs for 5.4 [ Ubuntu: 5.4.0-18.22 ] * focal/linux: 5.4.0-18.22 -proposed tracker (LP: #1866488) * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update helper scripts * Add sysfs attribute to show remapped NVMe (LP: #1863621) - SAUCE: ata: ahci: Add sysfs attribute to show remapped NVMe device count * [20.04 FEAT] Compression improvements in Linux kernel (LP: #1830208) - lib/zlib: add s390 hardware support for kernel zlib_deflate - s390/boot: rename HEAP_SIZE due to name collision - lib/zlib: add s390 hardware support for kernel zlib_inflate - s390/boot: add dfltcc= kernel command line parameter - lib/zlib: add zlib_deflate_dfltcc_enabled() function - btrfs: use larger zlib buffer for s390 hardware compression - [Config] Introducing s390x specific kernel config option CONFIG_ZLIB_DFLTCC * [UBUNTU 20.04] s390x/pci: increase CONFIG_PCI_NR_FUNCTIONS to 512 in kernel config (LP: #1866056) - [Config] Increase CONFIG_PCI_NR_FUNCTIONS from 64 to 512 starting with focal on s390x * CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set (LP: #1865332) - [Config] CONFIG_IP_MROUTE_MULTIPLE_TABLES=y * Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware (LP: #1865962) - iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560 - iwlwifi: 22000: fix some indentation - iwlwifi: pcie: rx: use rxq queue_size instead of constant - iwlwifi: allocate more receive buffers for HE devices - iwlwifi: remove some outdated iwl22000 configurations - iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg * [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled (LP: #1861521) - Revert "USUNTU: SAUCE: drm/i915: Force DPCD backlight mode on Dell Precision 4K sku" - Revert "UBUNTU: SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel" - SAUCE: drm/dp: Introduce EDID-based quirks - SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel - SAUCE: drm/i915: Force DPCD backlight mode for some Dell CML 2020 panels * [20.04 FEAT] Enable proper kprobes on ftrace support (LP: #1865858) - s390/ftrace: save traced function caller - s390: support KPROBES_ON_FTRACE * alsa/sof: load different firmware on different platforms (LP: #1857409) - ASoC: SOF: Intel: hda: use fallback for firmware name - ASoC: Intel: acpi-match: split CNL tables in three - ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names. * [UBUNTU 20.04] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal (LP: #1865452) - [Config] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal * Focal update: v5.4.24 upstream stable release (LP: #1866333) - io_uring: grab ->fs as part of async offload - EDAC: skx_common: downgrade message importance on missing PCI device - net: dsa: b53: Ensure the default VID is untagged - net: fib_rules: Correctly set table field when table number exceeds 8 bits - net: macb: ensure interface is not suspended on at91rm9200 - net: mscc: fix in frame extraction - net: phy: restore mdio regs in the iproc mdio driver - net: sched: correct flower port blocking - net/tls: Fix to avoid gettig invalid tls record - nfc: pn544: Fix occasional HW initialization failure - qede: Fix race between rdma destroy workqueue and link change event - Revert "net: dev: introduce support for sch BYPASS for lockless qdisc" - udp: rehash on disconnect - sctp: move the format error check out of __sctp_sf_do_9_1_abort - bnxt_en: Improve device shutdown method. - bnxt_en: Issue PCIe FLR in kdump kernel to cleanup pending DMAs. - bonding: add missing netdev_update_lockdep_key() - net: export netdev_next_lower_dev_rcu() - bonding: fix lockdep warning in bond_get_stats() - ipv6: Fix route replacement with dev-only route - ipv6: Fix nlmsg_flags when splitting a multipath route - ipmi:ssif: Handle a possible NULL pointer reference - drm/msm: Set dma maximum segment size for mdss - sched/core: Don't skip remote tick for idle CPUs - timers/nohz: Update NOHZ load in remote tick - sched/fair: Prevent unlimited runtime on throttled group - dax: pass NOWAIT flag to iomap_apply - mac80211: consider more elements in parsing CRC - cfg80211: check wiphy driver existence for drvinfo report - s390/zcrypt: fix card and queue total counter wrap - qmi_wwan: re-add DW5821e pre-production variant - qmi_wwan: unconditi
[Kernel-packages] [Bug 1865021] Re: focal/linux-azure: 5.4.0-1005.5 -proposed tracker
*** This bug is a duplicate of bug 1866484 *** https://bugs.launchpad.net/bugs/1866484 This bug was fixed in the package linux-azure - 5.4.0-1006.6 --- linux-azure (5.4.0-1006.6) focal; urgency=medium * focal/linux-azure: 5.4.0-1006.6 -proposed tracker (LP: #1866484) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * Miscellaneous Ubuntu changes - [Config] Update configs for 5.4 [ Ubuntu: 5.4.0-18.22 ] * focal/linux: 5.4.0-18.22 -proposed tracker (LP: #1866488) * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update helper scripts * Add sysfs attribute to show remapped NVMe (LP: #1863621) - SAUCE: ata: ahci: Add sysfs attribute to show remapped NVMe device count * [20.04 FEAT] Compression improvements in Linux kernel (LP: #1830208) - lib/zlib: add s390 hardware support for kernel zlib_deflate - s390/boot: rename HEAP_SIZE due to name collision - lib/zlib: add s390 hardware support for kernel zlib_inflate - s390/boot: add dfltcc= kernel command line parameter - lib/zlib: add zlib_deflate_dfltcc_enabled() function - btrfs: use larger zlib buffer for s390 hardware compression - [Config] Introducing s390x specific kernel config option CONFIG_ZLIB_DFLTCC * [UBUNTU 20.04] s390x/pci: increase CONFIG_PCI_NR_FUNCTIONS to 512 in kernel config (LP: #1866056) - [Config] Increase CONFIG_PCI_NR_FUNCTIONS from 64 to 512 starting with focal on s390x * CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set (LP: #1865332) - [Config] CONFIG_IP_MROUTE_MULTIPLE_TABLES=y * Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware (LP: #1865962) - iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560 - iwlwifi: 22000: fix some indentation - iwlwifi: pcie: rx: use rxq queue_size instead of constant - iwlwifi: allocate more receive buffers for HE devices - iwlwifi: remove some outdated iwl22000 configurations - iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg * [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled (LP: #1861521) - Revert "USUNTU: SAUCE: drm/i915: Force DPCD backlight mode on Dell Precision 4K sku" - Revert "UBUNTU: SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel" - SAUCE: drm/dp: Introduce EDID-based quirks - SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel - SAUCE: drm/i915: Force DPCD backlight mode for some Dell CML 2020 panels * [20.04 FEAT] Enable proper kprobes on ftrace support (LP: #1865858) - s390/ftrace: save traced function caller - s390: support KPROBES_ON_FTRACE * alsa/sof: load different firmware on different platforms (LP: #1857409) - ASoC: SOF: Intel: hda: use fallback for firmware name - ASoC: Intel: acpi-match: split CNL tables in three - ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names. * [UBUNTU 20.04] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal (LP: #1865452) - [Config] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal * Focal update: v5.4.24 upstream stable release (LP: #1866333) - io_uring: grab ->fs as part of async offload - EDAC: skx_common: downgrade message importance on missing PCI device - net: dsa: b53: Ensure the default VID is untagged - net: fib_rules: Correctly set table field when table number exceeds 8 bits - net: macb: ensure interface is not suspended on at91rm9200 - net: mscc: fix in frame extraction - net: phy: restore mdio regs in the iproc mdio driver - net: sched: correct flower port blocking - net/tls: Fix to avoid gettig invalid tls record - nfc: pn544: Fix occasional HW initialization failure - qede: Fix race between rdma destroy workqueue and link change event - Revert "net: dev: introduce support for sch BYPASS for lockless qdisc" - udp: rehash on disconnect - sctp: move the format error check out of __sctp_sf_do_9_1_abort - bnxt_en: Improve device shutdown method. - bnxt_en: Issue PCIe FLR in kdump kernel to cleanup pending DMAs. - bonding: add missing netdev_update_lockdep_key() - net: export netdev_next_lower_dev_rcu() - bonding: fix lockdep warning in bond_get_stats() - ipv6: Fix route replacement with dev-only route - ipv6: Fix nlmsg_flags when splitting a multipath route - ipmi:ssif: Handle a possible NULL pointer reference - drm/msm: Set dma maximum segment size for mdss - sched/core: Don't skip remote tick for idle CPUs - timers/nohz: Update NOHZ load in remote tick - sched/fair: Prevent unlimited runtime on throttled group - dax: pass NOWAIT flag to iomap_apply - mac80211: consider more elements in parsing CRC - cfg80211: check wiphy driver existence for drvinfo report - s390/zcrypt: fix card and queue total
[Kernel-packages] [Bug 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
Same story here on a Lenovo S340 Ideapad with Xubuntu 19.10. More details can be found here https://superuser.com/q/1524979/865660 [1.045638] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) [1.045676] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
>From the Superuser link I left above, I suspect that this causes suspend issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868324] Re: Eoan update: upstream stable patchset 2020-03-20
** Description changed: - - 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-20 -from git://git.kernel.org/ + 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-20 + + Ported from the following upstream stable releases: + v4.19.106, v5.4.22 + + from git://git.kernel.org/ + + core: Don't skip generic XDP program execution for cloned SKBs + enic: prevent waking up stopped tx queues over watchdog reset + net/smc: fix leak of kernel memory to user space + net: dsa: tag_qca: Make sure there is headroom for tag + net/sched: matchall: add missing validation of TCA_MATCHALL_FLAGS + net/sched: flower: add missing validation of TCA_FLOWER_FLAGS + Revert "KVM: nVMX: Use correct root level for nested EPT shadow page tables" + KVM: nVMX: Use correct root level for nested EPT shadow page tables + drm/gma500: Fixup fbdev stolen size usage evaluation + cpu/hotplug, stop_machine: Fix stop_machine vs hotplug order + brcmfmac: Fix use after free in brcmf_sdio_readframes() + leds: pca963x: Fix open-drain initialization + ext4: fix ext4_dax_read/write inode locking sequence for IOCB_NOWAIT + ALSA: ctl: allow TLV read operation for callback type of element in locked case + gianfar: Fix TX timestamping with a stacked DSA driver + pinctrl: sh-pfc: sh7264: Fix CAN function GPIOs + pxa168fb: Fix the function used to release some memory in an error handling path + media: i2c: mt9v032: fix enum mbus codes and frame sizes + powerpc/powernv/iov: Ensure the pdn for VFs always contains a valid PE number + gpio: gpio-grgpio: fix possible sleep-in-atomic-context bugs in grgpio_irq_map/unmap() + iommu/vt-d: Fix off-by-one in PASID allocation + media: sti: bdisp: fix a possible sleep-in-atomic-context bug in bdisp_device_run() + pinctrl: baytrail: Do not clear IRQ flags on direct-irq enabled pins + efi/x86: Map the entire EFI vendor string before copying it + MIPS: Loongson: Fix potential NULL dereference in loongson3_platform_init() + sparc: Add .exit.data section. + uio: fix a sleep-in-atomic-context bug in uio_dmem_genirq_irqcontrol() + usb: gadget: udc: fix possible sleep-in-atomic-context bugs in gr_probe() + usb: dwc2: Fix IN FIFO allocation + clocksource/drivers/bcm2835_timer: Fix memory leak of timer + kselftest: Minimise dependency of get_size on C library interfaces + jbd2: clear JBD2_ABORT flag before journal_reset to update log tail info when load journal + x86/sysfb: Fix check for bad VRAM size + pwm: omap-dmtimer: Simplify error handling + s390/pci: Fix possible deadlock in recover_store() + powerpc/iov: Move VF pdev fixup into pcibios_fixup_iov() + tracing: Fix tracing_stat return values in error handling paths + tracing: Fix very unlikely race of registering two stat tracers + ARM: 8952/1: Disable kmemleak on XIP kernels + ext4, jbd2: ensure panic when aborting with zero errno + ath10k: Correct the DMA direction for management tx buffers + drm/amd/display: Retrain dongles when SINK_COUNT becomes non-zero + nbd: add a flush_workqueue in nbd_start_device + KVM: s390: ENOTSUPP -> EOPNOTSUPP fixups + kconfig: fix broken dependency in randconfig-generated .config + clk: qcom: rcg2: Don't crash if our parent can't be found; return an error + drm/amdgpu: remove 4 set but not used variable in amdgpu_atombios_get_connector_info_from_object_table + drm/amdgpu: Ensure ret is always initialized when using SOC15_WAIT_ON_RREG + regulator: rk808: Lower log level on optional GPIOs being not available + net/wan/fsl_ucc_hdlc: reject muram offsets above 64K + NFC: port100: Convert cpu_to_le16(le16_to_cpu(E1) + E2) to use le16_add_cpu(). + arm64: dts: allwinner: H6: Add PMU mode + arm: dts: allwinner: H3: Add PMU node + selinux: ensure we cleanup the internal AVC counters on error in avc_insert() + arm64: dts: qcom: msm8996: Disable USB2 PHY suspend by core + ARM: dts: imx6: rdu2: Disable WP for USDHC2 and USDHC3 + ARM: dts: imx6: rdu2: Limit USBH1 to Full Speed + PCI: iproc: Apply quirk_paxc_bridge() for module as well as built-in + media: cx23885: Add support for AVerMedia CE310
[Kernel-packages] [Bug 1868324] [NEW] Eoan update: upstream stable patchset 2020-03-20
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-20 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868324 Title: Eoan update: upstream stable patchset 2020-03-20 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-03-20 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature
This bug was fixed in the package s390-tools - 2.12.0-0ubuntu3 --- s390-tools (2.12.0-0ubuntu3) focal; urgency=medium * Update patch series to master tip: - PVM / genprotimg LP: #1834534, FFe LP: #1866866 - zipl/libc: Fix potential buffer overflow LP: #1865032 - zipl: Fix secureboot documentation LP: #1864654 - Many other smaller bugfixes -- Dimitri John Ledkov Fri, 20 Mar 2020 12:08:13 + ** Changed in: s390-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866866 Title: [FFe] Please accept patches for secure guest feature Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in s390-tools package in Ubuntu: Fix Released Bug description: The secure guest feature (aka protvirt) affects multiple components (kernel, qemu and s390-tools - see below). While dedicated tickets for the different components exist since quite a while, the code arrived late and/or discussion to get it upstream accepted took longer than expected. (Even if we as of today didn't reached the kernel freeze, I'm already adding kernel to this FFe.) Since this is a very important feature the current IBM Z and LinuxONE family, it's requested to be included into focal, the next LTS release, to become exploitable by long running systems. The code is largely architecture specific. No brand new packages or new upstream version are requested, only the cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able. kernel: The patch set for the kernel is huge (30+ commits), but has only one common code patch (two files). The arch specific patches landed in between in linux-next, the arch specific one is expected to land there very soon (hours/days from now). The common-code patch ran through several hands and landed in between in Andrew Morton's mmots tree. A pre-screening of the code was done by the kernel team and it looked acceptable. (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531) qemu: The entire code seems to be arch specific. Again a pre-screening of the maintainer lead to the fact that it should be acceptable, too. (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546) s390-tools: The entire tool only exists for the s390x architecture. Hence obviously everything is arch specific on that. (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534) Currently work is going on to test this function end to end based on Ubuntu components (means based on our s390-tools, qemu and kernel [focal master-next] trees). On top I applied the patches to the packages as well and did manual test buids. With that a potential regression can be considered as low - and even in case of a regression, it will affect s390x only. The patches are being staged for this feature in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863581] Re: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1
Hi Sumit, I have placed the test kernels at the following link can you please test it? https://people.canonical.com/~mreed/lp1863581_megaraid_sas/ Regards, Michael -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863581 Title: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1 Status in linux package in Ubuntu: In Progress Bug description: [IMPACT] This is a feature request to update megaraid_sas driver in Ubuntu 20.04 release to latest Linux upstream tip. The current latest upstream megaraid_sas driver version is- 07.713.01.00-rc1. The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver version- 07.710.50.00-rc1. [FIXES] Below set of upstream commit ids will lift driver version to 07.713.01.00-rc1 from 07.710.50.00-rc1: 92b4f9d15059 scsi: megaraid_sas: fixup MSIx interrupt setup during resume 824b72db5086 scsi: megaraid_sas: Update driver version to 07.713.01.00-rc1 4d1634b8d12e scsi: megaraid_sas: Use Block layer API to check SCSI device in-flight IO requests 56ee0c585602 scsi: megaraid_sas: Limit the number of retries for the IOCTLs causing firmware fault 6d7537270e32 scsi: megaraid_sas: Do not initiate OCR if controller is not in ready state 201a810cc188 scsi: megaraid_sas: Re-Define enum DCMD_RETURN_STATUS eeb63c23ffe1 scsi: megaraid_sas: Do not set HBA Operational if FW is not in operational state 9330a0fd827a scsi: megaraid_sas: Do not kill HBA if JBOD Seqence map or RAID map is disabled eb974f34bb9d scsi: megaraid_sas: Do not kill host bus adapter, if adapter is already dead 6e73550670ed scsi: megaraid_sas: Update optimal queue depth for SAS and NVMe devices a7faf81d7858 scsi: megaraid_sas: Set no_write_same only for Virtual Disk 499e7246d6da scsi: megaraid_sas: Reset adapter if FW is not in READY state after device resume 73374b39b01e scsi: megaraid_sas: Make poll_aen_lock static 01b8bca81e18 compat_ioctl: use correct compat_ptr() translation in drivers 8cfb8e40d686 scsi: megaraid_sas: remove unused variables 'debugBlk','fusion' ff7ca7fd03ce scsi: megaraid_sas: Unique names for MSI-X vectors 9ab089d30bcf scsi: megaraid_sas: Introduce module parameter for default queue depth e5460f084b84 scsi: megaraid_sas: Fix a compilation warning 88d5c343949e scsi: megaraid_sas: Make a bunch of functions static e45ab43b1d40 scsi: megaraid_sas: Make some functions static 3b5f307ef3cb scsi: megaraid_sas: fix panic on loading firmware crashdump 359603a3847e scsi: megaraid_sas: fix spelling mistake "megarid_sas" -> "megaraid_sas" 07d9aa143464 scsi: megaraid_sas: set an unlimited max_segment_size Here is the link to latest Linux upstream megaraid_sas driver source: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid Please let me know if any further information is required. Thanks, Sumit All are clean cherry picks into the 5.4 branch and can be pulled from the following branch: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp1863581_megaraid_sas [TESTING] Modinfo should show that the megaraid_sas driver has been updated to 07.713.01.00 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
For some reason it now stopped working again... Don't know why. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (163 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic
[Kernel-packages] [Bug 1865571] Re: Sound card not detected on HP Spectre x360 13-aw0xxx
Problem solved with latest kernel update. Closing. For reference: $ uname -r 5.4.0-18-generic ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865571 Title: Sound card not detected on HP Spectre x360 13-aw0xxx Status in linux package in Ubuntu: Fix Released Bug description: On a fresh Ubuntu 19.10 install with the Linux kernel updated to 5.3.0 (via proposed-packages), no sound card detected (CPU: Intel i7-1065G). Relevant dmesg output: ``` [4.544994] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-icl.ri failed with error -2 [4.544997] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-icl.ri failed err: -2 [4.544999] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [4.545000] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Mon Mar 2 20:47:33 2020 InstallationDate: Installed on 2020-02-28 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.44 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx dmi.product.sku: 8NF08EA#ABU dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-28 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-aw0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=4934ba68-d847-4a31-8844-10f79fcaab92 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.44 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx dmi.product.sku: 8NF08EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang I'm not sure that I should file a bug against the Linux kernel; My USB headset works fine on 5.3.0-43-generic if I *don't* install libasound2 from your PPA. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866879] Re: Failure to boot on linux-image-5.3.0-40-generic
I upgraded/updated to `5.3.0-42-generic` and now it boots without me having to change anything in grub. I've attached `journalctl -b` in case this is of help. All the best Paul ** Attachment added: "journalctl -b" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+attachment/5339448/+files/journalctl-42.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/1866879 Title: Failure to boot on linux-image-5.3.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu on the laptop, rebooted and everything was fine. I did an upgrade to all packages and found that when I rebooted, it fails to load. I found out that a workaround is to select linux- image-5.3.0-18-generic in grub which leads me to think that the issue is related to the upgrade of the linux-image 5.3.0 package. To be clear, linux-image-5.3.0-18-generic works but linux- image-5.3.0-40-generic does not. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 2027 F pulseaudio /dev/snd/controlC0: paul 2027 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 18:25:57 2020 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=/dev/mapper/vgubuntu-root ro 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.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature
FFe granted for s390-tools. ** Changed in: s390-tools (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/1866866 Title: [FFe] Please accept patches for secure guest feature Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in s390-tools package in Ubuntu: Confirmed Bug description: The secure guest feature (aka protvirt) affects multiple components (kernel, qemu and s390-tools - see below). While dedicated tickets for the different components exist since quite a while, the code arrived late and/or discussion to get it upstream accepted took longer than expected. (Even if we as of today didn't reached the kernel freeze, I'm already adding kernel to this FFe.) Since this is a very important feature the current IBM Z and LinuxONE family, it's requested to be included into focal, the next LTS release, to become exploitable by long running systems. The code is largely architecture specific. No brand new packages or new upstream version are requested, only the cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able. kernel: The patch set for the kernel is huge (30+ commits), but has only one common code patch (two files). The arch specific patches landed in between in linux-next, the arch specific one is expected to land there very soon (hours/days from now). The common-code patch ran through several hands and landed in between in Andrew Morton's mmots tree. A pre-screening of the code was done by the kernel team and it looked acceptable. (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531) qemu: The entire code seems to be arch specific. Again a pre-screening of the maintainer lead to the fact that it should be acceptable, too. (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546) s390-tools: The entire tool only exists for the s390x architecture. Hence obviously everything is arch specific on that. (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534) Currently work is going on to test this function end to end based on Ubuntu components (means based on our s390-tools, qemu and kernel [focal master-next] trees). On top I applied the patches to the packages as well and did manual test buids. With that a potential regression can be considered as low - and even in case of a regression, it will affect s390x only. The patches are being staged for this feature in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868290] [NEW] Disco update: upstream stable patchset 2020-03-20
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-20
Ported from the following upstream stable releases:
v4.19.106, v5.4.22
from git://git.kernel.org/
core: Don't skip generic XDP program execution for cloned SKBs
enic: prevent waking up stopped tx queues over watchdog reset
net/smc: fix leak of kernel memory to user space
net: dsa: tag_qca: Make sure there is headroom for tag
net/sched: matchall: add missing validation of TCA_MATCHALL_FLAGS
net/sched: flower: add missing validation of TCA_FLOWER_FLAGS
Revert "KVM: nVMX: Use correct root level for nested EPT shadow page tables"
KVM: nVMX: Use correct root level for nested EPT shadow page tables
drm/gma500: Fixup fbdev stolen size usage evaluation
cpu/hotplug, stop_machine: Fix stop_machine vs hotplug order
brcmfmac: Fix use after free in brcmf_sdio_readframes()
leds: pca963x: Fix open-drain initialization
ext4: fix ext4_dax_read/write inode locking sequence for IOCB_NOWAIT
ALSA: ctl: allow TLV read operation for callback type of element in locked case
gianfar: Fix TX timestamping with a stacked DSA driver
pinctrl: sh-pfc: sh7264: Fix CAN function GPIOs
pxa168fb: Fix the function used to release some memory in an error handling path
media: i2c: mt9v032: fix enum mbus codes and frame sizes
powerpc/powernv/iov: Ensure the pdn for VFs always contains a valid PE number
gpio: gpio-grgpio: fix possible sleep-in-atomic-context bugs in
grgpio_irq_map/unmap()
iommu/vt-d: Fix off-by-one in PASID allocation
media: sti: bdisp: fix a possible sleep-in-atomic-context bug in
bdisp_device_run()
pinctrl: baytrail: Do not clear IRQ flags on direct-irq enabled pins
efi/x86: Map the entire EFI vendor string before copying it
MIPS: Loongson: Fix potential NULL dereference in loongson3_platform_init()
sparc: Add .exit.data section.
uio: fix a sleep-in-atomic-context bug in uio_dmem_genirq_irqcontrol()
usb: gadget: udc: fix possible sleep-in-atomic-context bugs in gr_probe()
usb: dwc2: Fix IN FIFO allocation
clocksource/drivers/bcm2835_timer: Fix memory leak of timer
kselftest: Minimise dependency of get_size on C library interfaces
jbd2: clear JBD2_ABORT flag before journal_reset to update log tail info when
load journal
x86/sysfb: Fix check for bad VRAM size
pwm: omap-dmtimer: Simplify error handling
s390/pci: Fix possible deadlock in recover_store()
powerpc/iov: Move VF pdev fixup into pcibios_fixup_iov()
tracing: Fix tracing_stat return values in error handling paths
tracing: Fix very unlikely race of registering two stat tracers
ARM: 8952/1: Disable kmemleak on XIP kernels
ext4, jbd2: ensure panic when aborting with zero errno
ath10k: Correct the DMA direction for management tx buffers
drm/amd/display: Retrain dongles when SINK_COUNT becomes non-zero
nbd: add a flush_workqueue in nbd_start_device
KVM: s390: ENOTSUPP -> EOPNOTSUPP fixups
kconfig: fix broken dependency in randconfig-generated .config
clk: qcom: rcg2: Don't crash if our parent can't be found; return an error
drm/amdgpu: remove 4 set but not used variable in
amdgpu_atombios_get_connector_info_from_object_table
drm/amdgpu: Ensure ret is always initialized when using SOC15_WAIT_ON_RREG
regulator: rk808: Lower log level on optional GPIOs being not available
net/wan/fsl_ucc_hdlc: reject muram offsets above 64K
NFC: port100: Convert cpu_to_le16(le16_to_cpu(E1) + E2) to use le16_add_cpu().
arm64: dts: allwinner: H6: Add PMU mode
arm: dts: allwinner: H3: Add PMU node
selinux: ensure we cleanup the internal AVC counters on error in avc_insert()
arm64: dts: qcom: msm8996: Disable USB2 PHY suspend by core
ARM: dts: imx6: rdu2: Disable WP for USDHC2 and USDHC3
ARM: dts: imx6: rdu2: Limit USBH1 to Full Speed
PCI: iproc: Apply quirk_paxc_bridge() for module as well as built-in
media: cx23885: Add support for AVerMedia CE310B
PCI: Add generic quirk for increasing D3hot delay
PCI: Increase D3 delay for AMD Ryzen5/7 XHCI controllers
media: v4l2-device.h: Explicitly compare grp{id,mask} to zero in v4l2_device
macros
reiserfs: Fix spurious unlock in reiserfs_fill_super() error handling
r8169: check that Realtek PHY driver module is loaded
fore200e: Fix incorrect checks of NULL pointer dereference
netfilter: nft_tunnel: add the missing ERSPAN_VERSION nla_policy
ALSA: usx2y: Adjust indentation in snd_usX2Y_hwdep_dsp_status
b43legacy: Fix -Wcast-function-type
ipw2x00: Fix -Wcast-function-type
iwlegacy: Fix -Wcast-function-type
rtlwifi: rtl_pci: Fix -Wcast-function-type
orinoco: avoid assertion in case of NULL pointer
ACPICA: Dis
[Kernel-packages] [Bug 1860182] Autopkgtest regression report (zfs-linux/0.7.5-1ubuntu16.9)
All autopkgtests for the newly accepted zfs-linux (0.7.5-1ubuntu16.9) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#zfs-linux [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1860182 Title: zpool scrub malfunction after kernel upgrade Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Bionic: Fix Committed Bug description: == SRU Request [BIONIC] == The HWE kernel on bionic provides zfs 0.8.1 driver which includes an improved scrub however, the progress stats reported by the kernel are incompatible to the 0.7.x zfs driver. == Fix == Use the new zfs 8.x pool_scan_stat_t extra fields to calculate the scan progress when using zfs 8.x kernel drivers. Add detection of the kernel module version and use an approximation to the zfs 0.8.0 progress and rate reporting for newer kernels. For 0.7.5 we can pass the larger 8.x port_scan_stat_t to 0.7.5 zfs w/o problems and ignore these new fields and continue to use the 0.7.5 rate calculations. == Test == Install the HWE kernel on Bionic, create some large ZFS pools and populate with a lot of data. Issue: sudo zpool scrub poolname and then look at the progress using sudo zpool status Without the fix, the progress stats are incorrect. With the fix the duration and rate stats as a fairly good approximation of the progress. Since the newer 0.8.x zfs does scanning now in two phases the older zfs tools will only report accurate stats for phase #2 of the scan to keep it roughly compatible with the 0.7.x zfs utils output. == Regression Potential == This is a userspace reporting fix so the zpool status output is only affected by this fix when doing a scrub, so the impact of this fix is very small and limited. I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly: eric@eric-8700K:~$ zpool status pool: storagepool1 state: ONLINE scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24 2020 config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 I ran zpool scrub after upgrading the kernel and rebooting, and now it fails to work properly. It appeared to finish in about 5 minutes but did not, and says it is going slow: eric@eric-8700K:~$ sudo zpool status pool: storagepool1 state: ONLINE scan: scrub in progress since Fri Jan 17 15:32:07 2020 1.89T scanned out of 1.89T at 589M/s, (scan is slow, no estimated time) 0B repaired, 100.00% done config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 errors: No known data errors ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.7 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 16:22:01 2020 InstallationDate: Installed on 2018-03-07 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: zfs-linux UpgradeStatus: Upgraded to bionic on 2018-08-02 (533 days ago) modi
[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
problem solved for me (bionic) dpkg -l linux-firmware ... linux-firmware 1.173.17all Firmware for Linux kernel drivers dmesg |grep UVD [ 31.608796] [drm] UVD initialized successfully. -- 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/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (16
[Kernel-packages] [Bug 1845704] Re: HDMI monitor is not detected as sound output device starting from kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04
I just wanted to report that after last update HDMI sound output is working as expected again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845704 Title: HDMI monitor is not detected as sound output device starting from kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading Ubuntu 18.10 from kernel 4.18.0-20-generic to 4.18.0-21-generic, HDMI Audio stopped working, system does not detect it at all as a sound output device. Downgrading to 4.18.0-20 helped on Ubuntu 18.10, but currently I'm using Ubuntu 19.04 with kernel 5.0.0-29-generic, and HDMI sound still does not work and system cannot detect it. Adding the following parameters to GRUB didn't helped (): - amdgpu.dc=1 - radeon.audio=1 Video card: Radeon HD 4850 with 2 DVI ports with ability to output sound thru DVI (DVI-HDMI cable or DVI-HDMI adapter). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oshmyrko 2595 F pulseaudio /dev/snd/controlC2: oshmyrko 2595 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 22:14:27 2019 InstallationDate: Installed on 2019-04-13 (166 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=a88b1763-5d14-4204-ba95-d6718c22158d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-09 (80 days ago) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868286] [NEW] Disable A2DP when switch input device
Public bug reported: Hi, How to reproduce: 1) Connect the headset via Bluetooth 2) Automatically will use A2DP (until here everything ok) 3) Go to sound settings, will be the "internal microphone" selected. Switch to use the microphone of the headset and will switch to low-quality audio HSP Happens with the upgrade: bluez:amd64 (5.50-0ubuntu4 -> 5.50-0ubuntu5). Before that upgrade, everything was working fine. Only the automatic selection of A2DP fails sometimes but the microphone and A2DP were possible to use. After the mentioned upgrade to 5.50-0ubuntu5, it's just impossible to use the microphone and the A2DP audio at the same time. When I do the switch in the input device in the syslog it's the following message: kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 I tried to downgrade to 5.50-0ubuntu4 but didn't work, the A2DP is not usable at all. pulseaudio[8370]: Refused to switch profile to a2dp_sink: Not connected Description:Ubuntu 19.10 Release:19.10 Device: LE_WH-H900N (h.ear) Regards, ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1868286 Title: Disable A2DP when switch input device Status in bluez package in Ubuntu: New Bug description: Hi, How to reproduce: 1) Connect the headset via Bluetooth 2) Automatically will use A2DP (until here everything ok) 3) Go to sound settings, will be the "internal microphone" selected. Switch to use the microphone of the headset and will switch to low-quality audio HSP Happens with the upgrade: bluez:amd64 (5.50-0ubuntu4 -> 5.50-0ubuntu5). Before that upgrade, everything was working fine. Only the automatic selection of A2DP fails sometimes but the microphone and A2DP were possible to use. After the mentioned upgrade to 5.50-0ubuntu5, it's just impossible to use the microphone and the A2DP audio at the same time. When I do the switch in the input device in the syslog it's the following message: kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 I tried to downgrade to 5.50-0ubuntu4 but didn't work, the A2DP is not usable at all. pulseaudio[8370]: Refused to switch profile to a2dp_sink: Not connected Description: Ubuntu 19.10 Release: 19.10 Device: LE_WH-H900N (h.ear) Regards, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1868286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg
I'm still having the problem in (X)Ubuntu 18.4, NVIDIA-SMI 340.107Driver Version: 340.107| |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GT 130M -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-settings source package in Disco: In Progress Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
** Description changed: [IMPACT] + + This is related to bug + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340 + + both patch sets are needed to make up This is a massive number of updates by Broadcom to the lpfc driver that didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware support for 5 years, we need to ensure as much hardware support lands as possible to support server vendors over the next couple years. Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The version in focal is 12.2.0.3 and missing several bug fixes and hardware support additions. Please update the driver in focal appropriately. [FIXES] eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences 6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity: lpfc_get_scsi_buf_s3(): Null pointer dereferences 61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix lpfc_cpumask_of_node_init() eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel warning triggered by lpfc_sli4_enable_intr() 765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel warning triggered by lpfc_get_sgl_per_hdwq() aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version to 12.6.0.1 171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of multiple adapter dumps dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ model on AMD architectures 93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration for CPU Offline/Online events b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error message 69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2 SLER change to require Conf with SLER dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log enablement check 2332e6e475b016e2026763f51333f84e2e6c57a3 scsi: lpfc: Fix unexpected error messages during RSCN handling 6c1e803eac846f886cd35131e6516fc51a8414b9 scsi: lpfc: Fix kernel crash at lpfc_nvme_info_show during remote port bounce 6bfb1620829825c01e1dcdd63b6a7700352babd9 scsi: lpfc: Fix configuration of BB credit recovery in service parameters 7cfd5639d99bec0d27af089d0c8c114330e43a72 scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow 7b10db555257d1248398643a23e10cf36b50d516 scsi: lpfc: Make lpfc_debugfs_ras_log_data static c3e5aac3e2f501ad4fcb03fed0e32a6f009faea2 scsi: lpfc: Fix NULL check before mempool_destroy is not needed 5792a0e81678da41f05bb724ebd20f134604fa15 scsi: lpfc: fix spelling error in MAGIC_NUMER_xxx 9e2edb41c3d4cab6da0eedcc07ae04758af62ab8 scsi: lpfc: fix build error of lpfc_debugfs.c for vfree/vmalloc 5314995e370e46ac12d12378544ad4575b6f6672 scsi: lpfc: lpfc_nvmet: Fix Use plain integer as NULL pointer 2c7fb469024f0da98f4d078fcf570786ec87c384 scsi: lpfc: lpfc_attr: Fix Use plain integer as NULL pointer 74acec655f560ef721c1e191732af2bcb094b537 scsi: lpfc: Update lpfc version to 12.6.0.0 b4b3417cf6c8051f9f210cd694e6342fb008795c scsi: lpfc: Add additional discovery log messages 83c6cb1ae8be6948b5fa43b2450a176dba80688b scsi: lpfc: Add FC-AL support to lpe32000 models e7d8595272553c27846946601b72e4c581f9712a scsi: lpfc: Add FA-WWN Async Event reporting b1dfa5411ea440f7a5bd65176259ffb3bfbdecf0 scsi: lpfc: Add log macros to allow print by serverity or verbosity setting 95bfc6d8ad86a76c89f62bb466f740b0fc05a667 scsi: lpfc: Make FW logging dynamically configurable 8156d378c4cbf8ca19df5d8f0c610ce6923b61e2 scsi: lpfc: Revise interrupt coalescing for missing scenarios ea85a20cd54f3b09880f6c08994b059f0d114a11 scsi: lpfc: Remove lock contention target write path 22770cbabf6bb77a397d9f11d41f97667dd0caa2 scsi: lpfc: Slight fast-path performance optimizations f84f8f93f01feb64fdda8dd6c72d1b7dc24ad11d scsi: lpfc: fix coverity error of dereference after null check 91a52b617cdb8bf6d298892101c061d438b84a19 scsi: lpfc: Fix hardlockup in lpfc_abort_handler 324e1c402069e8d277d2a2b18ce40bde1265b96a scsi: lpfc: Fix bad ndlp ptr in xri aborted handling feff8b3d84d3d9570f893b4d83e5eab6693d6a52 scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices 27f3efd637ce4859a44a7ca730c72392b4111c26 scsi: lpfc: Fix lockdep errors in sli_ringtx_put 0a5ce731977da
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
My Secure Boot is always off, and all three U, X, Kubuntu have the error, as of yesterdays ISO. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
Here's dmesg after booting with 5.3.0-42-generic, with options snd-hda- intel dmic_detect=0 appended to the end of /etc/modprobe.d/alsa- base.conf. If I reboot into 5.3.0-40-generic, sound plays fine (of course the mic isn't detected, which I think is a well known bug). Where would I get the 5.3.0-43 package? Do I also need the alsa-lib package mentioned in https://bugs.launchpad.net/ubuntu/+source/alsa- lib/+bug/1859754/comments/66 ? ** Attachment added: "dmesg on CX1g7 after booting with 5.3.0-42-generic" https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/+attachment/5339399/+files/dmesg.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/1864061 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. In the -41 kernel, we introduced a patch from stable kernel, that make the sof driver crash, and there is a fix patch in the 5.6-rc1, and this fix patch is already in the stable and is merged to focal kernel, now we backport this patch to Eoan kernel if -42 doesn't introduce this fix patch from stable. The patch introduced the crash: commit 063821115e02229d5fd3de31bad270d5e30aeb41 Author: Dragos Tarcatu Date: Mon Dec 9 18:39:38 2019 -0600 ASoC: topology: Check return value for snd_soc_add_dai_link() BugLink: https://bugs.launchpad.net/bugs/1861929 [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] snd_soc_add_dai_link() might fail. This situation occurs for instance in a very specific use case where a PCM device and a Back End DAI link are given identical names in the topology. When this happens, soc_new_pcm_runtime() fails and then snd_soc_add_dai_link() returns -ENOMEM when called from soc_tplg_fe_link_create(). Because of that, the link will not get added into the card list, so any attempt to remove it later ends up in a panic. Fix that by checking the return status and free the memory in case of an error. Reviewed-by: Ranjani Sridharan Signed-off-by: Dragos Tarcatu Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously [Impact] During the boot, the sof driver crash because the hdmi_pcm_list is not initialized before it is used. [Fix] This bug is fixed in the mainline kernel v5.6-rc1, now backport this patch to ubuntu kernel [Test Case] Boot the -41 kernel with this patch added. blacklist the snd_soc_skl the kernel can boot successfully, and sof driver worked well [Regression Risk] Low, the patches are backported from upstream kernel, and I tested this patch on Lenovo and Dell dmic machines. Focal kernel already has this patch and works well. Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_gene
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
Would also be interested how to come back from my hacky solution to the default one. If the new kernel and packages are available in the stable branch i would also try to fix it myself and write a small guide. I can use timeshift to go back to my working version if i f**up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856340] Re: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies
** Description changed: [IMPACT] - Here are the kernel and cli updates we discussed in email related to - LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc + In the run up to 20.04 release, Broadcom wants to ensure that customers + running ubuntu 20.04 have the proper support when using Emulex + Fibrechannel cards to use NVMe over FC. + + This updates nvme-fc and nvme with cherry picks from 5.5 upstream that + didn't land in time for the upstream 5.4 release. + + Deferring this request would delay customers using NVMe over FC until + February when the first HWE for Focal is released, roughly 9 months from + now. + + Here are the kernel and cli updates broadcom requested via email related + to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. - Please pull these into Ubuntu 20.04. - - Thank you - Laurie - - Expected that ubuntu is pulling in kernel v5.4 as a base. These would - go on top of that. [FIXES] Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page These are clean cherry-picks from 5.5 into 5.4 and can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1856340-broadcom-nvme-updates These two are already in focal and are only left here for reference as they were part of the original request: 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues - [TESTING] - [REGRESSION RISK] + Low: Patches are already upstream in 5.5 and have been tested there and by Broadcom Emululex. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856340 Title: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] In the run up to 20.04 release, Broadcom wants to ensure that customers running ubuntu 20.04 have the proper support when using Emulex Fibrechannel cards to use NVMe over FC. This updates nvme-fc and nvme with cherry picks from 5.5 upstream that didn't land in time for the upstream 5.4 release. Deferring this request would delay customers using NVMe over FC until February when the first HWE for Focal is released, roughly 9 months from now. Here are the kernel and cli updates broadcom requested via email related to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. [FIXES] Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page These are clean cherry-picks from 5.5 into 5.4 and can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1856340-broadcom-nvme-updates These two are already in focal and are only left here for reference as they were part of the original request: 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues [REGRESSION RISK] Low: Patches are already upstream in 5.5 and have been tested there and by Broadcom Emululex. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860182] Re: zpool scrub malfunction after kernel upgrade
** Changed in: zfs-linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1860182 Title: zpool scrub malfunction after kernel upgrade Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Bionic: Fix Committed Bug description: == SRU Request [BIONIC] == The HWE kernel on bionic provides zfs 0.8.1 driver which includes an improved scrub however, the progress stats reported by the kernel are incompatible to the 0.7.x zfs driver. == Fix == Use the new zfs 8.x pool_scan_stat_t extra fields to calculate the scan progress when using zfs 8.x kernel drivers. Add detection of the kernel module version and use an approximation to the zfs 0.8.0 progress and rate reporting for newer kernels. For 0.7.5 we can pass the larger 8.x port_scan_stat_t to 0.7.5 zfs w/o problems and ignore these new fields and continue to use the 0.7.5 rate calculations. == Test == Install the HWE kernel on Bionic, create some large ZFS pools and populate with a lot of data. Issue: sudo zpool scrub poolname and then look at the progress using sudo zpool status Without the fix, the progress stats are incorrect. With the fix the duration and rate stats as a fairly good approximation of the progress. Since the newer 0.8.x zfs does scanning now in two phases the older zfs tools will only report accurate stats for phase #2 of the scan to keep it roughly compatible with the 0.7.x zfs utils output. == Regression Potential == This is a userspace reporting fix so the zpool status output is only affected by this fix when doing a scrub, so the impact of this fix is very small and limited. I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly: eric@eric-8700K:~$ zpool status pool: storagepool1 state: ONLINE scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24 2020 config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 I ran zpool scrub after upgrading the kernel and rebooting, and now it fails to work properly. It appeared to finish in about 5 minutes but did not, and says it is going slow: eric@eric-8700K:~$ sudo zpool status pool: storagepool1 state: ONLINE scan: scrub in progress since Fri Jan 17 15:32:07 2020 1.89T scanned out of 1.89T at 589M/s, (scan is slow, no estimated time) 0B repaired, 100.00% done config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 errors: No known data errors ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.7 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 16:22:01 2020 InstallationDate: Installed on 2018-03-07 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: zfs-linux UpgradeStatus: Upgraded to bionic on 2018-08-02 (533 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1860182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847832] Re: Backport ZoL pull request 9203 into the official packages.
Hello Alex, or anyone else affected,
Accepted zfs-linux into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.1-1ubuntu14.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
eoan to verification-done-eoan. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-eoan. In either case, without details of your testing we will not
be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: zfs-linux (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1847832
Title:
Backport ZoL pull request 9203 into the official packages.
Status in zfs-linux package in Ubuntu:
In Progress
Status in zfs-linux source package in Eoan:
Fix Committed
Bug description:
== SRU Justification, EOAN ==
ZFS can deadlock, this can be sometimes triggered with a zfs rollback
- "the zfs_resume_fs() code path may cause zfs to spawn new threads as
it reinstantiates the suspended fs's zil. When a new thread is
spawned, the kernel may attempt to free memory for that thread by
freeing some unreferenced inodes. If it happens to select inodes that
are a a part of the suspended fs a deadlock will occur because freeing
inodes requires holding the fs's z_teardown_inactive_lock which is
still held from the suspend."
== The Fix ==
Backport of ZFS upstream commit
e7a2fa70c3b0d8c8cee2b484038bb5623c7c1ea9 ("Fix deadlock in 'zfs
rollback'")
The backport is relatively simple context wiggle.
== Test Case ==
This is hard to trigger so testing is non-trivial. To check for
regressions we run the entire Ubuntu ZFS regression test suite.
Without the fix rollbacks can very occasionally trip this issue. With
the test, it's not possible.
== Regression Potential ==
The fix adds in an extra z_suspended flag to track suspended state and
adds an extra reference to stop the kernel from free'ing inodes on a
suspected file system. The changes are small and are well-used in
upstream ZFS so I believe if a regression was to have occurred it
would have been found by the regression testing.
- Original Bug Report Below ---
Hopefully this is the correct bug tracker to report this on.
Recently, I ran into a bug in ZFS as shipped in Ubuntu 19.10 that
caused the kernel to deadlock and the system to eventually hang.
I was advised by a ZFS on Linux project maintainer that this was a bug
that was fixed in 0.8.2.
The relevant pull request is here:
https://github.com/zfsonlinux/zfs/pull/9203
It would probably be a good idea to backport that pull request into
19.10's build of ZFS.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865130] Please test proposed package
Hello yahia, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.17 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.3
[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Hello yahia, or anyone else affected, Accepted linux-firmware into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.183.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Eoan) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5
[Kernel-packages] [Bug 1868222] Re: rpi don't boot with 5.4.0-1004-raspi2
The author provided that he resolved the case with an update package. ** Changed in: linux-raspi2 (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Balint Harmath (bharmath) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1868222 Title: rpi don't boot with 5.4.0-1004-raspi2 Status in linux-raspi2 package in Ubuntu: Invalid Bug description: -> tested on raspberry 3b+ and 4b After a fresh install of Ubuntu 20.04 (focal-preinstalled-server-arm64+raspi3.img), the rpi boots normally. Then execute an apt update/upgrade The Raspberry doesn't boot (no output on the console) Reverting the device tree to the previous version resolve the issue (a .bak is kept during the upgrade) (file bcm2710-rpi-3-b-plus.dtb for Raspberry 3b+, bcm2711-rpi-4-b.dtb for Rpi 4b) package linux-modules-5.4.0-1004-raspi2 $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ dpkg -S bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1004-raspi2: /lib/firmware/5.4.0-1004-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1001-raspi2: /lib/firmware/5.4.0-1001-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.3.0-1017-raspi2: /lib/firmware/5.3.0-1017-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb $ apt show linux-modules-5.4.0-1004-raspi2 Package: linux-modules-5.4.0-1004-raspi2 Version: 5.4.0-1004.4 Priority: optional Section: universe/kernel Source: linux-raspi2 Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 176 MB Download-Size: 29.9 MB APT-Manual-Installed: no APT-Sources: http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages Description: Linux kernel extra modules for version 5.4.0 on ARMv8 SMP Contains the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-raspi2 meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1868222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Committed -- 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/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Focal: Incomplete Status in linux-oem source package in Focal: New Bug description: Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867656] Re: Remove linux-firmware dependency from kernel meta packages for s390x
** Changed in: ubuntu-z-systems Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1867656 Title: Remove linux-firmware dependency from kernel meta packages for s390x Status in Ubuntu on IBM z Systems: In Progress Status in linux-meta package in Ubuntu: In Progress Bug description: As far as we understand all firmware upgrades (and the firmware itself) is coming from the HMC on case of IBM Z and LinuxONE. This not only incl. the CEC code, but also all the firmware for the different cards and adapters. If this is the case (and will be in future), it would make sense for us to get rid of the linux-firmware package for s390x - this would make things leaner, reduce size and eventually increase (installation) performance ... So please IBM can you confirm that all firmware updates (MCLs) are always done via the HMC and that is therefore the linux-firmware package is obsolete on s390x? Thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867656] Re: Remove linux-firmware dependency from kernel meta packages for s390x
https://lists.ubuntu.com/archives/kernel-team/2020-March/108407.html ** Changed in: linux-meta (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1867656 Title: Remove linux-firmware dependency from kernel meta packages for s390x Status in Ubuntu on IBM z Systems: In Progress Status in linux-meta package in Ubuntu: In Progress Bug description: As far as we understand all firmware upgrades (and the firmware itself) is coming from the HMC on case of IBM Z and LinuxONE. This not only incl. the CEC code, but also all the firmware for the different cards and adapters. If this is the case (and will be in future), it would make sense for us to get rid of the linux-firmware package for s390x - this would make things leaner, reduce size and eventually increase (installation) performance ... So please IBM can you confirm that all firmware updates (MCLs) are always done via the HMC and that is therefore the linux-firmware package is obsolete on s390x? Thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
Vincenzo, can you confirm (or not) that you changed your secure boot settings since Ubuntu was installed? Can you check comment #26? 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/1835660 Title: initramfs unpacking failed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768452] Re: Insert test_bpf module will report 4 failures for ubuntu_bpf_jit on X s390x
** Description changed: == SRU Justification == In the ubuntu_bpf_jit test, it will insert the test_bpf module to perform the test. There will be 4 failures reported on s390x instances by the test, 3 of them were simply because they cannot be jited on s390x: * test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 * test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 * test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 (For another failure "ld_abs+vlan_push/pop" please check bug 1868243) == Fix == * 3203c901 (test_bpf: flag tests that cannot be jited on s390) - This patch needs to be backported to Xenial as some test case does not exist. + Only Xenial needs this patch, and it needs to be backported to Xenial + as some test case does not exist. == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1768452-bpf-jit/ The test will be marked as pass with the patched kernel: test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations PASS test_bpf: #244 BPF_MAXINSNS: Call heavy transformations PASS test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id PASS == Regression Potential == Low, change limited to the test_bpf module itself and specific to s390x, no impact to real functions. == Original Bug Report == After the test_bpf insert issue for Xenial was fixed in bug 1765698 But it looks like the s390x needs some extra work. $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument 4 tests failed here: test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 Complete test result: https://pastebin.ubuntu.com/p/zMDwVjwF7X/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 2 03:45:22 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768452 Title: Insert test_bpf module will report 4 failures for ubuntu_bpf_jit on X s390x 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 Disco: Fix Released Bug description: == SRU Justification == In the ubuntu_bpf_jit test, it will insert the test_bpf module to perform the test. There will be 4 failures reported on s390x instances by the test, 3 of them were simply because they cannot be jited on s390x: * test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 * test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 * test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 (For another failure "ld_abs+vlan_push/pop" please check bug 1868243) == Fix == * 3203c901 (test_bpf: flag tests that cannot be jited on s390) Only Xenial needs this patch, and it needs to be backported to Xenial as some test case does not exist. == Test == Test kernel
[Kernel-packages] [Bug 1836858] Re: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
Daniel, could get a debug log and report upstream? https://wiki.ubuntu.com/Plymouth#Enabling_Debugging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836858 Title: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Bug description: I am trying flickerfree boot in 19.10 [1], but find it actually flickers part way through: 1. BIOS logo on a black background. 2. Display mode resets, no image on a black background briefly. 3. BIOS logo on a black background. The flicker occurs seemingly during kernel startup since my peripherals are lit up before the problem occurs. Suspecting this might be related to FB handover: [2.751028] fb0: switching to inteldrmfb from EFI VGA I tried disabling that with a big hammer: i915.modeset=0 so it stays in efifb, and that works -- no more flickering, providing I don't let i915 take over the framebuffer. [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 17 16:34:36 2019 InstallationDate: Installed on 2019-05-02 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) MachineType: LENOVO 10M7CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768452] Re: Insert test_bpf module will report 4 failures for ubuntu_bpf_jit on X s390x
** Description changed: == SRU Justification == - In the ubuntu_bpf_jit test, it will insert the test_bpf module to perform the test. There will be 4 failures reported on s390x instances by the test, 3 of them were simply because they cannot be jited: + In the ubuntu_bpf_jit test, it will insert the test_bpf module to perform the test. There will be 4 failures reported on s390x instances by the test, 3 of them were simply because they cannot be jited on s390x: * test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 * test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 * test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 - (For another failure please check bug 1868243) + (For another failure "ld_abs+vlan_push/pop" please check bug 1868243) == Fix == * 3203c901 (test_bpf: flag tests that cannot be jited on s390) This patch needs to be backported to Xenial as some test case does not exist. == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1768452-bpf-jit/ The test will be marked as pass with the patched kernel: test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations PASS test_bpf: #244 BPF_MAXINSNS: Call heavy transformations PASS test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id PASS == Regression Potential == Low, change limited to the test_bpf module itself and specific to s390x, no impact to real functions. == Original Bug Report == After the test_bpf insert issue for Xenial was fixed in bug 1765698 But it looks like the s390x needs some extra work. $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument 4 tests failed here: test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 Complete test result: https://pastebin.ubuntu.com/p/zMDwVjwF7X/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 2 03:45:22 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768452 Title: Insert test_bpf module will report 4 failures for ubuntu_bpf_jit on X s390x 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 Disco: Fix Released Bug description: == SRU Justification == In the ubuntu_bpf_jit test, it will insert the test_bpf module to perform the test. There will be 4 failures reported on s390x instances by the test, 3 of them were simply because they cannot be jited on s390x: * test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 * test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 * test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 (For another failure "ld_abs+vlan_push/pop" please check bug 1868243) == Fix == * 3203c901 (test_bpf: flag tests that cannot be jite
[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash
5.3.0-42-generic -> still happening. Put my thinkpad in standby, disconnect it from the docking station, woke it up, user session crashed. Starting at Mar 20 09:59:52 deus-ex-machina at-spi-bus-launcher[6411]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" ** Attachment added: "journalctl--since-today.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5339307/+files/journalctl--since-today.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 962082] Re: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips
@Tim Abell (comment #18): I also have D-Link DBT-122. AD2P works fine, while I have no audio in HSP/HFP mode in Xenial. I didn't try the mic, but I bet it doesn't work either. On the net I see that the Mac recognize this adapter as a Broadcom BCM2035. Did you find a solution? Is there any firmware for this to fix the proble? Any help from anyone would be appreciated. -- 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/962082 Title: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips Status in HWE Next: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: This problem seems to occur on every device that uses the BCM20702A0 Bluetooth hardware. How to reproduce: (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0. (2) Activate the device. Usually there is a button on the headset you should press to notify the bluetooth stack that you're ready to use the device. This creates SCO link and the plumbs the audio components. (3) Open the sound settings tool and select the bluetooth device under the "Input" and "Output" tabs. Under each tab you should see a table with an entry that has a headset icon on the left with the bluetooth device name to the right. This is the item to select. Now, everything should be configured so that you can use your bluetooth device to hear and record audio. Test this by: Testing Input: (1) In the sound settings tool, select the "Input" tab. (2) Make sure the "Input Volume" is not muted and the scale widget is not set to zero. (3) Make sounds into the headset mic -- you should see the "Input Level" bar raise. Testing Output: In the same program: (1) Select the "Hardware" tab. (2) In the box labeled "Choose a device to configure", select your bluetooth device. (3) A combobox should appear at the bottom of the window labeled "Settings for the selected device". Choose "Telephony Duplex (HSP/HFP)". (4) Now click on the "Test Speakers" button to the right. (5) Run speaker test. You should hear a sound. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/962082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
Can we have a quick write-up of everything needed to test these fixes ? >From UCM to Kernel updates, just to have a standard procedure and avoid configuration issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868222] Re: rpi don't boot with 5.4.0-1004-raspi2
I have tried the focal-proposed repo. # echo "deb http://ports.ubuntu.com/ubuntu-ports focal-proposed universe" > /etc/apt/sources.list $ sudo apt update && sudo apt -t focal-proposed install linux-raspi2 && sudo reboot Reboot is fine, and the dtb file is the latest version. -> linux-modules-5.4.0-1006-raspi2 fix the issue. Tested on both rpi4b and rpi3b+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1868222 Title: rpi don't boot with 5.4.0-1004-raspi2 Status in linux-raspi2 package in Ubuntu: New Bug description: -> tested on raspberry 3b+ and 4b After a fresh install of Ubuntu 20.04 (focal-preinstalled-server-arm64+raspi3.img), the rpi boots normally. Then execute an apt update/upgrade The Raspberry doesn't boot (no output on the console) Reverting the device tree to the previous version resolve the issue (a .bak is kept during the upgrade) (file bcm2710-rpi-3-b-plus.dtb for Raspberry 3b+, bcm2711-rpi-4-b.dtb for Rpi 4b) package linux-modules-5.4.0-1004-raspi2 $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ dpkg -S bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1004-raspi2: /lib/firmware/5.4.0-1004-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1001-raspi2: /lib/firmware/5.4.0-1001-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.3.0-1017-raspi2: /lib/firmware/5.3.0-1017-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb $ apt show linux-modules-5.4.0-1004-raspi2 Package: linux-modules-5.4.0-1004-raspi2 Version: 5.4.0-1004.4 Priority: optional Section: universe/kernel Source: linux-raspi2 Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 176 MB Download-Size: 29.9 MB APT-Manual-Installed: no APT-Sources: http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages Description: Linux kernel extra modules for version 5.4.0 on ARMv8 SMP Contains the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-raspi2 meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1868222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867753] Comment bridged from LTC Bugzilla
--- Comment From h.carst...@de.ibm.com 2020-03-20 05:56 EDT--- (In reply to comment #17) > (In reply to comment #16) > > Let me just double check with you about disabling CONFIG_PM, as it also > > supports runtime power management of devices. If CONFIG_PM is disabled > > devices will not be put into low power states when idle. > > Yes, that's perfectly fine. There is now low power state for devices on s390. I meant to write: There is _no_ low power state for devices on s390. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868243] 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 1868243
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
** Changed in: linux (Ubuntu Xenial)
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/1868243
Title:
ld_abs+vlan_push/pop from ubuntu_bpf_jit will fail on X s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
Issue separated from bug 1768452
The ubuntu_bpf_jit will report the following failure on Xenial s390x:
* test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime
err=-524
This test has been moved to the test_verifier test in bpf of kselftests:
https://github.com/torvalds/linux/commit/93731ef086cee90af594e62874bb98ae6d6eee91
"Remove all eBPF tests involving LD_ABS/LD_IND from test_bpf.ko. Reason
is that the eBPF tests from test_bpf module do not go via BPF verifier
and therefore any instruction rewrites from verifier cannot take place.
Therefore, move them into test_verifier which runs out of user space,
so that verfier can rewrite LD_ABS/LD_IND internally in upcoming patches.
It will have the same effect since runtime tests are also performed from
there. This also allows to finally unexport bpf_skb_vlan_{push,pop}_proto
and keep it internal to core kernel."
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1868243/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868243] Re: ld_abs+vlan_push/pop from ubuntu_bpf_jit will fail on X s390x
** Description changed:
Issue separated from bug 1768452
The ubuntu_bpf_jit will report the following failure on Xenial s390x:
- * test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime
err=-524
+ * test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime
err=-524
- This test has been moved to the bpf in kselftests:
+ This test has been moved to the test_verifier test in bpf of kselftests:
https://github.com/torvalds/linux/commit/93731ef086cee90af594e62874bb98ae6d6eee91
"Remove all eBPF tests involving LD_ABS/LD_IND from test_bpf.ko. Reason
is that the eBPF tests from test_bpf module do not go via BPF verifier
and therefore any instruction rewrites from verifier cannot take place.
Therefore, move them into test_verifier which runs out of user space,
so that verfier can rewrite LD_ABS/LD_IND internally in upcoming patches.
It will have the same effect since runtime tests are also performed from
there. This also allows to finally unexport bpf_skb_vlan_{push,pop}_proto
and keep it internal to core 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/1868243
Title:
ld_abs+vlan_push/pop from ubuntu_bpf_jit will fail on X s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
Issue separated from bug 1768452
The ubuntu_bpf_jit will report the following failure on Xenial s390x:
* test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime
err=-524
This test has been moved to the test_verifier test in bpf of kselftests:
https://github.com/torvalds/linux/commit/93731ef086cee90af594e62874bb98ae6d6eee91
"Remove all eBPF tests involving LD_ABS/LD_IND from test_bpf.ko. Reason
is that the eBPF tests from test_bpf module do not go via BPF verifier
and therefore any instruction rewrites from verifier cannot take place.
Therefore, move them into test_verifier which runs out of user space,
so that verfier can rewrite LD_ABS/LD_IND internally in upcoming patches.
It will have the same effect since runtime tests are also performed from
there. This also allows to finally unexport bpf_skb_vlan_{push,pop}_proto
and keep it internal to core kernel."
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1868243/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768452] Re: Insert test_bpf module will report 4 failures for ubuntu_bpf_jit on X s390x
** Description changed: + == SRU Justification == + In the ubuntu_bpf_jit test, it will insert the test_bpf module to perform the test. There will be 4 failures reported on s390x instances by the test, 3 of them were simply because they cannot be jited: + * test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 + * test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 + * test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 + + (For another failure please check bug 1868243) + + == Fix == + * 3203c901 (test_bpf: flag tests that cannot be jited on s390) + This patch needs to be backported to Xenial as some test case does not exist. + + == Test == + Test kernel could be found here: + https://people.canonical.com/~phlin/kernel/lp-1768452-bpf-jit/ + + The test will be marked as pass with the patched kernel: + test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations PASS + test_bpf: #244 BPF_MAXINSNS: Call heavy transformations PASS + test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id PASS + + == Regression Potential == + Low, change limited to the test_bpf module itself, no impact to real functions. + + == Original Bug Report == After the test_bpf insert issue for Xenial was fixed in bug 1765698 But it looks like the s390x needs some extra work. $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument 4 tests failed here: - test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 - test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 - test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 - test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 + test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 + test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 + test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 + test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 Complete test result: https://pastebin.ubuntu.com/p/zMDwVjwF7X/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 2 03:45:22 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: - linux-restricted-modules-4.4.0-123-generic N/A - linux-backports-modules-4.4.0-123-generic N/A - linux-firmware 1.157.17 + linux-restricted-modules-4.4.0-123-generic N/A + linux-backports-modules-4.4.0-123-generic N/A + linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Tags added: sru-20200316 ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: ubuntu-kernel-tests Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Description changed: == SRU Justification == In the ubuntu_bpf_jit test, it will insert the test_bpf module to perform the test. There will be 4 failures reported on s390x instances by the test, 3 of them were simply because they cannot be jited: - * test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 - * test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 - * test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 + *
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
Hi everyone again, i am experiencing some APCI issues using 5.3.0-40 with sof drivers activated. It happens, almost randomly at this stage that the system is not waking up after a sleep, initiated by Gnome, what i see is just the fn led active on the X1-carbon-7h. It seems that disabling sof and loading the standard kernel modules (the blacklisted ones) the problem disappear. I saw that in 41 and 42 there are some ACPI-related fixes, but suddenly they broke the mic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868243] [NEW] ld_abs+vlan_push/pop from ubuntu_bpf_jit will fail on X s390x
Public bug reported:
Issue separated from bug 1768452
The ubuntu_bpf_jit will report the following failure on Xenial s390x:
* test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime
err=-524
This test has been moved to the test_verifier test in bpf of kselftests:
https://github.com/torvalds/linux/commit/93731ef086cee90af594e62874bb98ae6d6eee91
"Remove all eBPF tests involving LD_ABS/LD_IND from test_bpf.ko. Reason
is that the eBPF tests from test_bpf module do not go via BPF verifier
and therefore any instruction rewrites from verifier cannot take place.
Therefore, move them into test_verifier which runs out of user space,
so that verfier can rewrite LD_ABS/LD_IND internally in upcoming patches.
It will have the same effect since runtime tests are also performed from
there. This also allows to finally unexport bpf_skb_vlan_{push,pop}_proto
and keep it internal to core kernel."
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Tags: 4.4 s390x sru-20200106 sru-20200217 sru-20200316 ubuntu-bpf-jit xenial
** Tags added: 4.4 s390x sru-20200316 ubuntu-bpf-jit
** Tags added: sru-20200106 sru-20200217
** Tags added: xenial
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
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/1868243
Title:
ld_abs+vlan_push/pop from ubuntu_bpf_jit will fail on X s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
New
Bug description:
Issue separated from bug 1768452
The ubuntu_bpf_jit will report the following failure on Xenial s390x:
* test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime
err=-524
This test has been moved to the test_verifier test in bpf of kselftests:
https://github.com/torvalds/linux/commit/93731ef086cee90af594e62874bb98ae6d6eee91
"Remove all eBPF tests involving LD_ABS/LD_IND from test_bpf.ko. Reason
is that the eBPF tests from test_bpf module do not go via BPF verifier
and therefore any instruction rewrites from verifier cannot take place.
Therefore, move them into test_verifier which runs out of user space,
so that verfier can rewrite LD_ABS/LD_IND internally in upcoming patches.
It will have the same effect since runtime tests are also performed from
there. This also allows to finally unexport bpf_skb_vlan_{push,pop}_proto
and keep it internal to core kernel."
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1868243/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866866] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2020-03-20 05:42 EDT--- (In reply to comment #8) > For completeness reasons (and this current FFe) please see the attached > debdiff. > But for better readability the following link is probably preferable: > https://github.com/borntraeger/qemu/commits/pv42 > > The debdiff shows the difference between Ubuntu latest qemu 4.2 and pv42, > EXCEPT (see LP 1835546/, comment #15): > - 9da000ea0a "rebuild bios" -- not picked ok as you build that yourself > - ae150759a9 "s390/sclp: improve special wait psw logic" -- not needed This is needed, but according to ChristianE already in via qemu stable. Correct? > - 3c664ea0a6 "vhost: correctly turn on VIRTIO_F_IOMMU_PLATFORM" -- already in ok -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866866 Title: [FFe] Please accept patches for secure guest feature Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: The secure guest feature (aka protvirt) affects multiple components (kernel, qemu and s390-tools - see below). While dedicated tickets for the different components exist since quite a while, the code arrived late and/or discussion to get it upstream accepted took longer than expected. (Even if we as of today didn't reached the kernel freeze, I'm already adding kernel to this FFe.) Since this is a very important feature the current IBM Z and LinuxONE family, it's requested to be included into focal, the next LTS release, to become exploitable by long running systems. The code is largely architecture specific. No brand new packages or new upstream version are requested, only the cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able. kernel: The patch set for the kernel is huge (30+ commits), but has only one common code patch (two files). The arch specific patches landed in between in linux-next, the arch specific one is expected to land there very soon (hours/days from now). The common-code patch ran through several hands and landed in between in Andrew Morton's mmots tree. A pre-screening of the code was done by the kernel team and it looked acceptable. (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531) qemu: The entire code seems to be arch specific. Again a pre-screening of the maintainer lead to the fact that it should be acceptable, too. (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546) s390-tools: The entire tool only exists for the s390x architecture. Hence obviously everything is arch specific on that. (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534) Currently work is going on to test this function end to end based on Ubuntu components (means based on our s390-tools, qemu and kernel [focal master-next] trees). On top I applied the patches to the packages as well and did manual test buids. With that a potential regression can be considered as low - and even in case of a regression, it will affect s390x only. The patches are being staged for this feature in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature
@ 'Ubuntu Release Team' would you be so kind having a look at the: - s390-tools patches/changes in comment #7 (more details in Bug:1835546)and the - qemu patches/changes in comment #8 (more details in Bug:1834534) that are asked for in this FFe and let us know if the information is adequate and the changes acceptable -thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866866 Title: [FFe] Please accept patches for secure guest feature Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: The secure guest feature (aka protvirt) affects multiple components (kernel, qemu and s390-tools - see below). While dedicated tickets for the different components exist since quite a while, the code arrived late and/or discussion to get it upstream accepted took longer than expected. (Even if we as of today didn't reached the kernel freeze, I'm already adding kernel to this FFe.) Since this is a very important feature the current IBM Z and LinuxONE family, it's requested to be included into focal, the next LTS release, to become exploitable by long running systems. The code is largely architecture specific. No brand new packages or new upstream version are requested, only the cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able. kernel: The patch set for the kernel is huge (30+ commits), but has only one common code patch (two files). The arch specific patches landed in between in linux-next, the arch specific one is expected to land there very soon (hours/days from now). The common-code patch ran through several hands and landed in between in Andrew Morton's mmots tree. A pre-screening of the code was done by the kernel team and it looked acceptable. (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531) qemu: The entire code seems to be arch specific. Again a pre-screening of the maintainer lead to the fact that it should be acceptable, too. (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546) s390-tools: The entire tool only exists for the s390x architecture. Hence obviously everything is arch specific on that. (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534) Currently work is going on to test this function end to end based on Ubuntu components (means based on our s390-tools, qemu and kernel [focal master-next] trees). On top I applied the patches to the packages as well and did manual test buids. With that a potential regression can be considered as low - and even in case of a regression, it will affect s390x only. The patches are being staged for this feature in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867753] Comment bridged from LTC Bugzilla
--- Comment From h.carst...@de.ibm.com 2020-03-20 05:34 EDT--- (In reply to comment #16) > Let me just double check with you about disabling CONFIG_PM, as it also > supports runtime power management of devices. If CONFIG_PM is disabled > devices will not be put into low power states when idle. Yes, that's perfectly fine. There is now low power state for devices on s390. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
The 5.3 kernel can't work with the sof-firmware-1.4.2. So please have a try with the linux-firmware of 19.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
This is for eoan. Since focal will use the alsa-lib-1.2.1.2 and it already switch to use ucm2, so this SRU doesn't apply to focal, only for eoan and bionic. ** Patch added: "alsa-lib_1.1.9-0ubuntu1.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+attachment/5339265/+files/alsa-lib_1.1.9-0ubuntu1.3.debdiff ** Also affects: alsa-lib (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: alsa-lib (Ubuntu Eoan) Status: New => Confirmed ** Changed in: alsa-lib (Ubuntu Eoan) Importance: Undecided => High ** Description changed: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] + after applying this patch, I installed the testing alsa-lib on lenovo X1C7 and Dell vostro5390 which are all machines with the dmic connected to pch, after booing up, I checked the /usr/share/alsa/ucm/, the LENOVO-BIOSID-xxx folders are there, and the LENOVO machine loaded the N2H/*.conf, it worked well, the Dell machine still loaded the ucm by cardname, it worked as good as before. [Regression Potential] + low, just add some new ucms and let LENOVO machine find the ucm by bios_version if it fails by cardlongname. And already tested the change on lenovo and dell machines. -- 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/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Eoan: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] after applying this patch, I installed the testing alsa-lib on lenovo X1C7 and Dell vostro5390 which are all machines with the dmic connected to pch, after booing up, I checked the /usr/share/alsa/ucm/, the LENOVO-BIOSID-xxx folders are there, and the LENOVO machine loaded the N2H/*.conf, it worked well, the Dell machine still loaded the ucm by cardname, it worked as good as before. [Regression Potential] low, just add some new ucms and let LENOVO machine find the ucm by bios_version if it fails by cardlongname. And already tested the change on lenovo and dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature
For completeness reasons (and this current FFe) please see the attached debdiff. But for better readability the following link is probably preferable: https://github.com/borntraeger/qemu/commits/pv42 The debdiff shows the difference between Ubuntu latest qemu 4.2 and pv42, EXCEPT (see LP 1835546/, comment #15): - 9da000ea0a "rebuild bios" -- not picked - ae150759a9 "s390/sclp: improve special wait psw logic" -- not needed - 3c664ea0a6 "vhost: correctly turn on VIRTIO_F_IOMMU_PLATFORM" -- already in With that, all patches/commits are s390x specific, except some header changes: - 6807f46 "Sync pv" ** Patch added: "focal_qemu_content.diff" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+attachment/5339279/+files/focal_qemu_content.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866866 Title: [FFe] Please accept patches for secure guest feature Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: The secure guest feature (aka protvirt) affects multiple components (kernel, qemu and s390-tools - see below). While dedicated tickets for the different components exist since quite a while, the code arrived late and/or discussion to get it upstream accepted took longer than expected. (Even if we as of today didn't reached the kernel freeze, I'm already adding kernel to this FFe.) Since this is a very important feature the current IBM Z and LinuxONE family, it's requested to be included into focal, the next LTS release, to become exploitable by long running systems. The code is largely architecture specific. No brand new packages or new upstream version are requested, only the cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able. kernel: The patch set for the kernel is huge (30+ commits), but has only one common code patch (two files). The arch specific patches landed in between in linux-next, the arch specific one is expected to land there very soon (hours/days from now). The common-code patch ran through several hands and landed in between in Andrew Morton's mmots tree. A pre-screening of the code was done by the kernel team and it looked acceptable. (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531) qemu: The entire code seems to be arch specific. Again a pre-screening of the maintainer lead to the fact that it should be acceptable, too. (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546) s390-tools: The entire tool only exists for the s390x architecture. Hence obviously everything is arch specific on that. (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534) Currently work is going on to test this function end to end based on Ubuntu components (means based on our s390-tools, qemu and kernel [focal master-next] trees). On top I applied the patches to the packages as well and did manual test buids. With that a potential regression can be considered as low - and even in case of a regression, it will affect s390x only. The patches are being staged for this feature in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864871] Re: Failed to init Intel sound card in 20.04
Had the problem on Ubuntu 18.04 with kernel 5.3.0-42-generic, too. Going back to 5.3.0-40-generic resolved the issue for now. -- 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/1864871 Title: Failed to init Intel sound card in 20.04 Status in linux-5.4 package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card there is no sound available because sound card not detected (only dummy output available in sound settings): $ alsamixer cannot open mixer: No such file or directory $ lspci -nnk |grep -A2 audio lspci: Unable to load libkmod resources: error -12 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Lenovo Device [17aa:3816] Kernel driver in use: sof-audio-pci 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3] Subsystem: Lenovo Device [17aa:3819] $ pacmd list-cards 0 card(s) available. $ dmesg |grep sof [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB) [2.142149] systemd[1]: Mounting Mount unit for software-boutique, revision 54... [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 54. [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [2.817054] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 I've found similar bug reported here: https://bugs.archlinux.org/task/64720 As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot options and after that sound card successfully detected and started working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 26 19:22:05 2020 InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20RR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1864871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://h
[Kernel-packages] [Bug 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic
The same here, yet in 4.15.0-91 upgraded yesterday (March 19th, 2020). 4.15.0-88 had the same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836858] Re: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
Interesting. I tried changing this machine to Nvidia-only (nouveau driver) and the bug remains. So it's not unique to i915. ** Summary changed: - i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background + Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background ** Also affects: plymouth (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/1836858 Title: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Bug description: I am trying flickerfree boot in 19.10 [1], but find it actually flickers part way through: 1. BIOS logo on a black background. 2. Display mode resets, no image on a black background briefly. 3. BIOS logo on a black background. The flicker occurs seemingly during kernel startup since my peripherals are lit up before the problem occurs. Suspecting this might be related to FB handover: [2.751028] fb0: switching to inteldrmfb from EFI VGA I tried disabling that with a big hammer: i915.modeset=0 so it stays in efifb, and that works -- no more flickering, providing I don't let i915 take over the framebuffer. [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 17 16:34:36 2019 InstallationDate: Installed on 2019-05-02 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) MachineType: LENOVO 10M7CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853422] Re: sync_file_range02 from ubuntu_ltp_syscalls failed with XFS on 4.4
Passed with X/T 4.4 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:71: PASS: Sync inside of write sync_file_range02.c:71: PASS: Sync overlaps with write Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-aws (Ubuntu) Status: New => Invalid -- 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/1853422 Title: sync_file_range02 from ubuntu_ltp_syscalls failed with XFS on 4.4 Status in ubuntu-kernel-tests: Fix Released Status in linux-aws package in Ubuntu: Invalid Bug description: Test failed xfs filesystem: tst_test.c:1278: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25165824, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write startup='Mon Nov 18 08:59:23 2019' tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop0' tst_supported_fs_types.c:59: INFO: Kernel supports ext2 tst_supported_fs_types.c:43: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:59: INFO: Kernel supports ext3 tst_supported_fs_types.c:43: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:59: INFO: Kernel supports ext4 tst_supported_fs_types.c:43: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:59: INFO: Kernel supports xfs tst_supported_fs_types.c:43: INFO: mkfs.xfs does exist tst_supported_fs_types.c:59: INFO: Kernel supports btrfs tst_supported_fs_types.c:39: INFO: mkfs.btrfs does not exist tst_supported_fs_types.c:59: INFO: Kernel supports vfat tst_supported_fs_types.c:43: INFO: mkfs.vfat does exist tst_supported_fs_types.c:82: INFO: Filesystem exfat is not supported tst_test.c:1278: INFO: Testing on ext2 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:71: PASS: Sync inside of write sync_file_range02.c:71: PASS: Sync overlaps with write tst_test.c:1278: INFO: Testing on ext3 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:71: PASS: Sync inside of write sync_file_range02.c:71: PASS: Sync overlaps with write tst_test.c:1278: INFO: Testing on ext4 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:71: PASS: Sync inside of write sync_file_range02.c:71: PASS: Sync overlaps with write tst_test.c:1278: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25165824, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write tst_test.c:1278: INFO: Testing on vfat tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:111: INFO: Pre-filling file sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:71: PASS: Sync inside of write sync_file_range02.c:71: PASS: Sync overlaps with write Summary: passed 14 failed 1 skipped 0 warnings 0 tag=sync_file_range02 stime=1574067563 dur=4 exit=exited stat=1 core=no cu=0 cs=57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861470] Re: BIOS logo reappears mid-boot after the purple screen
Fixed, somewhere. ** Changed in: grub2 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-signed-5.4 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: plymouth (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861470 Title: BIOS logo reappears mid-boot after the purple screen Status in grub2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-signed-5.4 package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Bug description: BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple screen. This seems to be happening reliably on multiple focal machines: 0. Turn on or reboot the machine. 1. See the BIOS logo. 2. See a blank purple screen (grub) 3. See the BIOS logo again (this bug) 4. See the purple screen with Ubuntu logo (plymouth) 5. See the login screen I believe this is related to ACPI BGRT changes in the kernel. And I guess it wouldn't even need fixing if we just eliminated the blank purple grub screen (step 2)... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 11:31:44 2020 InstallationDate: Installed on 2020-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1316 F pulseaudio DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: LENOVO 20KFCTO1WW Package: linux-signed-5.4 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N20ET51W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X280 dmi.product.name: 20KFCTO1WW dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280 dmi.product.version: ThinkPad X280 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1861470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
Hm, previously I tried the script at #12. Maybe this is a firmware relict? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
** Also affects: alsa-lib (Ubuntu Focal) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Also affects: alsa-lib (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
@sponsor-team, This is a SRU of alsa-lib for bionic (18.04). thx. ** Patch added: "alsa-lib_1.1.3-5ubuntu0.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+attachment/5339264/+files/alsa-lib_1.1.3-5ubuntu0.5.debdiff -- 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/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
** Changed in: alsa-lib (Ubuntu Focal) Status: New => Invalid ** Changed in: alsa-lib (Ubuntu Bionic) Status: New => Confirmed ** Changed in: alsa-lib (Ubuntu Bionic) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Focal) Importance: Critical => Undecided ** Changed in: alsa-lib (Ubuntu Bionic) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: alsa-lib (Ubuntu Focal) Assignee: Hui Wang (hui.wang) => (unassigned) -- 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/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868227] 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 1868227 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/1868227 Title: Backport jitter entroy changes? Status in linux package in Ubuntu: Incomplete Bug description: One of our Ubuntu Core 16 devices failed to boot after a refresh recently [0]. After some debugging it turns out that it hangs in early boot because there is not enough entropy available. Snapd is using entropy to init it's CRNG and a change in snapd broke the boot. However while debugging/fixing this issue I was wondering if it would be possible to backport the new jitter entropy patches from kernel 5.4 [1] to the older LTS kernels. Thanks, Michael [0] https://bugs.launchpad.net/plano/+bug/1866940 [1] https://lwn.net/Articles/802360/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868227] [NEW] Backport jitter entroy changes?
Public bug reported: One of our Ubuntu Core 16 devices failed to boot after a refresh recently [0]. After some debugging it turns out that it hangs in early boot because there is not enough entropy available. Snapd is using entropy to init it's CRNG and a change in snapd broke the boot. However while debugging/fixing this issue I was wondering if it would be possible to backport the new jitter entropy patches from kernel 5.4 [1] to the older LTS kernels. Thanks, Michael [0] https://bugs.launchpad.net/plano/+bug/1866940 [1] https://lwn.net/Articles/802360/ ** 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/1868227 Title: Backport jitter entroy changes? Status in linux package in Ubuntu: New Bug description: One of our Ubuntu Core 16 devices failed to boot after a refresh recently [0]. After some debugging it turns out that it hangs in early boot because there is not enough entropy available. Snapd is using entropy to init it's CRNG and a change in snapd broke the boot. However while debugging/fixing this issue I was wondering if it would be possible to backport the new jitter entropy patches from kernel 5.4 [1] to the older LTS kernels. Thanks, Michael [0] https://bugs.launchpad.net/plano/+bug/1866940 [1] https://lwn.net/Articles/802360/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
Alexander, Looks like your sof-firmware is not same as the one on my machine (/lib/firmware/intel/sof|sof-tplg). Where did you find it? The sof- firmware on my machine is installed with linux-firmware of 19.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865965] Re: kill11 from ubuntu_ltp_syscalls failed
This test would pass if you run it directly: ubuntu@moe:/opt/ltp/testcases/bin$ sudo ./kill11 tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s kill11.c:117: INFO: Adjusting RLIMIT_CORE to 524288 kill11.c:97: PASS: signal SIGHUP kill11.c:97: PASS: signal SIGINT kill11.c:97: PASS: signal SIGQUIT dumped core kill11.c:97: PASS: signal SIGILL dumped core kill11.c:97: PASS: signal SIGTRAP dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGBUS dumped core kill11.c:97: PASS: signal SIGFPE dumped core kill11.c:97: PASS: signal SIGKILL kill11.c:97: PASS: signal SIGUSR1 kill11.c:97: PASS: signal SIGSEGV dumped core kill11.c:97: PASS: signal SIGUSR2 kill11.c:97: PASS: signal SIGPIPE kill11.c:97: PASS: signal SIGALRM kill11.c:97: PASS: signal SIGTERM kill11.c:97: PASS: signal SIGSTKFLT kill11.c:97: PASS: signal SIGXCPU dumped core kill11.c:97: PASS: signal SIGXFSZ dumped core kill11.c:97: PASS: signal SIGVTALRM kill11.c:97: PASS: signal SIGPROF kill11.c:97: PASS: signal SIGIO/SIGPOLL kill11.c:97: PASS: signal SIGPWR kill11.c:97: PASS: signal SIGSYS/SIGUNUSED dumped core Summary: passed 24 failed 0 skipped 0 warnings 0 Need to check if this is a composite issue with other cases. ** Tags added: sru-20200316 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865965 Title: kill11 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: startup='Tue Mar 3 15:46:25 2020' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s kill11.c:97: PASS: signal SIGHUP kill11.c:97: PASS: signal SIGINT kill11.c:97: PASS: signal SIGQUIT dumped core kill11.c:97: PASS: signal SIGILL dumped core kill11.c:97: PASS: signal SIGTRAP dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGBUS dumped core kill11.c:97: PASS: signal SIGFPE dumped core kill11.c:97: PASS: signal SIGKILL kill11.c:97: PASS: signal SIGUSR1 kill11.c:97: PASS: signal SIGSEGV dumped core kill11.c:97: PASS: signal SIGUSR2 kill11.c:97: PASS: signal SIGPIPE kill11.c:97: PASS: signal SIGALRM kill11.c:97: PASS: signal SIGTERM kill11.c:97: PASS: signal SIGSTKFLT kill11.c:97: PASS: signal SIGXCPU dumped core Test timeouted, sending SIGKILL! tst_test.c:1269: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1270: BROK: Test killed! (timeout?) Summary: passed 18 failed 0 skipped 0 warnings 0 tag=kill11 stime=1583250385 dur=302 exit=exited stat=2 core=no cu=0 cs=0 Need to see if bump the timeout threshold can help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
full journal log with kernel 5.3.0-43-generic ** Attachment added: "journallog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+attachment/5339251/+files/journallog.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/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
I tried kernel 5.3.0-43 from proposed but my notebook does not wake up from S3 suspend anymore (Lenovo Carbon X1 7th gen). It was working with kernel 5.3.0-40... I recognized some errors regarding this sound update package in journallog. Maybe this causes suspend not to work? Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: use msi interrupt mode Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: hda codecs found, mask 5 Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: unexpected ipc interrupt raised! Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: Firmware info: version 1:1:0-fcf6c Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: Firmware: ABI 3:11:0 Kernel ABI 3:8:0 Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: firmware boot complete Mär 20 07:24:25 m19040-lin kernel: skl_hda_dsp_generic skl_hda_dsp_generic: info: override FE DAI link iDisp1 Mär 20 07:24:25 m19040-lin kernel: skl_hda_dsp_generic skl_hda_dsp_generic: info: override FE DAI link iDisp2 Mär 20 07:24:25 m19040-lin kernel: skl_hda_dsp_generic skl_hda_dsp_generic: info: override FE DAI link iDisp3 Mär 20 07:24:25 m19040-lin kernel: skl_hda_dsp_generic skl_hda_dsp_generic: info: override FE DAI link Analog Playback and Capture Mär 20 07:24:25 m19040-lin kernel: skl_hda_dsp_generic skl_hda_dsp_generic: info: override FE DAI link Digital Playback and Capture Mär 20 07:24:25 m19040-lin kernel: skl_hda_dsp_generic skl_hda_dsp_generic: info: override FE DAI link dmic01 Mär 20 07:24:25 m19040-lin kernel: skl_hda_dsp_generic skl_hda_dsp_generic: info: override FE DAI link dmic16k Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: Topology: ABI 3:7:0 Kernel ABI 3:8:0 Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU Playback not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU Capture not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not handled Mär 20 07:24:25 m19040-lin kernel: sof-audio-pci :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred Mär 20 07:24:25 m19040-lin kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker Mär 20 07:24:25 m19040-lin kernel: snd_hda_codec_realtek ehdaudio0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Mär 20 07:24:25 m19040-lin kernel: snd_hda_codec_real
[Kernel-packages] [Bug 1868222] [NEW] rpi don't boot with 5.4.0-1004-raspi2
Public bug reported: -> tested on raspberry 3b+ and 4b After a fresh install of Ubuntu 20.04 (focal-preinstalled-server-arm64+raspi3.img), the rpi boots normally. Then execute an apt update/upgrade The Raspberry doesn't boot (no output on the console) Reverting the device tree to the previous version resolve the issue (a .bak is kept during the upgrade) (file bcm2710-rpi-3-b-plus.dtb for Raspberry 3b+, bcm2711-rpi-4-b.dtb for Rpi 4b) package linux-modules-5.4.0-1004-raspi2 $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ dpkg -S bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1004-raspi2: /lib/firmware/5.4.0-1004-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1001-raspi2: /lib/firmware/5.4.0-1001-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.3.0-1017-raspi2: /lib/firmware/5.3.0-1017-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb $ apt show linux-modules-5.4.0-1004-raspi2 Package: linux-modules-5.4.0-1004-raspi2 Version: 5.4.0-1004.4 Priority: optional Section: universe/kernel Source: linux-raspi2 Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 176 MB Download-Size: 29.9 MB APT-Manual-Installed: no APT-Sources: http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages Description: Linux kernel extra modules for version 5.4.0 on ARMv8 SMP Contains the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-raspi2 meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1868222 Title: rpi don't boot with 5.4.0-1004-raspi2 Status in linux-raspi2 package in Ubuntu: New Bug description: -> tested on raspberry 3b+ and 4b After a fresh install of Ubuntu 20.04 (focal-preinstalled-server-arm64+raspi3.img), the rpi boots normally. Then execute an apt update/upgrade The Raspberry doesn't boot (no output on the console) Reverting the device tree to the previous version resolve the issue (a .bak is kept during the upgrade) (file bcm2710-rpi-3-b-plus.dtb for Raspberry 3b+, bcm2711-rpi-4-b.dtb for Rpi 4b) package linux-modules-5.4.0-1004-raspi2 $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ dpkg -S bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1004-raspi2: /lib/firmware/5.4.0-1004-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1001-raspi2: /lib/firmware/5.4.0-1001-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.3.0-1017-raspi2: /lib/firmware/5.3.0-1017-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb $ apt show linux-modules-5.4.0-1004-raspi2 Package: linux-modules-5.4.0-1004-raspi2 Version: 5.4.0-1004.4 Priority: optional Section: universe/kernel Source: linux-raspi2 Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 176 MB Download-Size: 29.9 MB APT-Manual-Installed: no APT-Sources: http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages Description: Linux kernel extra modules for version 5.4.0 on ARMv8 SMP Contains the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-raspi2 meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. To manage notifications about this bug go to: https://bugs.launchp
[Kernel-packages] [Bug 1868217] 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 1868217 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 ** Changed in: linux (Ubuntu Eoan) 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/1868217 Title: Make Dell WD19 dock more reliable after suspend Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: Incomplete Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Incomplete Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When Dell WD19 dock connects multiple USB3 storage devices, the USB Hub used internally may stop working after suspend. [Fix] Disable LPM on the Realtek USB Hub, and let xHCI controller make sure the link state transition is completed. [Test] After applying the patches, the Dell WD19 works reliably after thousand times for suspend/resume cycle. [Regression Potential] Low. This replaces the currently "msleep" way with more robust mechanism. I also test other systems and nothing breaks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864092] Re: quotactl07 from ubuntu_ltp_syscalls failed
quotactl07.c:32: PASS: Q_XQUOTARM has quota type check ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You 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 1868217] Re: Make Dell WD19 dock more reliable after suspend
** Tags added: oem-priority originate-from-1853942 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868217 Title: Make Dell WD19 dock more reliable after suspend Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: New Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When Dell WD19 dock connects multiple USB3 storage devices, the USB Hub used internally may stop working after suspend. [Fix] Disable LPM on the Realtek USB Hub, and let xHCI controller make sure the link state transition is completed. [Test] After applying the patches, the Dell WD19 works reliably after thousand times for suspend/resume cycle. [Regression Potential] Low. This replaces the currently "msleep" way with more robust mechanism. I also test other systems and nothing breaks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
Hi @humbell, yeah i wrote this back in january when i freshly got my X1C7. It still works pretty good for me now with the -40-generic kernel. Newer kernels currently don't work and/or breaking reboots/sleep. I will also wait for @hui.wangs new kernel and libasound2 and test this locally. Using Timeshift to back to my working environment if needed. Hope we can get this one finally fixed for everyone with default packages and without hacky stuff. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation doesn't work. A microphone on a headset plugged into the 3.5mm jack works fine. This is probably relevant: https://bugzilla.kernel.org/show_bug.cgi?id=201251 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:13:25 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
** Tags added: sru-20200316 ** Tags added: 4.15 4.4 5.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Test failure in fallocate06 was composed by two issues, one is xfs fill_fs test issue addressed in bug 1865967. Another is this one, this is the case 2 of btrfs (fill_fs): tst_test.c:1290: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is 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:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2 This issue can be found from X to F X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/ B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/ D - https://pastebin.ubuntu.com/p/cryTnnn5wF/ E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/ F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/ Note that the hint printed in the test: HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e It something that will get printed after the test, as it's for XFS so it has nothing to do with this issue here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
