[Kernel-packages] [Bug 1859283] Re: package linux-modules-5.3.0-26-generic (not installed) failed to install/upgrade: no se puede crear el nuevo fichero '/var/lib/dpkg/info/linux-modules-5.3.0-26-gene
Marked as Incomplete as per comment #3, please change it back after fulfilling the request. Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859283 Title: package linux-modules-5.3.0-26-generic (not installed) failed to install/upgrade: no se puede crear el nuevo fichero '/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no permitida Status in linux package in Ubuntu: Incomplete Bug description: Is not posible update ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-modules-5.3.0-26-generic (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alvaro 1157 F pulseaudio Date: Sat Jan 11 13:00:47 2020 DpkgHistoryLog: Start-Date: 2020-01-11 13:00:42 Commandline: packagekit role='install-packages' Requested-By: alvaro (1000) Install: leocad:amd64 (19.07.1-1), libqt5concurrent5:amd64 (5.12.4+dfsg-4ubuntu1, automatic), linux-image-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), linux-headers-5.3.0-26:amd64 (5.3.0-26.28, automatic), linux-headers-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), linux-modules-extra-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), linux-modules-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic) Upgrade: linux-headers-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), linux-image-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), linux-generic:amd64 (5.3.0.24.28, 5.3.0.26.30) DpkgTerminalLog: Preparando para desempaquetar .../0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb ... Desempaquetando linux-modules-5.3.0-26-generic (5.3.0-26.28) ... dpkg: error al procesar el archivo /tmp/apt-dpkg-install-LCVldB/0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb (--unpack): no se puede crear el nuevo fichero '/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no permitida ErrorMessage: no se puede crear el nuevo fichero '/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no permitida InstallationDate: Installed on 2019-09-28 (104 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: TOSHIBA SATELLITE C855-21N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=5b70d5f9-c5a5-4122-8a7a-3e80eea36553 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1 SourcePackage: linux Title: package linux-modules-5.3.0-26-generic (not installed) failed to install/upgrade: no se puede crear el nuevo fichero '/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no permitida UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.70 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: PLCSF8 dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.70:bd07/17/2013:svnTOSHIBA:pnSATELLITEC855-21N:pvrPSCBWE-07900MCE:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE C855-21N dmi.product.sku: PSCBWE dmi.product.version: PSCBWE-07900MCE dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878907] Re: package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
As Trusty is in ESM state, I am going to close this bug, please feel free to open a new one if you're still seeing this issue. Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1878907 Title: package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: Won't Fix Bug description: linux update error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-55-generic 3.13.0-55.94 ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emody 1906 F pulseaudio Date: Fri May 15 14:03:24 2020 DuplicateSignature: package:linux-image-3.13.0-55-generic:3.13.0-55.94:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=27e9443b-f477-40c7-b543-282e6a516ecc InstallationDate: Installed on 2013-02-09 (2651 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: TOSHIBA Satellite L305 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic root=UUID=0946b065-28e5-49f1-bcca-563f551acbbd 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-9ubuntu1.17 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2014-04-19 (2217 days ago) dmi.bios.date: 09/23/2009 dmi.bios.vendor: INSYDE dmi.bios.version: 2.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.10:bd09/23/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-13T038:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite L305 dmi.product.version: PSLB8U-13T038 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
Hi,
I have installed ubuntu 20.04.1 LTS and have as kernel 5.10.7 and the
ath11 enabled. I am unable to get the wifi working on my xps 15 9500.
The bluetooth works.
If I do `dmesg`, then this is the output.
[49521.913254] r8152 4-2.4:1.0 enx74782787c3d0: carrier off
[49523.487603] ath11k_pci :6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[49523.487605] ath11k_pci :6c:00.0: failed to enable PMF QOS: (-108
[49523.487740] ath11k_pci :6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[49523.487741] ath11k_pci :6c:00.0: failed to enable PMF QOS: (-108
[49531.193591] r8152 4-2.4:1.0 enx74782787c3d0: carrier on
[49533.489875] ath11k_pci :6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[49533.489882] ath11k_pci :6c:00.0: failed to enable PMF QOS: (-108
[49533.490367] ath11k_pci :6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[49533.490373] ath11k_pci :6c:00.0: failed to enable PMF QOS: (-108
[49543.492600] ath11k_pci :6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[49543.492607] ath11k_pci :6c:00.0: failed to enable PMF QOS: (-108
[49543.493167] ath11k_pci :6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[49543.493175] ath11k_pci :6c:00.0: failed to enable PMF QOS: (-108
[49553.496286] ath11k_pci :6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[49553.496294] ath11k_pci :6c:00.0: failed to enable PMF QOS: (-108
[49553.496776] ath11k_pci :6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[49553.496781] ath11k_pci :6c:00.0: failed to enable PMF QOS: (-108
Is there something I can do to get this working?
Kind regards,
** Attachment added: "dmicode"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879633/+attachment/5454047/+files/dmicode.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1879633
Title:
Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-firmware source package in Focal:
Fix Released
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-firmware source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification: oem-5.6]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k and all
its prerequisite drivers.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
[Fix]
Tag ath11k-qca6390-bringup-202011301608 from ath tree
(https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks
first stable milestone on the platform/device under development since
v5.6-rc1. Most of the commits under this tag, ~350 commits, have been
in vanilla kernel v5.10-rc4 except those starting from commit
065c9528cc50 ("ath11k: add 64bit check before reading msi high addr").
While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling
in these components are also pulled.
Besides, tx encapsulation
https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/
and a couple more inclusive of 6 GHz capability, BSS Color were also
pulled to satisfy API changes in mac80211/cfg80211.
[Test Case]
1. Install firmwares & boot from patched kernel,
2. ath11k should be now up and running. Check with
`sudo dmesg | grep ath11k`
While this is going to bring massive changes to the kernel, as well as
shared wireless stack that is not only used by ath11k but also many
others, prebuilt kernel/firmware packages were deployed on platforms
with and without ath11k for regression tests, and so far the results are
positive.
[Where problems could occur]
ath11k and its relying parts have never been enabled in oem-5.6, so
changes to them should have little effect on most platforms. For
platforms equip QCA6390, this will be the first time they're probed and
enabled, and as the driver is still under polishing, there can be
regressions, performance lost, power consumption increase at this
moment.
Changes to wireless stack could also be an issue as this introduces
interface changes to the API, so maybe DKMS packages in the wild will be
affected.
== SRU for U/OEM-5.10 ==
[SRU Justification: U/OEM-5.10]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k
driver.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device
[Kernel-packages] [Bug 1909705] Re: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend
This bug was fixed in the package linux-firmware - 1.190.3 --- linux-firmware (1.190.3) groovy; urgency=medium * Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend (LP: #1909705) - rtl_bt: Update RTL8821C BT(USB I/F) FW to 0x829a_7644 -- Seth Forshee Thu, 07 Jan 2021 09:40:21 -0600 ** Changed in: linux-firmware (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1909705 Title: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] Connected BLE devices like keyboard and mouse won't automatically reconnect to host after system suspend. [Fix] New firmware from Realtek. [Test] With the new firmware used, BLE keyboard and mouse will reconnect to host by pressing any key or by moving it. [Where problems could occur] Tried some other Bluetooth peripherals and didn't see any regression. This is also internally tested by Realtek. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910995] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
thank you Rakhmanov its working on my laptop model HP ProBook 6570b! -- 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/1910995 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: after update the packages and reboot my computer, the wifi do not work any more. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-34-generic Date: Thu Jan 7 06:11:05 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-09-18 (114 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: 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/1910995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906907] Re: [Toshiba Satellite C55t-A] Laptop unable to wake up after being suspended
** Summary changed: - Laptop unable to wake up after being suspended + [Toshiba Satellite C55t-A] Laptop unable to wake up after being suspended -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906907 Title: [Toshiba Satellite C55t-A] Laptop unable to wake up after being suspended Status in linux package in Ubuntu: Incomplete Bug description: Laptop was unable to wake up after being suspended by lid's closing, resulting in a blank black screen, while LEDs on the laptop showed that it had woken up. This bug happened using kernel 5.4.0-56.62, and it was "solved" by changing the kernel used to version 5.4.0-54.60, in which the default behavior of suspension when lid was closed and lock/login screen after lid being lifted up ocurred as it always was. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rafael 1700 F pulseaudio /dev/snd/controlC1: rafael 1700 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 5 02:35:57 2020 InstallationDate: Installed on 2020-10-09 (57 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: TOSHIBA Satellite C55t-A ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=9b883e7b-5549-4c98-8084-ff648bf6066e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd04/28/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Durban-Curiosity 10S/10SG dmi.product.name: Satellite C55t-A dmi.product.sku: PSCFJU dmi.product.version: PSCFJU-00T00J dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907991] Re: Touchpad not working dynabook PORTEGE-X30L-G-10J
Marked as Incomplete as per comment #30 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907991 Title: Touchpad not working dynabook PORTEGE-X30L-G-10J Status in linux package in Ubuntu: Incomplete Bug description: This may be related to bug #1903858 “Synaptics Touchpad not working dynabook TECRA A40-G”. Release: Kubuntu 20.10 freshly out of the box. (The same problem observed with live versions of Ubuntu 20.04.) xserver-xorg-input-libinput: Installed: 0.30.0-1 Candidate: 0.30.0-1 Version table: *** 0.30.0-1 500 500 http://gb.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status Problem: Touchpad _almost_ does not work at all. The cursor moves a little from time to time, and reacts to buttons from time to time, in an indeterminate manner. There is no problem under Windows – touchpad works perfectly well there. Not sure this problem is specific to libinput. Tried replacing it with synaptics (as described here: https://askubuntu.com/questions/1088559/ubuntu-18-04-switch-back-to- synaptics-as-input-driver) and the problem persisted. Attaching various files suggested by https://wiki.ubuntu.com/DebuggingTouchpadDetection. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adamp 1180 F pulseaudio adamp 1197 F pipewire-media- /dev/snd/seq:adamp 1179 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-12-12 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dynabook Inc. dynabook PORTEGE X30L-G Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-33-generic N/A linux-backports-modules-5.8.0-33-generic N/A linux-firmware1.190.2 Tags: groovy Uname: Linux 5.8.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2020 dmi.bios.release: 3.50 dmi.bios.vendor: Dynabook Inc. dmi.bios.version: Version 3.50 dmi.board.asset.tag: 00 dmi.board.name: A0104/ dmi.board.vendor: Dynabook Inc. dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: Dynabook Inc. dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnDynabookInc.:bvrVersion3.50:bd10/27/2020:br3.50:efr1.80:svnDynabookInc.:pndynabookPORTEGEX30L-G:pvrPUZ20E-00S007EN:rvnDynabookInc.:rnA0104/:rvrVersionA0:cvnDynabookInc.:ct10:cvrVersion1.0: dmi.product.family: dynabook PORTEGE dmi.product.name: dynabook PORTEGE X30L-G dmi.product.sku: PUZ20E dmi.product.version: PUZ20E-00S007EN dmi.sys.vendor: Dynabook Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912056] Re: [Toshiba Satellite P750] Touch Pad doesnt work after update to Ubuntu 18.04.5 LTS
** Summary changed: - Touch Pad doesnt work after update to Ubuntu 18.04.5 LTS + [Toshiba Satellite P750] Touch Pad doesnt work after update to Ubuntu 18.04.5 LTS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912056 Title: [Toshiba Satellite P750] Touch Pad doesnt work after update to Ubuntu 18.04.5 LTS Status in linux package in Ubuntu: Confirmed Bug description: Touch pad of Laptop does not work after upate to version :Ubuntu 18.04.5 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-121-generic 4.15.0-121.123 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kiran 1553 F pulseaudio /dev/snd/controlC0: kiran 1553 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 19:13:19 2021 InstallationDate: Installed on 2017-11-04 (1168 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA Satellite P750 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-121-generic root=UUID=1a3e664e-3ef9-4a3a-99e2-e4733086ce66 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-121-generic N/A linux-backports-modules-4.15.0-121-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2020-10-24 (83 days ago) dmi.bios.date: 12/15/2011 dmi.bios.vendor: TOSHIBA dmi.bios.version: 2.40 dmi.board.asset.tag: NULL dmi.board.name: PEQAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr2.40:bd12/15/2011:svnTOSHIBA:pnSatelliteP750:pvrPSAY3A-02T001:rvnTOSHIBA:rnPEQAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite P750 dmi.product.version: PSAY3A-02T001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
hello,How about the issue now? Does it reproduce with the kernel version "5.3.0.45.101"? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in linux package in Ubuntu: Expired Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908366] Re: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin
This bug was fixed in the package linux-firmware - 1.187.8 --- linux-firmware (1.187.8) focal; urgency=medium * Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin (LP: #1908366) - i915: Add DMC firmware 2.08 for TGL * Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend (LP: #1909705) - rtl_bt: Update RTL8821C BT(USB I/F) FW to 0x829a_7644 -- Seth Forshee Thu, 07 Jan 2021 09:52:55 -0600 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1908366 Title: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] It shows the firmware is missing, and runtime power management has been disabled. [ 1.884400] i915 :00:02.0: vgaarb: deactivate vga console [ 1.887078] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.887161] i915 :00:02.0: Direct firmware load for i915/tgl_dmc_ver2_08.bin failed with error -2 [ 1.887164] i915 :00:02.0: [drm] Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin. Disabling runtime power management. [ 1.887165] i915 :00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 [Fix] cherry picked from linux-firmware bdf8d7a8 i915: Add DMC firmware 2.08 for TGL BTW, groovy has this commit already. [Test] Verified on Dell's machine [Where problems could occur] It's a new firmware for new GPU, not possible to introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908366] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1908366 Title: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] It shows the firmware is missing, and runtime power management has been disabled. [ 1.884400] i915 :00:02.0: vgaarb: deactivate vga console [ 1.887078] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.887161] i915 :00:02.0: Direct firmware load for i915/tgl_dmc_ver2_08.bin failed with error -2 [ 1.887164] i915 :00:02.0: [drm] Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin. Disabling runtime power management. [ 1.887165] i915 :00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 [Fix] cherry picked from linux-firmware bdf8d7a8 i915: Add DMC firmware 2.08 for TGL BTW, groovy has this commit already. [Test] Verified on Dell's machine [Where problems could occur] It's a new firmware for new GPU, not possible to introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909705] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1909705 Title: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] Connected BLE devices like keyboard and mouse won't automatically reconnect to host after system suspend. [Fix] New firmware from Realtek. [Test] With the new firmware used, BLE keyboard and mouse will reconnect to host by pressing any key or by moving it. [Where problems could occur] Tried some other Bluetooth peripherals and didn't see any regression. This is also internally tested by Realtek. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909705] Re: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend
This bug was fixed in the package linux-firmware - 1.187.8 --- linux-firmware (1.187.8) focal; urgency=medium * Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin (LP: #1908366) - i915: Add DMC firmware 2.08 for TGL * Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend (LP: #1909705) - rtl_bt: Update RTL8821C BT(USB I/F) FW to 0x829a_7644 -- Seth Forshee Thu, 07 Jan 2021 09:52:55 -0600 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1909705 Title: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] Connected BLE devices like keyboard and mouse won't automatically reconnect to host after system suspend. [Fix] New firmware from Realtek. [Test] With the new firmware used, BLE keyboard and mouse will reconnect to host by pressing any key or by moving it. [Where problems could occur] Tried some other Bluetooth peripherals and didn't see any regression. This is also internally tested by Realtek. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911456] Re: Can't receive files over bluetooth unless settings dialog is open
I'm not sure if this is a bug or a security feature. You might be able to keep it enabled in the 'bluetoothctl' tool. Or try something like 'bt-obex -s'. ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1911456 Title: Can't receive files over bluetooth unless settings dialog is open Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: On 18.04 I could send files from my phone to my laptop at any time. On 20.04 I can't get files to be accepted by the laptop over bluetooth. After much frustration and experimenting, I figured out that it will work, but only if the bluetooth settings dialog is open. If the settings dialog is not open, the incoming file is rejected. If the dialog is closed after the file transfer begins, the transfer continues but the file is discarded when the transfer is complete. This is very frustrating. I need to be able to send files (mostly photos and videos) from my phone to my laptop without having to open the settings dialog on the laptop, just like I could before upgrading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1911456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894017] Re: Keyboard not working
And somehow my windows is behaving in the same way as well. Oh, and another thing, there is stream of b's (bbb) being generated on both OS on my Latop. Any help, would be great -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894017] Re: Keyboard not working
I just received an patch yesterday on Live patch for Ubuntu 20.04.1, the kernel version in my Laptop is 5.8.0-38-generic, but still I am having this same bug from Ubuntu. Did try blacklisting intel_vbtn "sudoedit /etc/modprobe.d/blacklist-intel_vbtn.conf" but the bug continues on my Dell Inspiron 15 5558. This "cat /sys/class/dmi/id/chassis_type" give me a number: 9. Is there anyother fix? and any potential dates the patch for the same is 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911219] Re: [nouveau] Xorg freeze
Thanks but unfortunately that did not help. Next please try all of these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911219 Title: [nouveau] Xorg freeze Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Also freezes when trying to open Libre Office new documents Not sure if it is the video that is causing issues Mouse and keyboard seems to be frozen and cant do anything without a hard reboot Some times the video keeps playing even if everything is frozen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 11:29:12 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1212] InstallationDate: Installed on 2021-01-09 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=598990d0-29d6-4e5b-a8aa-3c75c00bd284 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-970A-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912147] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1912147 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912147 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 at Kernel 5.4 LTS Status in linux package in Ubuntu: Incomplete Bug description: Same issue was supposed to be fixed but now it happens still in 5.4.0-60 and 5.4.0-62 kernel This is the original bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846148 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912147] [NEW] Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 at Kernel 5.4 LTS
Public bug reported: Same issue was supposed to be fixed but now it happens still in 5.4.0-60 and 5.4.0-62 kernel This is the original bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846148 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912147 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 at Kernel 5.4 LTS Status in linux package in Ubuntu: Incomplete Bug description: Same issue was supposed to be fixed but now it happens still in 5.4.0-60 and 5.4.0-62 kernel This is the original bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846148 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910894] Re: Wireless worked in 5.0.0-37-generic doesn't work in 18.04 LTS
** Summary changed: - Wireless worked in 5.0.0-37-generic doesn't work in 5.4 LTS + Wireless worked in 5.0.0-37-generic doesn't work in 18.04 LTS ** Summary changed: - Wireless worked in 5.0.0-37-generic doesn't work in 18.04 LTS + Wireless worked in 5.0.0-37-generic doesn't work in 5.4 LTS ** Summary changed: - Wireless worked in 5.0.0-37-generic doesn't work in 5.4 LTS + Wireless worked in "linux-image-unsigned-5.0.0-37-generic 5.0.0-37.41+redmiv3" doesn't work in 5.4 kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910894 Title: Wireless worked in "linux-image-unsigned-5.0.0-37-generic 5.0.0-37.41+redmiv3" doesn't work in 5.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: run apt update && apt upgrade. after that booted with kernerl 5.4 LTS Wireless connection keep on asking for password or encryption keys for wi-fi which are already linked properly with 5.0.0-37-generic. Laptop: Redmi Book 14 2019 lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 uname -r 5.0.0-37-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
*** This bug is a duplicate of bug 1910709 *** https://bugs.launchpad.net/bugs/1910709 ** This bug has been marked a duplicate of bug 1910709 DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: Confirmed Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN
[Kernel-packages] [Bug 1873052] Re: Showing two cursors after login
** Tags added: amdgpu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
focal-proposed is not expected to help with this bug. The fix I mentioned in comment #57 is in future mutter version 40. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910561] Re: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation
Verified comment#5 on HP Fury machine. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910561 Title: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Mute and micmute LED are not work accurately on HP ZBook Fury 15/17 G7 Mobile Workstation when muting corresponding audio devices. * The right channel of internal speaker has not sound. [Fix] Apply ALC285_FIXUP_HP_GPIO_AMP_INIT quirk to expose GPIOs for controlling LEDs and initialing AMP. [Test] Built a test kernel with applying this patch, the mute/micmute LEDs are work as expected. The internal speaker could play the sounds from left and right channels. [Where problems could occur] This quirk is specific for these two platforms. It should not cause the regression to other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1910561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it
To change parameters you need to: 1. Edit /etc/default/grub as root, and change the GRUB_CMDLINE_LINUX_DEFAULT line. 2. Run: sudo update-grub 3. Reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it Status in linux package in Ubuntu: Confirmed Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
Diego, please open a new bug by running: ubuntu-bug linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
Can you please attach full dmesg? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1912033] Re: Thinkpad - add palm sensor support needed for WWAN
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) 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/1912033 Title: Thinkpad - add palm sensor support needed for WWAN Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: New Bug description: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems [Fix] thinkpad_acpi is updated to check palm sensor presence and its events [Test] Tested on Thinkpad systems [Where problems could occur] Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" Note: On some platforms, because of an issue in the HW implementation, the palm sensor presence may be incorrectly advertised as always enabled even if a palm sensor is not present. The palm sensor is intended for WWAN transmission power control and should be available and correct on all WWAN enabled systems. It is not recommended to use this interface for other use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910102] Re: Enable mute and micmute LED on HP EliteBook 850 G7
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910102 Title: Enable mute and micmute LED on HP EliteBook 850 G7 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Bug description: [Impact] Mute and micmute LED on HP EliteBook 850 G7 don't reflect the mute status. [Fix] Apply an HDA quirk to let HP EliteBook 850 G7 use codec GPIO to control LED. [Test] With the patch applied, both mute and micmute LED can be lit when audio output or input is muted, respectively. [Where problems could occur] This quirk is specific to one model. It's not likely to regress other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1910102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
This issue seems to have appeared somewhere between zfs-linux 0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16. When the issue first hit, I had zfs-dkms installed, which was on 0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed zfs-dkms to go back to the kernel built version and it was working OK. linux-image-5.8.0-36-generic is now released on Hirsute with 0.8.4-1ubuntu16 and so now the out of the box kernel is also broken and I am regularly having problems with this. linux-image-5.8.0-29-generic: working linux-image-5.8.0-36-generic: broken ` lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo /lib/modules/5.8.0-29-generic/kernel/zfs/zfs.ko|grep version version: 0.8.4-1ubuntu11 lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo /lib/modules/5.8.0-36-generic/kernel/zfs/zfs.ko|grep version version: 0.8.4-1ubuntu16 ` I don't have a good quick/easy reproducer but just using my desktop for a day or two seems I am likely to hit the issue after a while. I tried to install the upstream zfs-dkms package for 2.0 to see if I can bisect the issue on upstream versions but it breaks my boot for some weird systemd reason I cannot quite figure out as yet. Looking at the Ubuntu changelog I'd say the fix for https://bugs.launchpad.net/bugs/1899826 that landed in 0.8.4-1ubuntu13 to backport the 5.9 and 5.10 compataibility patches is a prime suspect but could also be any other version. I'm going to try and 'bisect' 0.8.4-1ubuntu11 through 0.8.4-1ubuntu16 to figure out which version actually hit it. Since the default kernel is now hitting this, there have been 2 more user reports of the same things in the upstream bug in the past few days since that kernel landed and I am regularly getting inaccessible files not just from chrome but even a linux git tree among other things I am going to raise the priority on this bug to Critical as you lose access to files so has data loss potential. I have not yet determined if you can somehow get the data back, so far it's only affected files I can replace such as cache/git files. It seems like snapshots might be OK (which would make sense). ** Changed in: zfs-linux (Ubuntu) Importance: High => Critical -- 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in zfs-linux package in Ubuntu: Confirmed Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30
[Kernel-packages] [Bug 1899826] Re: backport upstream fixes for 5.9 Linux support
This issue seems to have appeared somewhere between zfs-linux
0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.
When the issue first hit, I had zfs-dkms installed, which was on
0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed
zfs-dkms to go back to the kernel built version and it was working OK.
linux-image-5.8.0-36-generic is now released on Hirsute with
0.8.4-1ubuntu16 and so now the out of the box kernel is also broken, and
I am regularly having problems with this.
linux-image-5.8.0-29-generic: working
linux-image-5.8.0-36-generic: broken
`
lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo
/lib/modules/5.8.0-29-generic/kernel/zfs/zfs.ko|grep version
version: 0.8.4-1ubuntu11
lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo
/lib/modules/5.8.0-36-generic/kernel/zfs/zfs.ko|grep version
version: 0.8.4-1ubuntu16
`
I don't have a good quick/easy reproducer but just using my desktop for
a day or two seems I am likely to hit the issue after a while.
I tried to install the upstream zfs-dkms package for 2.0 to see if I can
bisect the issue on upstream versions but it breaks my boot for some
reason I cannot quite figure out.
Looking at the Ubuntu changelog I'd say the fix for
https://bugs.launchpad.net/bugs/1899826 that landed in 0.8.4-1ubuntu13
to backport the 5.9 and 5.10 compataibility patches is a prime suspect
but could also be any other version. I'm going to try and 'bisect'
0.8.4-1ubuntu11 through 0.8.4-1ubuntu16 to figure out which version
actually hit it.
Since the default kernel is now hitting this, there have been 2 more
user reports of the same things in the upstream bug in the past few days
since that kernel landed, and I am regularly getting inaccessible files
not just from chrome but even a linux git tree among other things I am
going to raise the priority on this bug to Critical as you lose access
to files so has data loss potential. I have not yet determined if you
can somehow get the data back, so far it's only affected files I can
replace such as cache/git files. It seems like snapshots might be OK
(which would make sense).
--
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/1899826
Title:
backport upstream fixes for 5.9 Linux support
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Groovy:
Confirmed
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
== SRU Request Groovy ==
Upstream zfs supports 5.9. it would be useful to backport these for
users who want newer kernels.
== The Fix ==
Although 6 fixes are required, 2 add changes that get removed by a
later change, so one can backport this with just the following 4
changes:
1823c8fe6a4a20971463e9b51615dad412aea9a9 ("Linux 5.9 compat: add
linux/blkdev.h include")
3e29e1971bbb4ab63dafeb592b747ef56bad3534 ("Linux 5.9 compat:
NR_SLAB_RECLAIMABLE")
d817c17100183b266aa6bf8b868e016805d51d16 ("Linux 5.9 compat: make_request_fn
replaced with submit_bio")
4b59c195ffbaebfdd5f0971a54613c0ed7c42005 ("Increase Supported Linux Kernel to
5.9")
== Regression potential ==
The first patch just includes blkdev.h to workaround a build warning,
so the results in no functional change to the working code.
The second patch removes legacy arc page free estimation by droping
the accounting for inactive anonymous pages and reclaimable pages on
the slab. This change removes a very minor component of the free
memory calculation and speeds up arc free stats calculations. There is
a potential that this small change in free page calculation may impact
systems where memory is more constrained, but the change is so small I
believe this really is insignificant.
The third patch is a build time detection of the kernel block
allocation queue due to API changes, so should not change behaviour
for current 5.8 kernels, only change behaviour for newer kernels with
the newer kernel API. Hence for the released 5.8 groovy kernel the
code will not be changed, so the regression potential for 5.8 is zero.
The final patch changes the META build data to allow the driver to
build on newer kernels, so the risk on this change is effectively
zero.
== Testing ==
Run the autotest client tests for ZFS tests:
ubuntu_zfs_smoke_tests (general functionality smoke tests)
ubuntu_zfs_fstests (file system semantics tests)
ubuntu_zfs_xfs_generic (subset of XFS tests on ZFS)
ubuntu_zfs_stress (stress-ng file system tests on a wide range of ZFS mount
options)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1899826/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1899826] Re: backport upstream fixes for 5.9 Linux support
Accidentally posted the above comment in the wrong bug, sorry, was meant
for https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476 -
where I suspect this bug as having caused a regression.
--
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/1899826
Title:
backport upstream fixes for 5.9 Linux support
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Groovy:
Confirmed
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
== SRU Request Groovy ==
Upstream zfs supports 5.9. it would be useful to backport these for
users who want newer kernels.
== The Fix ==
Although 6 fixes are required, 2 add changes that get removed by a
later change, so one can backport this with just the following 4
changes:
1823c8fe6a4a20971463e9b51615dad412aea9a9 ("Linux 5.9 compat: add
linux/blkdev.h include")
3e29e1971bbb4ab63dafeb592b747ef56bad3534 ("Linux 5.9 compat:
NR_SLAB_RECLAIMABLE")
d817c17100183b266aa6bf8b868e016805d51d16 ("Linux 5.9 compat: make_request_fn
replaced with submit_bio")
4b59c195ffbaebfdd5f0971a54613c0ed7c42005 ("Increase Supported Linux Kernel to
5.9")
== Regression potential ==
The first patch just includes blkdev.h to workaround a build warning,
so the results in no functional change to the working code.
The second patch removes legacy arc page free estimation by droping
the accounting for inactive anonymous pages and reclaimable pages on
the slab. This change removes a very minor component of the free
memory calculation and speeds up arc free stats calculations. There is
a potential that this small change in free page calculation may impact
systems where memory is more constrained, but the change is so small I
believe this really is insignificant.
The third patch is a build time detection of the kernel block
allocation queue due to API changes, so should not change behaviour
for current 5.8 kernels, only change behaviour for newer kernels with
the newer kernel API. Hence for the released 5.8 groovy kernel the
code will not be changed, so the regression potential for 5.8 is zero.
The final patch changes the META build data to allow the driver to
build on newer kernels, so the risk on this change is effectively
zero.
== Testing ==
Run the autotest client tests for ZFS tests:
ubuntu_zfs_smoke_tests (general functionality smoke tests)
ubuntu_zfs_fstests (file system semantics tests)
ubuntu_zfs_xfs_generic (subset of XFS tests on ZFS)
ubuntu_zfs_stress (stress-ng file system tests on a wide range of ZFS mount
options)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1899826/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903596] Re: stack trace in kernel
** Changed in: linux (Ubuntu Hirsute)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1903596
Title:
stack trace in kernel
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Bug description:
== SRU Justification ==
Whenever a buggy NAPI driver returns more than its budget, it will
trigger a stack trace warning with:
WARN_ON_ONCE(work > weight);
The warning message looks like this :
WARNING: CPU: 2 PID: 0 at
/build/linux-hwe-ymdo11/linux-hwe-4.15.0/net/core/dev.c:5672
net_rx_action+0x276/0x3b0
This is not very useful for debugging purpose, since it does not tell
you what's going on there.
== Fix ==
* 427d5838e996 ("net: napi: remove useless stack trace")
This patch will emit a message giving the function name, and a
descriptive message like:
NAPI poll function ath10k_pci_napi_poll+0x0/0x120 [ath10k_pci] returned
0, exceeding its budget of 64.
This patch is a clean-cherry for all the releases except Xenial.
For Xenial it will need to be applied with -C1
== Test ==
Test kernels can be found here:
https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon/
Please note that even though I tried to reproduce this on a XPS 13
9360 mentioned in this bug report that shipped with Atheros QCA6174
[168c:003e] wireless card, but I can't trigger this warning message.
The bug opener is also unable to test this due to some other reasons.
Howeve I did tried to trigger this warning forcibly by putting it
outside the if statement with the test kernels in the following link
to make sure it won't cause some other problem.
https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon
/force-to-warn/
== Where problems could occur ==
For this bug itself, this patch does not really solve the problem
but it will provide more debug information for developers in the
future (and since this is just a warning message, it should be fine).
We can expect to see more a detailed report against ath10k driver
in the future on launchpad.
== Original Bug Report ==
This appears to be a problem in the ath10k module. I am not sure what it is
exactly.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-122-generic 4.15.0-122.124~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.26
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 9 13:35:54 2020
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2020-11-09 (0 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
20160624-10:47
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903596/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454024/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454023/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454016/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454022/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454018/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454009/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454021/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454015/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454013/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454017/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454020/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454019/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454010/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454014/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454012/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454008/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454007/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454011/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] Re: No sound on Dell Latitude E6420 with Kernel 5.8.0
apport information ** Tags added: apport-collected focal ** Description changed: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: christerw 1637 F pipewire-media- + /dev/snd/seq:christerw 1629 F pipewire + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Feren OS 20.04 + InstallationDate: Installed on 2020-03-06 (317 days ago) + InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) + MachineType: Dell Inc. Latitude E6420 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-38-generic N/A + linux-backports-modules-5.8.0-38-generic N/A + linux-firmware1.187.7 + Tags: focal + Uname: Linux 5.8.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sudo + _MarkForUpload: True + dmi.bios.date: 10/18/2011 + dmi.bios.release: 4.6 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A08 + dmi.board.name: 0K0DNP + dmi.board.vendor: Dell Inc. + dmi.board.version: A02 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E6420 + dmi.product.version: 01 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1912037/+attachment/5454006/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop
Hello Tom,
It will be great if you can help out to verify this.
To do so for Xenial, you will need to install Ubuntu Xenial and enable
the "proposed" pocket [1] on it, then dist-upgrade to the latest kernel
and reboot to see if it works.
The same applies to other releases, you can verify the version that you can.
Thanks!
[1] https://wiki.ubuntu.com/Testing/EnableProposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906128
Title:
Touchpad not detected on ByteSpeed C15B laptop
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
Touchpad on a ByteSpeed C15B laptop is not working.
User will need to add i8042.noloop=1 to boot options to make it work.
[Fix]
* a48491c65b513e ("Input: i8042 - add ByteSpeed touchpad to noloop table")
This fix can be cherry-picked into all affected releases.
[Test Case]
Test kernel for Bionic / Focal can be found here:
https://people.canonical.com/~phlin/kernel/lp-1906128-C15B/
And they have been tested with positive test results.
[Where problems could occur]
The fix is just a small and simple hardware quirk. I can't think of any
potential problem for now.
== Original Bug Report ==
Touchpad hardware is OK and works for Win10. Not working for live disc, not
for 18.04 and not for 20.04 after upgrading. I've attached a Logitech wireless
mouse with its USB adapter and that works. Bluetooth is also missing, but I
have not started trying to skull that out. I'm happy to help try debugging
things, and to help resolve the issue.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tom1395 F pulseaudio
/dev/snd/controlC0: tom1395 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 28 19:09:05 2020
InstallationDate: Installed on 2020-01-26 (307 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: ByteSpeed LLC ByteSpeed Laptop C15B
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic
root=UUID=07b919ee-c6ad-41a5-9c64-df3c8e477b6f ro quiet splash i8042.reset
i8042.nomux i8042.nopnp i8042noloop noapic vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-54-generic N/A
linux-backports-modules-5.4.0-54-generic N/A
linux-firmware1.187.4
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-11-25 (3 days ago)
dmi.bios.date: 03/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C15B.616
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: C15B
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ByteSpeed LLC
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrC15B.616:bd03/18/2014:svnByteSpeedLLC:pnByteSpeedLaptopC15B:pvr1.0:rvnPEGATRONCORPORATION:rnC15B:rvr1.0:cvnByteSpeedLLC:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: ByteSpeed Laptop C15B
dmi.product.sku: 0
dmi.product.version: 1.0
dmi.sys.vendor: ByteSpeed LLC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
Thanks joaorami (joaomppr)! I've tried your solution and is working fine for BCM4312 on Ubuntu 20.04 with kernel 5.8.0-38 -- 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/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
Upgrading to nvidia-opencl-icd-340:amd64 (340.108-0ubuntu2, 340.108-0ubuntu5.20.04.1) from focal-proposed solves this problem. See bug #1910709. I came to this conclusion after testing the focal-daily (20210116) and finding that nvidia-340 installed just fine. Since LTS daily builds always have the proposed repos enabled it was just a matter of parsing what packages were available in proposed. Probably OK to mark this fix released but I'll leave that decision up to one of the devs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: Confirmed Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No
[Kernel-packages] [Bug 1910995] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
Confirmed on Lenovo laptop -- 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/1910995 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: after update the packages and reboot my computer, the wifi do not work any more. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-34-generic Date: Thu Jan 7 06:11:05 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-09-18 (114 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: 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/1910995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
Cher, ZdravkoG (zdravko-g). Merci beaucoup! Avant de lire ceci j'ai réinstaller Ubuntu 4 fois. :) Mais avec les conseilles prodiguée par toi , je peux de nouveau me connecter sur mon réseau Wifi. Un Grand merci. Дорогой,ZdravkoG (zdravko-g). Большое спасибо! Перед тем, как прочитать это, я переустанавливал Убунту 4 раза. :) Но, по вашему совету, я могу снова подключиться к своей Wi-Fi сети. Большое спасибо. -- 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/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 Status in bcmwl package in Ubuntu: Confirmed Bug description: Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi doesn't work anymore. After a try rebuild (reconfigure) the result is: --- # dpkg-reconfigure bcmwl-kernel-source Removing all DKMS Modules Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-59-generic 5.8.0-34-generic Building for architecture x86_64 Building initial module for 5.4.0-59-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. --- As could be seen, the build for 5.4 completes successfully (and works on same kernel), but for 5.8 fails. Seems something is going wrong with missing function declaration - function "ioremap_nocache", as could be seen in attached make.log. I'm guessing, driver code may need be updated according to the new kernel headers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 17:13:05 2021 InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1910555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912094] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912094 Title: touchpad not showing up and not working Status in linux package in Ubuntu: Confirmed Bug description: Hi, touchpad does not seem to be recognised at all and thus does not work, can you please help, thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leo1595 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 17 13:16:20 2021 InstallationDate: Installed on 2020-12-14 (33 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=0a29a516-0bd9-45c7-ab20-165d3b5a1d0e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912094] [NEW] touchpad not showing up and not working
Public bug reported: Hi, touchpad does not seem to be recognised at all and thus does not work, can you please help, thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leo1595 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 17 13:16:20 2021 InstallationDate: Installed on 2020-12-14 (33 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=0a29a516-0bd9-45c7-ab20-165d3b5a1d0e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912094 Title: touchpad not showing up and not working Status in linux package in Ubuntu: Confirmed Bug description: Hi, touchpad does not seem to be recognised at all and thus does not work, can you please help, thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leo1595 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 17 13:16:20 2021 InstallationDate: Installed on 2020-12-14 (33 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=0a29a516-0bd9-45c7-ab20-165d3b5a1d0e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
Hi I am getting Failed to send firmware data (-38), even after cool boot diego@lfb-Desktop:~$ dmesg | grep -i bluetooth [5.985839] Bluetooth: Core ver 2.22 [5.985858] Bluetooth: HCI device and connection manager initialized [5.985864] Bluetooth: HCI socket layer initialized [5.985867] Bluetooth: L2CAP socket layer initialized [5.985872] Bluetooth: SCO socket layer initialized [6.132508] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [6.138629] Bluetooth: hci0: Device revision is 5 [6.138631] Bluetooth: hci0: Secure boot is enabled [6.138631] Bluetooth: hci0: OTP lock is enabled [6.138632] Bluetooth: hci0: API lock is enabled [6.138632] Bluetooth: hci0: Debug lock is disabled [6.138633] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [6.183029] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [6.206658] Bluetooth: hci0: Failed to send firmware data (-38) [6.206731] Bluetooth: hci0: Intel reset sent to retry FW download [8.736500] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [8.736503] Bluetooth: BNEP filters: protocol multicast [8.736512] Bluetooth: BNEP socket layer initialized diego@lfb-Desktop:~$ dpkg --status bluez | grep '^Version:' Version: 5.53-0ubuntu3 diego@lfb-Desktop:~$ lspci -knn | grep Net -A3;lsusb 02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Kernel driver in use: iwlwifi Kernel modules: iwlwifi Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 8087:0a2b Intel Corp. Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 03f0:7d11 HP, Inc Photosmart Premium C309g-m Bus 001 Device 002: ID 045e:0761 Microsoft Corp. LifeCam VX-2000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 003: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4G Mouse Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 014 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 013 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following:
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
Hi, can someone help... Cold boot is not working for me I am getting Failed to send firmware data (-38) $ dmesg | grep -i bluetooth [5.985839] Bluetooth: Core ver 2.22 [5.985858] Bluetooth: HCI device and connection manager initialized [5.985864] Bluetooth: HCI socket layer initialized [5.985867] Bluetooth: L2CAP socket layer initialized [5.985872] Bluetooth: SCO socket layer initialized [6.132508] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [6.138629] Bluetooth: hci0: Device revision is 5 [6.138631] Bluetooth: hci0: Secure boot is enabled [6.138631] Bluetooth: hci0: OTP lock is enabled [6.138632] Bluetooth: hci0: API lock is enabled [6.138632] Bluetooth: hci0: Debug lock is disabled [6.138633] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [6.183029] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [6.206658] Bluetooth: hci0: Failed to send firmware data (-38) [6.206731] Bluetooth: hci0: Intel reset sent to retry FW download [8.736500] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [8.736503] Bluetooth: BNEP filters: protocol multicast [8.736512] Bluetooth: BNEP socket layer initialized $ lspci -knn | grep Net -A3;lsusb 02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Kernel driver in use: iwlwifi Kernel modules: iwlwifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
sudo apt install broadcom-sta-dkms is enough. You don't need all 3 packages. -- 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/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
This thread has saved me from the 3 days nightmare. Thank you joaorami (joaomppr) -- 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/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** Tags added: verification-done-groovy verification-needed-focal
--
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/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Fix Committed
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
* Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
* The option is available on grub and will let you with a broken system,
partially cloned.
[Test Case]
* Boot on a system, using ZFS and ZSys.
* In grub, select "History" entry
* Select one of the "Revert" option: the system should boot after being
reverted with an older version.
[Where problems could occur]
* The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
* We replace dd with another way (more robust and simple) for generating
this ID.
-
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909457] Re: Support CML-S CPU + TGP PCH
@acelan, Hello, We also need this https://lkml.org/lkml/2021/1/14/1418 for the audio support. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909457 Title: Support CML-S CPU + TGP PCH Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] i915 driver gives below warnings that CML-S GPU doesn't work with TGL/RKL PCH, and the screen is blank. kernel: i915 :00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE)) [Fix] Intel provides us a new patch for this issue https://patchwork.freedesktop.org/patch/412664/ [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
