[Kernel-packages] [Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Just upgraded to -58 kernel and it broke my remote too. Going back to -42 kernel fixed it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading Status in linux package in Ubuntu: Confirmed Bug description: I run mythtv on Ubuntu 20.04 and I used a custom remote control keymap in /etc/rc_keymaps to correctly map buttons on my IR remote. The above kernel seems to break custom keymap loading for my remote (certain buttons no longer work in mythtv). Reverting to kernel 5.4.0-48 corrects the problem. Description: Ubuntu 20.04.1 LTS Release: 20.04 linux-image-5.4.0-52-generic: Installed: 5.4.0-52.57 Candidate: 5.4.0-52.57 Version table: *** 5.4.0-52.57 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status belongs to the linux source package ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pdaniel1552 F pulseaudio /dev/snd/controlC0: pdaniel1552 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 22 16:16:58 2020 InstallationDate: Installed on 2017-04-17 (1284 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: MSI MS-7792 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=38b7dfb0-9848-4919-890b-fdc027e936f1 ro radeon.dpm=0 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: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-11 (164 days ago) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FM2-A75IA-E53 (MS-7792) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd02/12/2015:svnMSI:pnMS-7792:pvr1.0:rvnMSI:rnFM2-A75IA-E53(MS-7792):rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7792 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
It looks like 5.6.0-1037.41 is on the PPA, is it worth trying that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 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-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
I'm already on linux-oem-5.6-headers-5.6.0-1036 with the issue still present. I recently upgraded to a Dell Ultrasharp 38" instead of my double configuration, and the same issue occurs with USB-C connection in this configuration. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 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-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900584] Re: Regression: suspend/wake-up no longer working properly
Alberto, this requires you :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1900584 Title: Regression: suspend/wake-up no longer working properly Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: With kernel 5.4.0-47.51, suspend (and resuming thereafter) works flawlessly. With 5.4.0-48.52 and later versions, the display refuses to wake up after a suspend. Display adaptor: Nvidia driver version: 440.100 Screens: 1 GPU: GeForce GT 710 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 1332 F pulseaudio /dev/snd/controlC0: craig 1332 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 20:15:38 2020 InstallationDate: Installed on 2020-09-04 (44 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enx582c80139263 no wireless extensions. lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=90130dae-9aab-4a03-9308-cf17561e3af2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 01TKCC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/24/2011:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn01TKCC:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893663] Re: touchpad not detected
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893663 Title: touchpad not detected Status in linux package in Ubuntu: Expired Bug description: Fujitsu Lifebook U7410 core7 10th generation (Model: 7U14A1) S26391-K502-V100 no information on the touchpad fresh install ubuntu 20.04LTS * touchpad is not detected * sudo lspci -vnvn > lspci-vnvn.log more lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c) Subsystem: Fujitsu Client Computing Limited Device [1e26:003f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Client Computing Limited UHD Graphics [1e26:004a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, NROPrPrP-, LTR- 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 cat /proc/version_signature > version.log more version.log Ubuntu 5.4.0-42.46-generic 5.4.44 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmadmin2348 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 16:22:12 2020 InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=4dadb030-fc54-4457-a7cd-6934b85d602c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2020 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2D4 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK
[Kernel-packages] [Bug 1907761] Re: vanishing kernel 5.4.0-56-generic
This link is what *should* have been easily discoverable for anyone wondering about the vanished version: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262 Ideas: * allow updating USNs even when no new binaries are available, simply because changelogs are *not* * add this possibility to the list of theories ubuntu-security-status (update-manager) helpfully explains when reporting unknown packages * make "DELETED" a more prominent feature on links from USNs (obvious: https://launchpad.net/ubuntu/+source/linux/5.4.0-56.62/+publishinghistory - not obvious: https://launchpad.net/ubuntu/+source/linux/5.4.0-56.62) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic Status in linux-meta package in Ubuntu: Incomplete Bug description: Kernel version 5.4.0-56-generic has just vanished off the face of the earth, after an update to that version some days ago. This was not updated from "proposed" or anything like that, it was updated in the normal way from "focal-updates". I had to revert several systems to kernel version 5.4.0-54-generic, after apt reported that my installed 5.4.0-56-generic packages were foreign, unknown and unaccounted-for. Have you lost your damn minds? By all means issue a fix for this outrageous situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc
Thanks, Marcelo! I tested all the 3 kernels and they worked as we expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1902531 Title: [linux-azure] IP forwarding issue in netvsc Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure-4.15 source package in Focal: Invalid Bug description: We identified an issue with the Linux netvsc driver when used in IP forwarding mode. The problem is that the RSS hash value is not propagated to the outgoing packet, and so such packets go out on channel 0. This produces an imbalance across outgoing channels, and a possible overload on the single host-side CPU that is processing channel 0. The problem does not occur when Accelerated Networking is used because the packets go out through the Mellanox driver. Because it is tied to IP forwarding, the problem is presumably most likely to be visible in a virtual appliance device that is doing network load balancing or other kinds of packet filtering and redirection. We would like to request fixes to this issue in 16.04, 18.04 and 20.04. Two fixes are already in the upstream v5.5+, so they’re already in 5.8.0-1011.11. For 5.4.0-1031.32, the 2 fixes can apply cleanly: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 5.0.0-1036.38, we need 1 more patch applied first, so the list is: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan backported them here: https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795 https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a (The 2 patches are on the branch https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850612] Re: Transition OEM & OSP1 kernel users to generic / hwe-5.4
This bug was fixed in the package linux-restricted-modules-hwe-5.4 - 5.4.0-58.64~18.04.1 --- linux-restricted-modules-hwe-5.4 (5.4.0-58.64~18.04.1) bionic; urgency=medium * Master version: 5.4.0-58.64~18.04.1 * Miscellaneous Ubuntu changes - debian/dkms-versions -- update from master linux-restricted-modules-hwe-5.4 (5.4.0-57.63~18.04.1+1) bionic; urgency=medium * Transition OEM & OSP1 kernel users to generic / hwe-5.4 (LP: #1850612) - [Packaging] Transition oem(-osp1) to hwe-5.4 linux-restricted-modules-hwe-5.4 (5.4.0-57.63~18.04.1) bionic; urgency=medium * Master version: 5.4.0-57.63~18.04.1 * Miscellaneous Ubuntu changes - debian/dkms-versions -- update from master -- Stefan Bader Wed, 09 Dec 2020 12:10:24 +0100 ** Changed in: linux-restricted-modules-hwe-5.4 (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1850612 Title: Transition OEM & OSP1 kernel users to generic / hwe-5.4 Status in linux-meta package in Ubuntu: Fix Released Status in linux-meta-hwe-5.4 package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux-restricted-modules-hwe-5.4 package in Ubuntu: Invalid Status in linux-meta source package in Bionic: Invalid Status in linux-meta-hwe-5.4 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Invalid Status in linux-restricted-modules-hwe-5.4 source package in Bionic: Fix Released Bug description: Topic says it all, focal should not have OEM & OSP1 kernels, the stock kernel is good enough. Also migrate NVIDIA 418 users to 430, since there's no generic modules for 418. bionic: For bionic we're able to migrate OSP1 users to hwe-5.4. OEM will follow after remaining blockers are fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1850612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
This bug was fixed in the package linux - 4.15.0-128.131 --- linux (4.15.0-128.131) bionic; urgency=medium * bionic/linux: 4.15.0-128.131 -proposed tracker (LP: #1907354) * Packaging resync (LP: #1786013) - update dkms package versions * raid10: discard leads to corrupted file system (LP: #1907262) - Revert "md/raid10: improve discard request for far layout" - Revert "md/raid10: improve raid10 discard request" - Revert "md/raid10: pull codes that wait for blocked dev into one function" - Revert "md/raid10: extend r10bio devs to raid disks" - Revert "md: add md_submit_discard_bio() for submitting discard bio" -- Khalid Elmously Wed, 09 Dec 2020 01:27:33 -0500 ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890612] Re: [Source NEW SRU FOCAL] ITP: Please support loading microcode early, whilst otherwise booting without initrd
This bug was fixed in the package linux-meta-aws - 5.4.0.1032.33 --- linux-meta-aws (5.4.0.1032.33) focal; urgency=medium * Bump ABI 5.4.0-1032 * Packaging resync (LP: #1786013) - [Packaging] resync debian/dkms-versions from main package -- Marcelo Henrique Cerri Wed, 09 Dec 2020 10:19:53 -0300 ** Changed in: linux-meta-aws (Ubuntu Focal) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1890612 Title: [Source NEW SRU FOCAL] ITP: Please support loading microcode early, whilst otherwise booting without initrd Status in cloud-images: Fix Committed Status in linux-meta-aws package in Ubuntu: Fix Released Status in microcode-initrd package in Ubuntu: Fix Released Status in linux-meta-aws source package in Focal: Fix Released Status in microcode-initrd source package in Focal: Fix Released Bug description: Now that micorocode-initrd is in focal, linux-meta-aws should start depending on it in focal too. -- [Impact] * New package to provide micorocode-only initrd for application of microcode on boot, when otherwise no initrd is in use. [Test Case] * install microcode-initrd in AWS cloud x86 metal instance * reboot, observe that microcode has been applied, and yet the boot was without initrd (observe journalctl -b -k to see that initrd was not used for boot) [Regression Potential] * This is a brand new package, that will be used by AWS images. Otherwise this package will not be automatically installed anywhere. Re spinning & promoting AWS images are tested and gated by the CPC team. [Other Info] * Original bug report for groovy: Normally Ubuntu boots using initrd that has three archives: early amd64 microcode, early intel microcode, and compressed main initrd. When booting without initrd, simply kernel is loaded without any initrd and thus without microcode. However, grub supports booting with multiple initrds and one can specify a standalone early initrd which contains microcode only, and separate main initrd. As an added bonus one can also specify just eary microcode initrd without a main one, to allow kernel to load microcode early, but otherwise boot without an initrd. To achieve that I need to introduce a microcode-initrd package will will only provide early initrd which only has microcode. The intention is to seed microcode-initrd to targets that boot on baremental without initrd. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1890612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
This bug was fixed in the package linux - 5.4.0-58.64 --- linux (5.4.0-58.64) focal; urgency=medium * focal/linux: 5.4.0-58.64 -proposed tracker (LP: #1907390) * Packaging resync (LP: #1786013) - update dkms package versions * raid10: discard leads to corrupted file system (LP: #1907262) - Revert "dm raid: remove unnecessary discard limits for raid10" - Revert "dm raid: fix discard limits for raid1 and raid10" - Revert "md/raid10: improve discard request for far layout" - Revert "md/raid10: improve raid10 discard request" - Revert "md/raid10: pull codes that wait for blocked dev into one function" - Revert "md/raid10: extend r10bio devs to raid disks" - Revert "md: add md_submit_discard_bio() for submitting discard bio" -- Khalid Elmously Wed, 09 Dec 2020 02:10:30 -0500 ** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905620] Re: please promote modules from extra to modules for HiFive Unleashed
This bug was fixed in the package linux-riscv - 5.8.0-12.14
---
linux-riscv (5.8.0-12.14) groovy; urgency=medium
* groovy/linux-riscv: 5.8.0-12.14 -proposed tracker (LP: #1907406)
[ Ubuntu: 5.8.0-33.36 ]
* groovy/linux: 5.8.0-33.36 -proposed tracker (LP: #1907408)
* raid10: discard leads to corrupted file system (LP: #1907262)
- Revert "dm raid: remove unnecessary discard limits for raid10"
- Revert "dm raid: fix discard limits for raid1 and raid10"
- Revert "md/raid10: improve discard request for far layout"
- Revert "md/raid10: improve raid10 discard request"
- Revert "md/raid10: pull codes that wait for blocked dev into one function"
- Revert "md/raid10: extend r10bio devs to raid disks"
- Revert "md: add md_submit_discard_bio() for submitting discard bio"
linux-riscv (5.8.0-11.13) groovy; urgency=medium
* groovy/linux-riscv: 5.8.0-11.13 -proposed tracker (LP: #1905863)
* please promote modules from extra to modules for HiFive Unleashed
(LP: #1905620)
- [Packaging] Add HiFive Unleashed drivers to generic inclusion list
[ Ubuntu: 5.8.0-32.34 ]
* groovy/linux: 5.8.0-32.34 -proposed tracker (LP: #1905865)
* Packaging resync (LP: #1786013)
- update dkms package versions
* [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports
topology where zoning is enabled in expander (LP: #1899802)
- scsi: mpt3sas: Define hba_port structure
- scsi: mpt3sas: Allocate memory for hba_port objects
- scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device()
- scsi: mpt3sas: Update hba_port's sas_address & phy_mask
- scsi: mpt3sas: Get device objects using sas_address & portID
- scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port()
- scsi: mpt3sas: Get sas_device objects using device's rphy
- scsi: mpt3sas: Update hba_port objects after host reset
- scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough
- scsi: mpt3sas: Handling HBA vSES device
- scsi: mpt3sas: Add bypass_dirty_port_flag parameter
- scsi: mpt3sas: Handle vSES vphy object during HBA reset
- scsi: mpt3sas: Add module parameter multipath_on_hba
- scsi: mpt3sas: Bump driver version to 35.101.00.00
* CVE-2020-12912
- hwmon: (amd_energy) modify the visibility of the counters
* Intel Tiger Lake IDs supplement (LP: #1904521)
- mtd: spi-nor: intel-spi: Add support for Intel Tiger Lake-H SPI serial
flash
- pinctrl: tigerlake: Add support for Tiger Lake-H
* [i915] Noise-like lines of graphics corruption when moving windows in Xorg
sessions (LP: #1896091)
- Revert "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks"
* Fix no headset sound after S3 on Intel HDA (LP: #1904595)
- ALSA: hda: Refactor codec PM to use direct-complete optimization
- ALSA: hda: Separate runtime and system suspend
- ALSA: hda: Reinstate runtime_allow() for all hda controllers
* Ask 8821C Bluetooth controller to drop old firmware (LP: #1904221)
- Bluetooth: btrtl: Ask 8821C to drop old firmware
- Bluetooth: btrtl: fix incorrect skb allocation failure check
* Use ACPI S5 for reboot (LP: #1904225)
- PM: ACPI: reboot: Use S5 for reboot
* Groovy update: v5.8.18 upstream stable release (LP: #1904941)
- netfilter: nftables_offload: KASAN slab-out-of-bounds Read in
nft_flow_rule_create
- io_uring: don't run task work on an exiting task
- io_uring: allow timeout/poll/files killing to take task into account
- io_uring: move dropping of files into separate helper
- io_uring: stash ctx task reference for SQPOLL
- io_uring: unconditionally grab req->task
- io_uring: return cancelation status from poll/timeout/files handlers
- io_uring: enable task/files specific overflow flushing
- io_uring: don't rely on weak ->files references
- io_uring: reference ->nsproxy for file table commands
- io_wq: Make io_wqe::lock a raw_spinlock_t
- io-wq: fix use-after-free in io_wq_worker_running
- io_uring: no need to call xa_destroy() on empty xarray
- io_uring: Fix use of XArray in __io_uring_files_cancel
- io_uring: Fix XArray usage in io_uring_add_task_file
- io_uring: Convert advanced XArray uses to the normal API
- scripts/setlocalversion: make git describe output more reliable
- efi/arm64: libstub: Deal gracefully with EFI_RNG_PROTOCOL failure
- fs/kernel_read_file: Remove FIRMWARE_EFI_EMBEDDED enum
- arm64: Run ARCH_WORKAROUND_1 enabling code on all CPUs
- arm64: Run ARCH_WORKAROUND_2 enabling code on all CPUs
- arm64: link with -z norelro regardless of CONFIG_RELOCATABLE
- x86/PCI: Fix intel_mid_pci.c build error when ACPI is not enabled
- x86, powerpc: Rename memcpy_mcsafe() to copy_mc_to_{user, kernel}()
- [Config] update config for ARCH_HAS_COPY_MC
- x86/copy_mc: Introduce copy_mc_enhanced_fast_string()
- bnxt_en: Check abort error state in bnxt_open_nic().
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
This bug was fixed in the package linux - 5.8.0-33.36 --- linux (5.8.0-33.36) groovy; urgency=medium * groovy/linux: 5.8.0-33.36 -proposed tracker (LP: #1907408) * raid10: discard leads to corrupted file system (LP: #1907262) - Revert "dm raid: remove unnecessary discard limits for raid10" - Revert "dm raid: fix discard limits for raid1 and raid10" - Revert "md/raid10: improve discard request for far layout" - Revert "md/raid10: improve raid10 discard request" - Revert "md/raid10: pull codes that wait for blocked dev into one function" - Revert "md/raid10: extend r10bio devs to raid disks" - Revert "md: add md_submit_discard_bio() for submitting discard bio" -- Khalid Elmously Wed, 09 Dec 2020 03:56:47 -0500 ** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid 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 Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904458] Re: [linux-azure] Batch hibernate and resume IO requests
SRU submission: https://lists.ubuntu.com/archives/kernel-
team/2020-December/115552.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1904458
Title:
[linux-azure] Batch hibernate and resume IO requests
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
In Progress
Status in linux-azure source package in Groovy:
In Progress
Bug description:
[Impact]
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification
delay in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on
a system with limited storage IOPS.
[Test Case]
Follow the steps described here:
https://bugs.launchpad.net/ubuntu/+source/linux-
azure/+bug/1880032/comments/14
And compare the time need to save the instance state.
[Where problems could occur]
Considering the size of the patch and the code it touches, the most
likely issues are related to hibernation itself. Considering the
hibernation isn't officially support, any hibernation issues should
even considered regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904458/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907848] Re: Can't connect to Wi-Fi after update [Atheros AR9565]
** Summary changed: - Can't connect to Wi-Fi after update + Can't connect to Wi-Fi after update [Atheros AR9565] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1907848 Title: Can't connect to Wi-Fi after update [Atheros AR9565] Status in wireless-regdb package in Ubuntu: New Bug description: I can't connect to Wi-Fi after update of this particular package to version 2020.11.20-0ubuntu1~20.10.1 yesterday (10 XII 2020). If I finally connect, Internet is not reliable and soon I can't load any webpage even if I'm connected. When I downgraded this package, Wi-Fi works. System information: Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-31-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 My Wi-Fi device is: Qualcomm Atheros AR9565, driver: ath9k, Wi-Fi N, 2.4GHz ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: wireless-regdb 2020.11.20-0ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 11 19:40:53 2020 Dependencies: InstallationDate: Installed on 2020-02-05 (309 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: wireless-regdb UpgradeStatus: Upgraded to groovy on 2020-10-23 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1907848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907854] Re: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- 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/1907854 Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: After update zfsutils-linux, the update process tries to mount zfs file in /mnt but since in /mnt there are another disk mount fails with: Setting up zfsutils-linux (0.8.3-1ubuntu12.5) ... zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-12-11 21:05:24 CET; 8ms ago Docs: man:zfs(8) Process: 177294 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 177294 (code=exited, status=1/FAILURE) dic 11 21:05:24 serv systemd[1]: Starting Mount ZFS filesystems... dic 11 21:05:24 serv zfs[177294]: cannot mount '/mnt': directory is not empty dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Failed with result 'exit-code'. dic 11 21:05:24 serv systemd[1]: Failed to start Mount ZFS filesystems. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.5 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: python3-aptdaemon.gtk3widgets:amd64: Install aptdaemon:amd64: Install python3-aptdaemon:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 11 20:56:40 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-24 (261 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-19 (206 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1907854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900584] Re: Regression: suspend/wake-up no longer working properly
The crux of the problem is an API mismatch between the kernel module and the nvidia driver. The problem arises in the normal course of applying updates and not from user tinkering (see #1). $ uname -a Linux OptiPlex-380 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ journalctl -b -k | grep -m 1 -A 3 "API mismatch" Dec 11 21:07:00 OptiPlex-380 kernel: NVRM: API mismatch: the client has the version 455.38, but NVRM: this kernel module has the version 440.100. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. $ apt-cache depends linux-modules-nvidia-455-generic linux-modules-nvidia-455-generic Depends: linux-modules-nvidia-455-5.4.0-54-generic Depends: nvidia-kernel-common-455 Depends: nvidia-kernel-common-455 There's no nvidia kernel module for 455 and 5.4.0-47 and hence the broken system. Boot 5.4.0-54 and everything works. Upgrade[boot] 5.4.0-57 and the system breaks again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1900584 Title: Regression: suspend/wake-up no longer working properly Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: With kernel 5.4.0-47.51, suspend (and resuming thereafter) works flawlessly. With 5.4.0-48.52 and later versions, the display refuses to wake up after a suspend. Display adaptor: Nvidia driver version: 440.100 Screens: 1 GPU: GeForce GT 710 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 1332 F pulseaudio /dev/snd/controlC0: craig 1332 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 20:15:38 2020 InstallationDate: Installed on 2020-09-04 (44 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enx582c80139263 no wireless extensions. lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=90130dae-9aab-4a03-9308-cf17561e3af2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 01TKCC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/24/2011:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn01TKCC:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907854] [NEW] package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit statu
Public bug reported: After update zfsutils-linux, the update process tries to mount zfs file in /mnt but since in /mnt there are another disk mount fails with: Setting up zfsutils-linux (0.8.3-1ubuntu12.5) ... zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-12-11 21:05:24 CET; 8ms ago Docs: man:zfs(8) Process: 177294 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 177294 (code=exited, status=1/FAILURE) dic 11 21:05:24 serv systemd[1]: Starting Mount ZFS filesystems... dic 11 21:05:24 serv zfs[177294]: cannot mount '/mnt': directory is not empty dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Failed with result 'exit-code'. dic 11 21:05:24 serv systemd[1]: Failed to start Mount ZFS filesystems. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.5 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: python3-aptdaemon.gtk3widgets:amd64: Install aptdaemon:amd64: Install python3-aptdaemon:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 11 20:56:40 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-24 (261 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-19 (206 days ago) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1907854 Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: After update zfsutils-linux, the update process tries to mount zfs file in /mnt but since in /mnt there are another disk mount fails with: Setting up zfsutils-linux (0.8.3-1ubuntu12.5) ... zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-12-11 21:05:24 CET; 8ms ago Docs: man:zfs(8) Process: 177294 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 177294 (code=exited, status=1/FAILURE) dic 11 21:05:24 serv systemd[1]: Starting Mount ZFS filesystems... dic 11 21:05:24 serv zfs[177294]: cannot mount '/mnt': directory is not empty dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Failed with result 'exit-code'. dic 11 21:05:24 serv systemd[1]: Failed to start Mount ZFS filesystems. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.5 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: python3-aptdaemon.gtk3widgets:amd64: Install aptdaemon:amd64: Install python3-aptdaemon:amd64: Install NULL: ConfigurePending Architecture: amd64
[Kernel-packages] [Bug 1904458] Re: [linux-azure] Batch hibernate and resume IO requests
I tested the change on Azure using Standard L8s_v2 (8 vcpus, 64 GiB
memory) VMs using the 5.4 linux-azure kernel on bionic and the 5.8
kernel on groovy.
During my tests the VMs continued to successfully hibernate with the
patch and the time needed to save the VM state went down from 25 seconds
to around 3 seconds.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1904458
Title:
[linux-azure] Batch hibernate and resume IO requests
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
In Progress
Status in linux-azure source package in Groovy:
In Progress
Bug description:
[Impact]
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification
delay in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on
a system with limited storage IOPS.
[Test Case]
Follow the steps described here:
https://bugs.launchpad.net/ubuntu/+source/linux-
azure/+bug/1880032/comments/14
And compare the time need to save the instance state.
[Where problems could occur]
Considering the size of the patch and the code it touches, the most
likely issues are related to hibernation itself. Considering the
hibernation isn't officially support, any hibernation issues should
even considered regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904458/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904458] Re: [linux-azure] Batch hibernate and resume IO requests
Targeting only 5.4 and 5.8 since 4.15 will not support hibernation.
** No longer affects: linux-azure-4.15 (Ubuntu)
** Also affects: linux-azure (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Focal)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Changed in: linux-azure (Ubuntu Groovy)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Changed in: linux-azure (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Groovy)
Status: New => In Progress
** Description changed:
+ [Impact]
+
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification delay
in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
-
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on a
system with limited storage IOPS.
+
+
+ [Test Case]
+
+ Follow the steps described here:
+
+ https://bugs.launchpad.net/ubuntu/+source/linux-
+ azure/+bug/1880032/comments/14
+
+ And compare the time need to save the instance state.
+
+
+ [Where problems could occur]
+
+ Considering the size of the patch and the code it touches, the most
+ likely issues are related to hibernation itself. Considering the
+ hibernation isn't officially support, any hibernation issues should even
+ considered regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1904458
Title:
[linux-azure] Batch hibernate and resume IO requests
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
In Progress
Status in linux-azure source package in Groovy:
In Progress
Bug description:
[Impact]
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification
delay in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on
a system with limited storage IOPS.
[Test Case]
Follow the steps described here:
https://bugs.launchpad.net/ubuntu/+source/linux-
azure/+bug/1880032/comments/14
And compare the time need to save the instance state.
[Where problems could occur]
Considering the size of the patch and the code it touches, the most
likely issues are related to hibernation itself. Considering the
hibernation isn't officially support, any hibernation issues should
even considered regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904458/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907432] Re: Raspberry Pi 400 Kernel Panic
Sorry, muscle memory kicked in. This problem is confirmed and on my list of things to look at. ** Changed in: linux-raspi (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1907432 Title: Raspberry Pi 400 Kernel Panic Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Triaged Bug description: When I power the Pi 400 down (with the key-combination on the pi 400 or with the navigation from the top right), a line like this is on screen: [59095.049506] reboot: Power down or that: [25784.810857] reboot: Power down Under this line, the cursor is frozen. After a while, suddenly, the text scrolls and stops after a while. I can read something about "Kernel Panic" on screen. I cannot power the device off. I have to pull the power plug to shut it down, or to re-plug it to reset it. The power-button (2sec) does not work, 10 seconds reset signal, neither. Here you can find my initial question to this phenomenon: https://answers.launchpad.net/ubuntu/+question/694349 This I should include: Linux version 5.8.0-1008-raspi (buildd@bos02-arm64-062) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #11-Ubuntu SMP PREEMPT Thu Nov 12 15:49:32 UTC 2020 I hope this report includes enough information. If not, please do not hesitate to contact me! Thanks so much for this project and thx for being a part of it! <3 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-1008-raspi 5.8.0-1008.11 ProcVersionSignature: Ubuntu 5.8.0-1008.11-raspi 5.8.17 Uname: Linux 5.8.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 9 10:40:08 2020 ImageMediaBuild: 20201022 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1907432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906691] Re: Laptop wakes up immediatly from suspend to RAM
Just tried it, the problem remains even with these two modules unloaded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906691 Title: Laptop wakes up immediatly from suspend to RAM Status in linux package in Ubuntu: Confirmed Bug description: Since last kernel update to (5.4.0-56-generic #62-Ubuntu SMP), my laptop wakes up as soon as it reaches the suspend to RAM S3 state. I'm running ubuntu 20.04 on a Microsoft Surface Pro (the 2013 version). The only relevant error message I found is : ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wilk 1801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Dec 3 17:35:36 2020 HibernationDevice: RESUME=UUID=adb12a68-9928-4181-b4e2-487010d3c501 InstallationDate: Installed on 2017-10-22 (1138 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Microsoft Corporation Surface with Windows 8 Pro ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=919f00b8-5010-46e1-b2f9-c129e17d5312 ro video=VGA-1:1366x768@60 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-generic N/A linux-backports-modules-5.4.0-56-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.00.0250 dmi.board.asset.tag: 0 dmi.board.name: Surface with Windows 8 Pro dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 17 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.00.0250:bd01/08/2013:svnMicrosoftCorporation:pnSurfacewithWindows8Pro:pvr1:rvnMicrosoftCorporation:rnSurfacewithWindows8Pro:rvr1:cvnMicrosoftCorporation:ct17:cvr1: dmi.product.family: Surface dmi.product.name: Surface with Windows 8 Pro dmi.product.sku: Surface_PRO_1 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907848] Re: Can't connect to Wi-Fi after update
** Description changed: I can't connect to Wi-Fi after update of this particular package to version 2020.11.20-0ubuntu1~20.10.1 yesterday (10 XII 2020). If I finally connect, Internet is not reliable and soon I can't load any - webpage even if I'm connected. + webpage even if I'm connected. When I downgraded this package, Wi-Fi + works. System information: Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-31-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 My Wi-Fi device is: Qualcomm Atheros AR9565, driver: ath9k, Wi-Fi N, 2.4GHz ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: wireless-regdb 2020.11.20-0ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 11 19:40:53 2020 Dependencies: - + InstallationDate: Installed on 2020-02-05 (309 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: wireless-regdb UpgradeStatus: Upgraded to groovy on 2020-10-23 (49 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1907848 Title: Can't connect to Wi-Fi after update Status in wireless-regdb package in Ubuntu: New Bug description: I can't connect to Wi-Fi after update of this particular package to version 2020.11.20-0ubuntu1~20.10.1 yesterday (10 XII 2020). If I finally connect, Internet is not reliable and soon I can't load any webpage even if I'm connected. When I downgraded this package, Wi-Fi works. System information: Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-31-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 My Wi-Fi device is: Qualcomm Atheros AR9565, driver: ath9k, Wi-Fi N, 2.4GHz ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: wireless-regdb 2020.11.20-0ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 11 19:40:53 2020 Dependencies: InstallationDate: Installed on 2020-02-05 (309 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: wireless-regdb UpgradeStatus: Upgraded to groovy on 2020-10-23 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1907848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907848] [NEW] Can't connect to Wi-Fi after update
Public bug reported: I can't connect to Wi-Fi after update of this particular package to version 2020.11.20-0ubuntu1~20.10.1 yesterday (10 XII 2020). If I finally connect, Internet is not reliable and soon I can't load any webpage even if I'm connected. When I downgraded this package, Wi-Fi works. System information: Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-31-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 My Wi-Fi device is: Qualcomm Atheros AR9565, driver: ath9k, Wi-Fi N, 2.4GHz ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: wireless-regdb 2020.11.20-0ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 11 19:40:53 2020 Dependencies: InstallationDate: Installed on 2020-02-05 (309 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: wireless-regdb UpgradeStatus: Upgraded to groovy on 2020-10-23 (49 days ago) ** Affects: wireless-regdb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1907848 Title: Can't connect to Wi-Fi after update Status in wireless-regdb package in Ubuntu: New Bug description: I can't connect to Wi-Fi after update of this particular package to version 2020.11.20-0ubuntu1~20.10.1 yesterday (10 XII 2020). If I finally connect, Internet is not reliable and soon I can't load any webpage even if I'm connected. When I downgraded this package, Wi-Fi works. System information: Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-31-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 My Wi-Fi device is: Qualcomm Atheros AR9565, driver: ath9k, Wi-Fi N, 2.4GHz ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: wireless-regdb 2020.11.20-0ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 11 19:40:53 2020 Dependencies: InstallationDate: Installed on 2020-02-05 (309 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: wireless-regdb UpgradeStatus: Upgraded to groovy on 2020-10-23 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1907848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905663] Re: Add dpcd backlight control for 0x4c83 0x4f41
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1905663 Title: Add dpcd backlight control for 0x4c83 0x4f41 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 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] There is a new OLED panel that is required to be listed in the EDID quirk to make its backlight work. [Fix] The commit adds its EDID to the quirk. https://lkml.org/lkml/2020/11/19/1564 [Test] Verified on Dell's platform with this panel. [Where problems could occur] Only if this panel switches to use PWM mode only, and doesn't support DPCD backlight. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906229] Re: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1906229 Title: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Dell Precision 5550 cannot detect Thunderbolt device hotplug. [Fix] Refresh ACPI wakeup power if it's already enabled to make GPE work. [Test] Make sure the root port of TBT hierachy is in D3cold. Plug a Thunderbolt Dock or Thunderbolt Disk, the system cannot detect anything. With the patch applied, OS can always detect hotplugged Thunderbolt devices. [Where problems could occur] Though we refresh the wakeup device power, we didn't disable/enable ACPI GPEs, so we won't miss any GPE event from this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904521] Re: Intel Tiger Lake IDs supplement
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1904521 Title: Intel Tiger Lake IDs supplement Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: [Impact] Intel Tiger Lake-H platform requires new pin settings and IDs to enable. [Fix] Intel provides us a list of TGL-H commits from 5.8 and 5.9, we need all of the commits to enable TGL-H platforms completely. [Test] Verified those commits on Intel TGL-H SDP [Regression potential] Low, all of those commits are adding new IDs for TGL-H platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904430] Re: Fix AMD GFX where no HDMI audio when hotplugging different monitors
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1904430 Title: Fix AMD GFX where no HDMI audio when hotplugging different monitors Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] Hotplugging different monitors on different ports makes HDMI audio disappears. [Fix] Make sure new EDID is added. [Test case] Boot up with a HDMI monitor with audio output, unplug the monitor and plug another monitor without speaker and without audio jack. Then plug back the original monitor. With the patch applied, there's still HDMI audio output from the original monitor. [Where problems could occur] If the EDID is valid, the driver does the correct thing. If the EDID is invalid, then the driver spends a bit more time setting up EDID, without doing any harm. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904595] Re: Fix no headset sound after S3 on Intel HDA
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1904595
Title:
Fix no headset sound after S3 on Intel HDA
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[Impact]
After system S3, hotplugging headset cannot produce any sound despite of
being auto-selected as audio output.
[Fix]
Avoid using pm_runtime_force_{suspend,resume} helpers to ensure codec
suspend/resume flow, and also ensure HDA driver and PCI set correct
wakeup settings.
[Test case]
Plug headset, unplug headset, switch audio ouput from speakers to HDMI
to let Intel HDA auto suspend. Suspend/resume the system, plug the
headset again, hear no sound.
With the patch series applied, the issue is gone.
[Where problems could occur]
If there is bad firmware/hardware that makes codec have system-wide
wakeup capability, direct-complete flow may trigger unwanted system
wakeup or even break system suspend. The series was tested on both AMD
and Intel platforms, with Realtek and Connexant codecs respectively.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1904595/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907761] Re: vanishing kernel 5.4.0-56-generic
OK I have now officially had enough of this ToyTown Distro. You make a severe CRITICAL mistake and then try to triage it away by insisting we use a tool that simply does not work. This bug is not even assigned to anyone yet. That tells me everything I need to know about whether to persist with this idiocy. Not only are you feckless cretins, you are also incapable of fixing your own mess. And the reporting procedures are hopeless. My recommendation to management is that we find another solution as a matter of urgency. Goodbye. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic Status in linux-meta package in Ubuntu: Incomplete Bug description: Kernel version 5.4.0-56-generic has just vanished off the face of the earth, after an update to that version some days ago. This was not updated from "proposed" or anything like that, it was updated in the normal way from "focal-updates". I had to revert several systems to kernel version 5.4.0-54-generic, after apt reported that my installed 5.4.0-56-generic packages were foreign, unknown and unaccounted-for. Have you lost your damn minds? By all means issue a fix for this outrageous situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906949] Re: ext4_find_entry:1531
no. it happened: when i was installing a steam game, when i was transfering files between external hdd and onboard nvme, when i was checking my code in vscode, when i was opening a new tab in firefox.. in the first 2 days after building my pc it happened anywhere from 30 min into using the cpu to a few hours in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906949 Title: ext4_find_entry:1531 Status in linux package in Ubuntu: Incomplete Bug description: Installed Ubunutu 20.04 on a fresh machine, ASRock b450 Pro4 with a Kingston A2000 1TB PCI Express 3.0 x4 M.2 2280 in the M.2 Ultra slot. Randomly, got freezes with only cursor moving on screen and after a few minutes i'd get a black screen with errors, EXT4-fs error (device nvme0n1p2): _ext4_find_entry: 1531 and Failed to write entry, ignoring: Read-only file system. (attached photo) I am a fresh Ubuntu user, not really tech savy, help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claus 1354 F pulseaudio /dev/snd/controlC1: claus 1354 F pulseaudio /dev/snd/pcmC1D0p: claus 1354 F...m pulseaudio /dev/snd/timer: claus 1354 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 5 21:36:02 2020 InstallationDate: Installed on 2020-12-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=6c1a0898-4be8-465f-b69f-87c3a0d49cd4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-generic N/A linux-backports-modules-5.4.0-56-generic N/A linux-firmware1.187.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target
Adding this bug as that seems to be the exact issue here - https://github.com/openzfs/zfs/issues/10140 Solution is "Use zfs-mount-generator instead of zfs-mount.service" ... ** Bug watch added: github.com/openzfs/zfs/issues #10140 https://github.com/openzfs/zfs/issues/10140 -- 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/1904764 Title: failed boot mount, and systemd ordering cycle on zfs-import.target Status in zfs-linux package in Ubuntu: Confirmed Bug description: On a new Ubuntu 20.10 ZoL root I frequently get boot failures, and I see these errors: [ 11.353930] systemd[1]: boot.mount: Mount process exited, code=exited, status=1/FAILURE [ 11.353934] systemd[1]: boot.mount: Failed with result 'exit-code'. [ 11.354267] systemd[1]: Failed to mount /boot. [ 11.354307] systemd[1]: Dependency failed for /boot/efi. [ 11.354327] systemd[1]: Dependency failed for /boot/grub. [ 11.354344] systemd[1]: Dependency failed for Local File Systems. [ 11.354365] systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. [ 11.354367] systemd[1]: local-fs.target: Triggering OnFailure= dependencies. [ 11.355088] systemd[1]: var-lib.mount: Found ordering cycle on zfs-import.target/start [ 11.355090] systemd[1]: var-lib.mount: Found dependency on zfs-import-cache.service/start [ 11.355091] systemd[1]: var-lib.mount: Found dependency on zfs-load-module.service/start [ 11.355093] systemd[1]: var-lib.mount: Found dependency on cryptsetup.target/start [ 11.355094] systemd[1]: var-lib.mount: Found dependency on systemd-cryptsetup@cryptoswap.service/start [ 11.355096] systemd[1]: var-lib.mount: Found dependency on systemd-random-seed.service/start [ 11.355097] systemd[1]: var-lib.mount: Found dependency on var-lib.mount/start [ 11.355099] systemd[1]: var-lib.mount: Job zfs-import.target/start deleted to break ordering cycle starting with var-lib.mount/start [ 11.355819] systemd[1]: boot-grub.mount: Job boot-grub.mount/start failed with result 'dependency'. [ 11.355823] systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with result 'dependency'. Journalctl shows "filesystem 'bpool/BOOT/ubuntu_o9gk00' cannot be mounted, unable to open the dataset" for boot.mount I can manually start boot.mount from the console, which then lets the boot process complete. N.B. "zfs list" is NAME USED AVAIL REFER MOUNTPOINT bpool 402M 1.36G 96K /boot bpool/BOOT 401M 1.36G 96K none bpool/BOOT/ubuntu_o9gk00 401M 1.36G 201M /boot rpool 171G 720G 192K / rpool/ROOT9.26G 720G 192K none rpool/ROOT/ubuntu_1.57G 720G 5.16G / rpool/ROOT/ubuntu_o9gk00 7.69G 720G 4.24G / rpool/ROOT/ubuntu_o9gk00/srv 192K 720G 192K /srv rpool/ROOT/ubuntu_o9gk00/usr 1.02M 720G 192K /usr rpool/ROOT/ubuntu_o9gk00/usr/local 852K 720G 388K /usr/local rpool/ROOT/ubuntu_o9gk00/var 2.09G 720G 192K /var rpool/ROOT/ubuntu_o9gk00/var/games 192K 720G 192K /var/games rpool/ROOT/ubuntu_o9gk00/var/lib 1.85G 720G 1.42G /var/lib rpool/ROOT/ubuntu_o9gk00/var/lib/AccountsService 1.39M 720G 496K /var/lib/AccountsService rpool/ROOT/ubuntu_o9gk00/var/lib/NetworkManager 3.39M 720G 292K /var/lib/NetworkManager rpool/ROOT/ubuntu_o9gk00/var/lib/apt 87.2M 720G 78.0M /var/lib/apt rpool/ROOT/ubuntu_o9gk00/var/lib/dpkg 148M 720G 63.6M /var/lib/dpkg rpool/ROOT/ubuntu_o9gk00/var/log 223M 720G 94.2M /var/log rpool/ROOT/ubuntu_o9gk00/var/mail 1.19M 720G 224K /var/mail rpool/ROOT/ubuntu_o9gk00/var/snap 940K 720G 500K /var/snap rpool/ROOT/ubuntu_o9gk00/var/spool26.7M 720G 5.52M /var/spool rpool/ROOT/ubuntu_o9gk00/var/www 192K 720G 192K /var/www rpool/USERDATA 162G 720G 192K / rpool/USERDATA/chris_hwz0bd162G 720G 156G /home/chris rpool/USERDATA/root_hwz0bd2.91M 720G 804K /root rpool/keystore 518M 720G 48.1M - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904764/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1906949] Re: ext4_find_entry:1531
Does this issue only happen after suspend? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906949 Title: ext4_find_entry:1531 Status in linux package in Ubuntu: Incomplete Bug description: Installed Ubunutu 20.04 on a fresh machine, ASRock b450 Pro4 with a Kingston A2000 1TB PCI Express 3.0 x4 M.2 2280 in the M.2 Ultra slot. Randomly, got freezes with only cursor moving on screen and after a few minutes i'd get a black screen with errors, EXT4-fs error (device nvme0n1p2): _ext4_find_entry: 1531 and Failed to write entry, ignoring: Read-only file system. (attached photo) I am a fresh Ubuntu user, not really tech savy, help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claus 1354 F pulseaudio /dev/snd/controlC1: claus 1354 F pulseaudio /dev/snd/pcmC1D0p: claus 1354 F...m pulseaudio /dev/snd/timer: claus 1354 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 5 21:36:02 2020 InstallationDate: Installed on 2020-12-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=6c1a0898-4be8-465f-b69f-87c3a0d49cd4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-generic N/A linux-backports-modules-5.4.0-56-generic N/A linux-firmware1.187.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906949] Re: ext4_find_entry:1531
Yes. I changed my NVMe slot. But the change 'nvme_core.default_ps_max_latency_us=5500' has proven stable on both slots. attached dmesg. below the output of the lspci -tv command. -[:00]-+-00.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex +-01.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge +-01.1-[01]00.0 Kingston Technology Company, Inc. Device 2263 +-01.3-[02-09]--+-00.0 Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller | +-00.1 Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller | \-00.2-[03-09]--+-00.0-[04]-- | +-01.0-[05]-- | +-04.0-[06]-- | +-05.0-[07]-- | +-06.0-[08]00.0 ASMedia Technology Inc. ASM1062 Serial ATA Controller | \-07.0-[09]00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller +-02.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge +-03.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge +-03.1-[0a]--+-00.0 NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] |+-00.1 NVIDIA Corporation TU116 High Definition Audio Controller |+-00.2 NVIDIA Corporation TU116 USB 3.1 Host Controller |\-00.3 NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] +-04.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge +-05.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge +-07.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge +-07.1-[0b]00.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function +-08.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge +-08.1-[0c]--+-00.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP |+-00.1 Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP |+-00.3 Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller |\-00.4 Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller +-08.2-[0d]00.0 Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] +-08.3-[0e]00.0 Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] +-14.0 Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller +-14.3 Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge +-18.0 Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 +-18.1 Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 +-18.2 Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 +-18.3 Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 +-18.4 Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 +-18.5 Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 +-18.6 Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 \-18.7 Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906949/+attachment/5442811/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906949 Title: ext4_find_entry:1531 Status in linux package in Ubuntu: Incomplete Bug description: Installed Ubunutu 20.04 on a fresh machine, ASRock b450 Pro4 with a Kingston A2000 1TB PCI Express 3.0 x4 M.2 2280 in the M.2 Ultra slot. Randomly, got freezes with only cursor moving on screen and after a few minutes i'd get a black screen with errors, EXT4-fs error (device nvme0n1p2): _ext4_find_entry: 1531 and Failed to write entry, ignoring: Read-only file system. (attached photo) I am a fresh Ubuntu user, not really tech savy, help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claus 1354 F pulseaudio /dev/snd/controlC1: claus 1354 F pulseaudio /dev/snd/pcmC1D0p:
[Kernel-packages] [Bug 1900584] Re: Regression: suspend/wake-up no longer working properly
focal-updates only has nvidia-driver-450. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1900584 Title: Regression: suspend/wake-up no longer working properly Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: With kernel 5.4.0-47.51, suspend (and resuming thereafter) works flawlessly. With 5.4.0-48.52 and later versions, the display refuses to wake up after a suspend. Display adaptor: Nvidia driver version: 440.100 Screens: 1 GPU: GeForce GT 710 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 1332 F pulseaudio /dev/snd/controlC0: craig 1332 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 20:15:38 2020 InstallationDate: Installed on 2020-09-04 (44 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enx582c80139263 no wireless extensions. lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=90130dae-9aab-4a03-9308-cf17561e3af2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 01TKCC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/24/2011:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn01TKCC:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900584] Re: Regression: suspend/wake-up no longer working properly
$ sudo apt update ... $ sudo apt install nvidia-drivers-455 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package nvidia-drivers-455 $ sudo apt install nvidia-driver-455 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package nvidia-driver-455 I no longer have focal-proposed enabled. Not sure if that makes a difference. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1900584 Title: Regression: suspend/wake-up no longer working properly Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: With kernel 5.4.0-47.51, suspend (and resuming thereafter) works flawlessly. With 5.4.0-48.52 and later versions, the display refuses to wake up after a suspend. Display adaptor: Nvidia driver version: 440.100 Screens: 1 GPU: GeForce GT 710 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 1332 F pulseaudio /dev/snd/controlC0: craig 1332 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 20:15:38 2020 InstallationDate: Installed on 2020-09-04 (44 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enx582c80139263 no wireless extensions. lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=90130dae-9aab-4a03-9308-cf17561e3af2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 01TKCC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/24/2011:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn01TKCC:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900584] Re: Regression: suspend/wake-up no longer working properly
Something like `sudo apt install nvidia-drivers-455` should do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1900584 Title: Regression: suspend/wake-up no longer working properly Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: With kernel 5.4.0-47.51, suspend (and resuming thereafter) works flawlessly. With 5.4.0-48.52 and later versions, the display refuses to wake up after a suspend. Display adaptor: Nvidia driver version: 440.100 Screens: 1 GPU: GeForce GT 710 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 1332 F pulseaudio /dev/snd/controlC0: craig 1332 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 20:15:38 2020 InstallationDate: Installed on 2020-09-04 (44 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enx582c80139263 no wireless extensions. lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=90130dae-9aab-4a03-9308-cf17561e3af2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 01TKCC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/24/2011:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn01TKCC:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906095] Re: Fails to boot
There was also a recent linux-firmware update that I applied with no luck. At this point is another ubuntu-bug report needed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906095 Title: Fails to boot Status in linux package in Ubuntu: Confirmed Bug description: 1) Ubuntu 20.10 2) kernel 5.8.0-29-generic 3) To boot 4) Instead the boot screen only shows up on one monitor and freezes ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Nov 28 00:21:51 2020 InstallationDate: Installed on 2020-11-19 (8 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=b19340a3-b1fa-4e95-88ea-3b3d2ff8e4f6 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3201 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X299-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3201:bd09/04/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX299-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900584] Re: Regression: suspend/wake-up no longer working properly
>"it looks like the user installed the driver through >the nvidia installer, and then used our packages. >The perfect recipe for disaster." Thanks for continuing to look into this. I don't believe I have an nvidia installer, only nvidia settings. I can't test with a live disk, because the nvidia install requires a restart. I'm happy to purge everything nvidia and reinstall if that helps. Please provide the commands you wish to be executed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1900584 Title: Regression: suspend/wake-up no longer working properly Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: With kernel 5.4.0-47.51, suspend (and resuming thereafter) works flawlessly. With 5.4.0-48.52 and later versions, the display refuses to wake up after a suspend. Display adaptor: Nvidia driver version: 440.100 Screens: 1 GPU: GeForce GT 710 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 1332 F pulseaudio /dev/snd/controlC0: craig 1332 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 20:15:38 2020 InstallationDate: Installed on 2020-09-04 (44 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enx582c80139263 no wireless extensions. lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=90130dae-9aab-4a03-9308-cf17561e3af2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 01TKCC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/24/2011:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn01TKCC:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904458] Re: [linux-azure] Batch hibernate and resume IO requests
** Also affects: linux-azure-4.15 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1904458
Title:
[linux-azure] Batch hibernate and resume IO requests
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Bug description:
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification
delay in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on
a system with limited storage IOPS.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904458/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907761] Re: vanishing kernel 5.4.0-56-generic
This affects multiple GA and HWE (including -edge) stacks. These are the notices announcing the now missing package versions as intentional releases: https://ubuntu.com/security/notices/USN-4658-1 https://ubuntu.com/security/notices/USN-4659-1 https://ubuntu.com/security/notices/USN-4660-1 https://ubuntu.com/security/notices/USN-4657-1 These are the "-generic" package names that should include the security backports for (among others) CVE-2020-28915 but are now missing: linux-image-5.8.0-31-generic linux-image-5.4.0-56-generic linux-image-4.15.0-126-generic These links at this moment point nowhere: https://packages.ubuntu.com/focal/linux-image-5.8.0-31-generic https://packages.ubuntu.com/bionic/linux-image-5.4.0-56-generic https://packages.ubuntu.com/xenial/linux-image-4.15.0-126-generic ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28915 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic Status in linux-meta package in Ubuntu: Incomplete Bug description: Kernel version 5.4.0-56-generic has just vanished off the face of the earth, after an update to that version some days ago. This was not updated from "proposed" or anything like that, it was updated in the normal way from "focal-updates". I had to revert several systems to kernel version 5.4.0-54-generic, after apt reported that my installed 5.4.0-56-generic packages were foreign, unknown and unaccounted-for. Have you lost your damn minds? By all means issue a fix for this outrageous situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907761] Re: vanishing kernel 5.4.0-56-generic
I have created Bug 1907814 to complain about apport refusing to report bugs about unknown updates with an unhelpful message. I believe these remain two separate concerns: a) Retracting security upgrades on purpose after releasing them to non-proposed channels needs a better workflow, reverting in a lower version number is probably entirely unnecessary for smooth upgrades. b) Apport should still be improved even if this is never done on purpose again, because there are other reasons a Package might vanish (outdated mirrors I guess) which apport should be failing gracefully about. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic Status in linux-meta package in Ubuntu: Incomplete Bug description: Kernel version 5.4.0-56-generic has just vanished off the face of the earth, after an update to that version some days ago. This was not updated from "proposed" or anything like that, it was updated in the normal way from "focal-updates". I had to revert several systems to kernel version 5.4.0-54-generic, after apt reported that my installed 5.4.0-56-generic packages were foreign, unknown and unaccounted-for. Have you lost your damn minds? By all means issue a fix for this outrageous situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905632] Re: Touchpad not recognized
[2.162691] platform idma64.0: failed to claim resource 0: [mem 0x0800-0x0fff] [2.162694] intel-lpss :00:15.0: Failed to add idma64, fallback to PIO Please try kernel parameter "pci=nocrs". ** 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/1905632 Title: Touchpad not recognized Status in linux package in Ubuntu: Incomplete Bug description: Just bought this note and installed Ubunt 20.04. All ok, except for touchpad not being recognized. xinput Returns: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9[slave keyboard (3)] ↳ Ideapad extra buttons id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] cat /proc/bus/input/devices | grep -I touchpad Returns nothing Thanks in advance. 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.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sergio 1565 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 20:12:31 2020 InstallationDate: Installed on 2020-11-25 (0 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 004: ID 1d57:0005 Xenta Wireless Receiver (Keyboard and Mouse) Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82DJ ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:svnLENOVO:pn82DJ:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 82DJ dmi.product.sku: LENOVO_MT_82DJ_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid 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 Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907308] Re: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05
Maybe ask this in Lenovo forum? This is indeed a kernel issue, however we can't do much without physical access... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 Status in linux package in Ubuntu: Incomplete Bug description: The keys marked for brightness control on the keyboard are supposed to be Fn+F5 (down) and Fn+F6 (up). But pressing them does not have any effects. Volume control keys Fn+F1 (off), Fn+F2 (down), Fn+F3 (up) all do work, and KDE shows appropriate indicators when they are pressed. I know this is a popular problem with Lenovo laptops. I use Ubuntu 21.04 Hirsute on built-in NVMe, but Ubuntu 20.04 booted from USB flash drive also does not allow me to control screen brightness. Hardware and OS information will be collected on Apport request and attached here. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mwg1006 F pulseaudio mwg1010 F pipewire-media- /dev/snd/seq:mwg1005 F pipewire BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Ubuntu 21.04 DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G1 (Ice Lake) [17aa:3fd9] HibernationDevice: #RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc RESUME=UUID=ce49bc01-a59b-4abf-9110-87bc71689769 InstallationDate: Installed on 2009-11-01 (4055 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: LENOVO 81YK NonfreeKernelModules: wl Package: xorg 1:7.7+19ubuntu15 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-31-generic root=/dev/mapper/vg_c540scadaw-root64 ro rootflags=commit=3600 transparent_hugepage=always init=/lib/systemd/systemd ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A linux-firmware1.192 Tags: hirsute ubuntu single-occurrence reproducible has-workaround Uname: Linux 5.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout dip disk kvm libvirt lpadmin netdev plugdev sambashare src _MarkForUpload: True dmi.bios.date: 07/06/2020 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvrDPCN45WW:bd07/06/2020:br1.45:efr1.45:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898057] Re: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4
After a reboot of the whole fabric (switches and machines), this problem has not resurfaced. Conceivably this could have been a transient error state, so I will close this with "invalid". ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Invalid Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel:
[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc
Hi, Joseph. I've built test kernels for xenial:linux-azure, bionic:linux-azure-4.15 and focal:linux-azure. You can find them at: https://kernel.ubuntu.com/~mhcerri/azure/lp1902531/ Inside each directory, I included all the kernel .deb files and also a tarball containing the same .debs. The patches used for each kernel version is also inside each directory. Let me know if they work as expected. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1902531 Title: [linux-azure] IP forwarding issue in netvsc Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure-4.15 source package in Focal: Invalid Bug description: We identified an issue with the Linux netvsc driver when used in IP forwarding mode. The problem is that the RSS hash value is not propagated to the outgoing packet, and so such packets go out on channel 0. This produces an imbalance across outgoing channels, and a possible overload on the single host-side CPU that is processing channel 0. The problem does not occur when Accelerated Networking is used because the packets go out through the Mellanox driver. Because it is tied to IP forwarding, the problem is presumably most likely to be visible in a virtual appliance device that is doing network load balancing or other kinds of packet filtering and redirection. We would like to request fixes to this issue in 16.04, 18.04 and 20.04. Two fixes are already in the upstream v5.5+, so they’re already in 5.8.0-1011.11. For 5.4.0-1031.32, the 2 fixes can apply cleanly: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 5.0.0-1036.38, we need 1 more patch applied first, so the list is: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan backported them here: https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795 https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a (The 2 patches are on the branch https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
I checked on kernel 5.9.12 Ubuntu 20.04 Huawei amd D13 , problem not
solved
--
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/1887968
Title:
Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
Status in Linux:
Confirmed
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03
[Kernel-packages] [Bug 1907308] Re: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05
$ sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Sleep Button /dev/input/event3: AT Translated Set 2 keyboard /dev/input/event4: Video Bus /dev/input/event5: Ideapad extra buttons /dev/input/event6: MSFT0001:01 04F3:3140 Mouse /dev/input/event7: MSFT0001:01 04F3:3140 Touchpad /dev/input/event8: sof-hda-dsp Mic /dev/input/event9: sof-hda-dsp Headphone /dev/input/event10: sof-hda-dsp HDMI/DP,pcm=3 /dev/input/event11: sof-hda-dsp HDMI/DP,pcm=4 /dev/input/event12: sof-hda-dsp HDMI/DP,pcm=5 /dev/input/event13: Integrated Camera: Integrated C Select the device event number [0-13]: tried to select 5, could not trigger any events from keyboard tried to select 3, could trigger code 113 (KEY_MUTE), code 114 (KEY_VOLUMEDOWN) and code 115 (KEY_VOLUMEUP) with Fn+F1/F2/F3, _nothing happened_ with pressing Fn+F4 (picture: microphone off), Fn+F5 (picture: brightness down), Fn+F6 (picture: brightness up), Fn+F8 (picture: airplane mode), Fn+Insert (on the right from F12, picture: star and letter S), Fn+PrtSc (picture: scissors and oval pointed cutout) With Fn+F7 (picture: probably switch between local/external display), ^X@sp is printed in the terminal (Konsole), and the following events are dumped : Event: time 1607686644.627232, type 4 (EV_MSC), code 4 (MSC_SCAN), value 19 Event: time 1607686644.627232, type 1 (EV_KEY), code 25 (KEY_P), value 0 Event: time 1607686644.627232, -- SYN_REPORT Event: time 1607686644.632269, type 4 (EV_MSC), code 4 (MSC_SCAN), value db Event: time 1607686644.632269, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 0 Event: time 1607686644.632269, -- SYN_REPORT Fn+F9 (picture: cog wheel or sun) prints ^X@si and code 23 (KEY_I) in the dump, Fn+F10 (picture: lock) prints ^X@sl and code 38 (KEY_L), Fn+F11 (picture: bar with 3 squares within) generated ESC Tab (0x1b 0x9) codes Fn+F12 (picture: calculator) generates code 140 (KEY_CALC) multimedia keys above the Num field generated codes 164 (KEY_PLAYPAUSE), 166 (KEY_STOPCD), 165 (KEY_PREVIOUSSONG) and 163 (KEY_NEXTSONG), accordingly Fn+Space generated no events in evtest, but caused keyboard backlight cycle through medium level, high level and back off. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 Status in linux package in Ubuntu: Incomplete Bug description: The keys marked for brightness control on the keyboard are supposed to be Fn+F5 (down) and Fn+F6 (up). But pressing them does not have any effects. Volume control keys Fn+F1 (off), Fn+F2 (down), Fn+F3 (up) all do work, and KDE shows appropriate indicators when they are pressed. I know this is a popular problem with Lenovo laptops. I use Ubuntu 21.04 Hirsute on built-in NVMe, but Ubuntu 20.04 booted from USB flash drive also does not allow me to control screen brightness. Hardware and OS information will be collected on Apport request and attached here. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mwg1006 F pulseaudio mwg1010 F pipewire-media- /dev/snd/seq:mwg1005 F pipewire BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Ubuntu 21.04 DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G1 (Ice Lake) [17aa:3fd9] HibernationDevice: #RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc RESUME=UUID=ce49bc01-a59b-4abf-9110-87bc71689769 InstallationDate: Installed on 2009-11-01 (4055 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: LENOVO 81YK NonfreeKernelModules: wl Package: xorg 1:7.7+19ubuntu15 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-31-generic root=/dev/mapper/vg_c540scadaw-root64 ro rootflags=commit=3600 transparent_hugepage=always init=/lib/systemd/systemd ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A linux-firmware1.192 Tags: hirsute ubuntu single-occurrence reproducible has-workaround Uname: Linux 5.8.0-31-generic x86_64 UpgradeStatus: No
[Kernel-packages] [Bug 1473723] 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 1473723 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/1473723 Title: Elantech 0501 touch pad bug Status in linux package in Ubuntu: Incomplete Bug description: A lot of modern laptop use Elantech 0501 touch pad. One properly works only with 3.13 kernels. A have found that only one, higher than 3.13 is 3.18.7. The rest of kernels does not work properly. It means that there are problems with Click and marking text or touch pad do not work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907808] 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/1907808 Title: my mouse isnt alway working Status in linux package in Ubuntu: Confirmed Bug description: I am using a macbook pro for this ubuntu distro on a 61 gb partition. I realize macbooks are terrible for linux however I felt like giving it a try, the trackpad was working on some start ups but seems not to be anymore at all. I saw online that reporting this issue is possible from terminal, so i figured it would be the correct thing to do. Anyway I shall try to find a solution now 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.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: felix 1036 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 11 12:30:12 2020 InstallationDate: Installed on 2020-12-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M MachineType: Apple Inc. MacBookPro14,1 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=18a8c951-82bf-4733-8f17-b447f26b0e8e 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.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 429.50.1.0.0 dmi.board.name: Mac-B4831CEBD52A0C4C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B4831CEBD52A0C4C dmi.modalias: dmi:bvnAppleInc.:bvr429.50.1.0.0:bd10/19/2020:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907808] [NEW] my mouse isnt alway working
Public bug reported: I am using a macbook pro for this ubuntu distro on a 61 gb partition. I realize macbooks are terrible for linux however I felt like giving it a try, the trackpad was working on some start ups but seems not to be anymore at all. I saw online that reporting this issue is possible from terminal, so i figured it would be the correct thing to do. Anyway I shall try to find a solution now 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.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: felix 1036 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 11 12:30:12 2020 InstallationDate: Installed on 2020-12-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M MachineType: Apple Inc. MacBookPro14,1 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=18a8c951-82bf-4733-8f17-b447f26b0e8e 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.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 429.50.1.0.0 dmi.board.name: Mac-B4831CEBD52A0C4C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B4831CEBD52A0C4C dmi.modalias: dmi:bvnAppleInc.:bvr429.50.1.0.0:bd10/19/2020:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907808 Title: my mouse isnt alway working Status in linux package in Ubuntu: Confirmed Bug description: I am using a macbook pro for this ubuntu distro on a 61 gb partition. I realize macbooks are terrible for linux however I felt like giving it a try, the trackpad was working on some start ups but seems not to be anymore at all. I saw online that reporting this issue is possible from terminal, so i figured it would be the correct thing to do. Anyway I shall try to find a solution now 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.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: felix 1036 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 11 12:30:12 2020 InstallationDate: Installed on 2020-12-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M MachineType: Apple Inc. MacBookPro14,1 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=18a8c951-82bf-4733-8f17-b447f26b0e8e ro quiet splash vt.handoff=7 RelatedPackageVersions:
[Kernel-packages] [Bug 1473723] Re: Elantech 0501 touch pad bug
** Package changed: linux-kernel (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1473723 Title: Elantech 0501 touch pad bug Status in linux package in Ubuntu: Incomplete Bug description: A lot of modern laptop use Elantech 0501 touch pad. One properly works only with 3.13 kernels. A have found that only one, higher than 3.13 is 3.18.7. The rest of kernels does not work properly. It means that there are problems with Click and marking text or touch pad do not work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1473723] [NEW] Elantech 0501 touch pad bug
You have been subscribed to a public bug: A lot of modern laptop use Elantech 0501 touch pad. One properly works only with 3.13 kernels. A have found that only one, higher than 3.13 is 3.18.7. The rest of kernels does not work properly. It means that there are problems with Click and marking text or touch pad do not work at all. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Elantech 0501 touch pad bug https://bugs.launchpad.net/bugs/1473723 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900584] Re: Regression: suspend/wake-up no longer working properly
>From the nvidia package maintainer "it looks like the user installed the driver through the nvidia installer, and then used our packages. The perfect recipe for disaster." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1900584 Title: Regression: suspend/wake-up no longer working properly Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: With kernel 5.4.0-47.51, suspend (and resuming thereafter) works flawlessly. With 5.4.0-48.52 and later versions, the display refuses to wake up after a suspend. Display adaptor: Nvidia driver version: 440.100 Screens: 1 GPU: GeForce GT 710 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 1332 F pulseaudio /dev/snd/controlC0: craig 1332 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 20:15:38 2020 InstallationDate: Installed on 2020-09-04 (44 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enx582c80139263 no wireless extensions. lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=90130dae-9aab-4a03-9308-cf17561e3af2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 01TKCC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/24/2011:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn01TKCC:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
What's the "runtime_status" and "control" of device :01:00.1? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.10 which ships kernel 5.8.0-31-generic, battery life is considerably less and power consumption is about 10 watts more idle, (idling at 14-15 watts) using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and based on past experiences a possible cause is not powering off the dedicated GPU completely while using the integrated. Running sudo powertop --auto-tune doesn't eliminate the issue. $ cat /sys/bus/pci/devices/:01:00.0/power/runtime_status suspended $ cat /sys/bus/pci/devices/:01:00.0/power/runtime_suspended_time 1815948 $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_status active $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_suspended_time 3827 Device "01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller" appears active, does this mean that the audio subsystem of dGPU keeps it enabled, causing the 10-watt consumption? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
@Lucas, thank you for testing. We're, however, experiencing an issue that MHI device may become unresponsive after a few warm boots, ath11k stops further attempt to init, and it takes a cold boot to resolve. Reported. -- 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: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux-firmware source package in Groovy: In Progress 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] BugLink: https://bugs.launchpad.net/bugs/1879633 [Impact] Qualcomm QCA6390 series not recognized due to the lack of ath11k driver. $ lspci :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] [Fix] 25 additional fixes in ath tree (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms, and firmware updates from mainline are required. [Test Case] 1. Install firmwares & boot from patched kernel, 2. ath11k should be now up and running. Check with `sudo dmesg | grep ath11k` [Where problems could occur] There has been a lot patches landed in kernel since 5.7 devel cycle. The last bits here has merge base with mainline at v5.10-rc4, and since then only patches for ath11k itself has been committed. == Original Bug Description == Qualcomm QCA6390 series not recognized due to the lack of ath11k driver. :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1842 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=580a1e2b-9a42-4f3b-b20f-ddbed7b572f5 ro ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.6.0-1010-oem N/A linux-backports-modules-5.6.0-1010-oem N/A linux-firmware 1.187+lp1867862.1 RfKill: Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.9 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.9:bd05/14/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1879633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907523] Re: selftests: ftrace: linux ADT test failure with linux 5.4.0-57.63 Focal
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: ubuntu-kernel-selftests ** Tags added: 5.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907523 Title: selftests: ftrace: linux ADT test failure with linux 5.4.0-57.63 Focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20201209_050128_d377a@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20201209_061300_0aada@/log.gz Kprobe event user-memory access [FAIL] Have only spotted amd64 and arm64 on Focal 5.4.0-57.63 so far Possibly related to LP#1893024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1907523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907715] Re: Kernel 5.4.0.54.60 instalation failure on laptop HP EliteBook 8460p
Hi, in the warning message: gzip: stdout: No space left on device You might want to check your disk free space. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907715 Title: Kernel 5.4.0.54.60 instalation failure on laptop HP EliteBook 8460p Status in linux package in Ubuntu: Incomplete Bug description: Details of the error after installation. If I restart and the new kernel tries to get active, it does not boot up and I need to delete it and go to an old kernel 5.3... to get Linux mint 19.3 cinamon working again Selecting previously unselected package linux-modules-5.4.0-54-generic. (Reading database ... 503663 files and directories currently installed.) Preparing to unpack .../0-linux-modules-5.4.0-54-generic_5.4.0-54.60~18.04.1_amd64.deb ... Unpacking linux-modules-5.4.0-54-generic (5.4.0-54.60~18.04.1) ... Selecting previously unselected package linux-image-5.4.0-54-generic. Preparing to unpack .../1-linux-image-5.4.0-54-generic_5.4.0-54.60~18.04.1_amd64.deb ... Unpacking linux-image-5.4.0-54-generic (5.4.0-54.60~18.04.1) ... Selecting previously unselected package linux-modules-extra-5.4.0-54-generic. Preparing to unpack .../2-linux-modules-extra-5.4.0-54-generic_5.4.0-54.60~18.04.1_amd64.deb ... Unpacking linux-modules-extra-5.4.0-54-generic (5.4.0-54.60~18.04.1) ... Selecting previously unselected package linux-image-generic-hwe-18.04. Preparing to unpack .../3-linux-image-generic-hwe-18.04_5.4.0.54.60~18.04.48_amd64.deb ... Unpacking linux-image-generic-hwe-18.04 (5.4.0.54.60~18.04.48) ... Selecting previously unselected package linux-hwe-5.4-headers-5.4.0-54. Preparing to unpack .../4-linux-hwe-5.4-headers-5.4.0-54_5.4.0-54.60~18.04.1_all.deb ... Unpacking linux-hwe-5.4-headers-5.4.0-54 (5.4.0-54.60~18.04.1) ... Selecting previously unselected package linux-headers-5.4.0-54-generic. Preparing to unpack .../5-linux-headers-5.4.0-54-generic_5.4.0-54.60~18.04.1_amd64.deb ... Unpacking linux-headers-5.4.0-54-generic (5.4.0-54.60~18.04.1) ... Selecting previously unselected package linux-headers-generic-hwe-18.04. Preparing to unpack .../6-linux-headers-generic-hwe-18.04_5.4.0.54.60~18.04.48_amd64.deb ... Unpacking linux-headers-generic-hwe-18.04 (5.4.0.54.60~18.04.48) ... Selecting previously unselected package linux-generic-hwe-18.04. Preparing to unpack .../7-linux-generic-hwe-18.04_5.4.0.54.60~18.04.48_amd64.deb ... Unpacking linux-generic-hwe-18.04 (5.4.0.54.60~18.04.48) ... Setting up linux-modules-5.4.0-54-generic (5.4.0-54.60~18.04.1) ... Setting up linux-hwe-5.4-headers-5.4.0-54 (5.4.0-54.60~18.04.1) ... Setting up linux-headers-5.4.0-54-generic (5.4.0-54.60~18.04.1) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.4.0-54-generic ...done. Setting up linux-image-5.4.0-54-generic (5.4.0-54.60~18.04.1) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.3.0-62-generic I: /initrd.img.old is now a symlink to boot/initrd.img-5.3.0-62-generic I: /vmlinuz is now a symlink to boot/vmlinuz-5.4.0-54-generic I: /initrd.img is now a symlink to boot/initrd.img-5.4.0-54-generic Setting up linux-headers-generic-hwe-18.04 (5.4.0.54.60~18.04.48) ... Setting up linux-modules-extra-5.4.0-54-generic (5.4.0-54.60~18.04.1) ... Setting up linux-image-generic-hwe-18.04 (5.4.0.54.60~18.04.48) ... Setting up linux-generic-hwe-18.04 (5.4.0.54.60~18.04.48) ... Processing triggers for linux-image-5.4.0-54-generic (5.4.0-54.60~18.04.1) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.4.0-54-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-54-generic W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915 I: The initramfs will attempt to resume from /dev/sdb3 I: (UUID=3f5060fc-56bf-4ce8-a0c9-34b5e9558a7d) I: Set the RESUME variable to override this. gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-5.4.0-54-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-5.4.0-54-generic (--configure): installed linux-image-5.4.0-54-generic package
[Kernel-packages] [Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
Dmesg after booting with provided kernel https://people.canonical.com/~khfeng/lp1907212/ High power consumption remains, `echo :01:00.1 | sudo tee /sys/module/snd_hda_intel/drivers/pci:snd_hda_intel/unbind` works. ** Attachment added: "dmesg_5.8.0-35-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+attachment/5442741/+files/dmesg_5.8.0-35-generic.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/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.10 which ships kernel 5.8.0-31-generic, battery life is considerably less and power consumption is about 10 watts more idle, (idling at 14-15 watts) using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and based on past experiences a possible cause is not powering off the dedicated GPU completely while using the integrated. Running sudo powertop --auto-tune doesn't eliminate the issue. $ cat /sys/bus/pci/devices/:01:00.0/power/runtime_status suspended $ cat /sys/bus/pci/devices/:01:00.0/power/runtime_suspended_time 1815948 $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_status active $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_suspended_time 3827 Device "01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller" appears active, does this mean that the audio subsystem of dGPU keeps it enabled, causing the 10-watt consumption? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897963] Re: Cherry Pick needed for Critical upstream patch for Kernel null pointer dereference - usb-c altmode
This commit 386e15a650447f53de3d2d8819ce9393f31650a4 can be found in Hirsute as well. Closing this bug. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897963 Title: Cherry Pick needed for Critical upstream patch for Kernel null pointer dereference - usb-c altmode Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: Basically a null pointer dereference was happening while using a lenovo usb-c dock. The issue has been addressed upstream with commit: https://github.com/torvalds/linux/commit/386e15a650447f53de3d2d8819ce9393f31650a4 Apparently the dock kept sending altmode information repeatedly, and the kernel did not expect this to happen, a check was added to make sure it only observes the amount of altmodes limited by the standard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 15:40:24 2020 InstallationDate: Installed on 2020-09-30 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904529] Re: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot
Hello Xiyue Wang, Could you please try the latest bionic kernel from -proposed? The version would be linux-generic 4.15.0.128.115. Following are instructions on how to enable proposed: https://wiki.ubuntu.com/Testing/EnableProposed Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904529 Title: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The exactly the same behavior is observed when upgrade kernel to 4.15.0-123-generic. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834322 If we do 'ip link set dev bond2 down' and 'ip link set dev bond2 up', the port with the mismatched ID appears to renegotiate with the port- channel and becomes aggregated. ubuntu@vcd41025:~$ sudo lspci -vnvn https://pastebin.canonical.com/p/x56r4P6mGB/ ubuntu@vcd41025:~$ uname -a Linux vcd41025 4.15.0-123-generic #126-Ubuntu SMP Wed Oct 21 09:40:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Hardware: Dell PowerEdge R740xd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904529/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904529] Re: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904529 Title: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The exactly the same behavior is observed when upgrade kernel to 4.15.0-123-generic. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834322 If we do 'ip link set dev bond2 down' and 'ip link set dev bond2 up', the port with the mismatched ID appears to renegotiate with the port- channel and becomes aggregated. ubuntu@vcd41025:~$ sudo lspci -vnvn https://pastebin.canonical.com/p/x56r4P6mGB/ ubuntu@vcd41025:~$ uname -a Linux vcd41025 4.15.0-123-generic #126-Ubuntu SMP Wed Oct 21 09:40:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Hardware: Dell PowerEdge R740xd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904529/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899832] Re: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels
** Changed in: linux-kvm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1899832 Title: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Xenial: Fix Released Status in linux-kvm source package in Bionic: Fix Released Status in linux-kvm source package in Focal: Fix Released Status in linux-kvm source package in Groovy: Fix Released Bug description: CONFIG_NET_IPIP and CONFIG_IPV6_SIT are set to =y in the -kvm kernels. This means that they are always present in the kernel, and the virtual devices they created (tunl0 and sit0) are always present, even when not configured and not needed. This is causing some issues for clouds that use the -kvm flavour, and there is no good reason for those configuration options to be =y anyway. So they should be converted to =m instead. [Regression potential] - The only possible regression I can think of by compiling these as modules is the possibility that someone's boot setup somehow depended on IP tunneling. Such issues would need to be worked out by some initramfs means, etc. - After this change, the modules (ipip.ko, sit.ko) are present in linux-modules. - General consensus was that these options should have been =m all along. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1899832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894972] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with Groovy KVM kernel
Passed with 5.8.0-1012.13-kvm
Closing this bug.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
** Changed in: linux-kvm (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1894972
Title:
test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
with Groovy KVM kernel
Status in ubuntu-kernel-tests:
Fix Released
Status in linux-kvm package in Ubuntu:
Fix Released
Bug description:
Issue found on 5.8.0-1001.1 - kvm
FAIL: test_520_config_random_trust_cpu
(__main__.KernelSecurityConfigTest)
Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2928, in
test_520_config_random_trust_cpu
self.assertKernelConfig('RANDOM_TRUST_CPU', expected)
File "./test-kernel-security.py", line 214, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 201, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: RANDOM_TRUST_CPU option was expected to be set in the
kernel config
(Similar failure found with 5.0 before bug 1825280)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1894972/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo
There it is: https://lore.kernel.org/linux- media/CAO5W59geLtP7kHJkW=ELusAcd9==ceqhsuzznukfradtkxz...@mail.gmail.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827452 Title: null pointer dereference in uvcvideo Status in linux package in Ubuntu: Expired Bug description: I have a logitech c920 webcam. When using this camera in obs-studio v23.x, all of my USB devices stop working and I see the following in my kernel log: [ 590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd [ 592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 [ 592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 592.660925] usb 3-3: Product: HD Pro Webcam C920 [ 592.660928] usb 3-3: SerialNumber: 2EAD866F [ 592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) [ 592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not initialized! [ 592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not initialized! [ 592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not initialized! [ 592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not initialized! [ 592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not initialized! [ 592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not initialized! [ 592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not initialized! [ 592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not initialized! [ 592.22] input: HD Pro Webcam C920 as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23 [ 748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd [ 938.125745] usb 3-3: USB disconnect, device number 5 [ 943.298530] BUG: unable to handle kernel NULL pointer dereference at [ 943.298533] #PF error: [normal kernel read fault] [ 943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 [ 943.298536] Oops: [#1] SMP PTI [ 943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P OE 5.0.0-13-generic #14-Ubuntu [ 943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, BIOS F7 01/20/2014 [ 943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60 [ 943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48 [ 943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202 [ 943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 0004 [ 943.298547] RDX: RSI: 0001 RDI: a1070ad0a800 [ 943.298548] RBP: bdae493dbab0 R08: 00027040 R09: b57825b8 [ 943.298549] R10: fba45fce4bc0 R11: 0001 R12: [ 943.298550] R13: a10644187b98 R14: ff92 R15: a1075131a000 [ 943.298551] FS: 7f93c40d7700() GS:a1075ea0() knlGS: [ 943.298552] CS: 0010 DS: ES: CR0: 80050033 [ 943.298553] CR2: CR3: 0006f8a94004 CR4: 001606f0 [ 943.298553] Call Trace: [ 943.298557] usb_hcd_alloc_bandwidth+0x241/0x370 [ 943.298559] usb_set_interface+0xfc/0x380 [ 943.298565] uvc_video_start_transfer+0x155/0x4b0 [uvcvideo] [ 943.298568] uvc_video_start_streaming+0x7f/0xd0 [uvcvideo] [ 943.298570] uvc_start_streaming+0x28/0x70 [uvcvideo] [ 943.298573] vb2_start_streaming+0x6d/0x110 [videobuf2_common] [ 943.298575] vb2_core_streamon+0x59/0xc0 [videobuf2_common] [ 943.298578] vb2_streamon+0x18/0x30 [videobuf2_v4l2] [ 943.298580] uvc_queue_streamon+0x2e/0x50 [uvcvideo] [ 943.298582] uvc_ioctl_streamon+0x3f/0x60 [uvcvideo] [ 943.298588] v4l_streamon+0x20/0x30 [videodev] [ 943.298592] __video_do_ioctl+0x19a/0x3f0 [videodev] [ 943.298596] video_usercopy+0x1a6/0x660 [videodev] [ 943.298599] ? v4l_s_fmt+0x630/0x630 [videodev] [ 943.298603] video_ioctl2+0x15/0x20 [videodev] [ 943.298606] v4l2_ioctl+0x49/0x50 [videodev] [ 943.298608] do_vfs_ioctl+0xa9/0x640 [ 943.298610] ? __switch_to_asm+0x34/0x70 [ 943.298611] ? __switch_to_asm+0x40/0x70 [ 943.298612] ? __switch_to_asm+0x34/0x70 [ 943.298612] ? __switch_to_asm+0x40/0x70 [ 943.298613] ? __switch_to_asm+0x34/0x70 [ 943.298614] ? __switch_to_asm+0x40/0x70 [ 943.298615] ? __switch_to_asm+0x34/0x70 [ 943.298616] ? __switch_to_asm+0x40/0x70 [ 943.298617] ksys_ioctl+0x67/0x90 [ 943.298619] __x64_sys_ioctl+0x1a/0x20 [ 943.298621] do_syscall_64+0x5a/0x110 [ 943.298622] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [
[Kernel-packages] [Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm
Hello Louis, I can see this CONFIG_NF_TABLES got enabled in 5.4 KVM kernel now. $ grep CONFIG_NF_TABLES /boot/config-5.4.0-1026-kvm CONFIG_NF_TABLES=m CONFIG_NF_TABLES_SET=m CONFIG_NF_TABLES_INET=y CONFIG_NF_TABLES_NETDEV=y CONFIG_NF_TABLES_IPV4=y CONFIG_NF_TABLES_ARP=y CONFIG_NF_TABLES_IPV6=y CONFIG_NF_TABLES_BRIDGE=m Therefore I am going to close this bug, please feel free to open a new one if this is still not working for you. Thanks ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-kvm (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1880522 Title: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Focal: Fix Released Bug description: The NF_TABLES options are not included in the -kvm flavor of the 5.4 kernel. This package is used in the Ubuntu Cloud Image. The linux-image-5.4.0-31-generic package has the options present in the config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo
Yes this was the original thread. Alan was helpful and responsive but in the end he suggested I contact the uvcvideo maintainers which I did and got nowhere. https://lore.kernel.org/linux- usb/20201123152654.gb708...@rowland.harvard.edu/#t The 2nd patch was to uvcvideo maintainers Laurent Pinchart and linux- me...@vger.kernel.org and isn't archived. Maybe it never got through? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827452 Title: null pointer dereference in uvcvideo Status in linux package in Ubuntu: Expired Bug description: I have a logitech c920 webcam. When using this camera in obs-studio v23.x, all of my USB devices stop working and I see the following in my kernel log: [ 590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd [ 592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 [ 592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 592.660925] usb 3-3: Product: HD Pro Webcam C920 [ 592.660928] usb 3-3: SerialNumber: 2EAD866F [ 592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) [ 592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not initialized! [ 592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not initialized! [ 592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not initialized! [ 592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not initialized! [ 592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not initialized! [ 592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not initialized! [ 592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not initialized! [ 592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not initialized! [ 592.22] input: HD Pro Webcam C920 as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23 [ 748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd [ 938.125745] usb 3-3: USB disconnect, device number 5 [ 943.298530] BUG: unable to handle kernel NULL pointer dereference at [ 943.298533] #PF error: [normal kernel read fault] [ 943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 [ 943.298536] Oops: [#1] SMP PTI [ 943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P OE 5.0.0-13-generic #14-Ubuntu [ 943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, BIOS F7 01/20/2014 [ 943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60 [ 943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48 [ 943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202 [ 943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 0004 [ 943.298547] RDX: RSI: 0001 RDI: a1070ad0a800 [ 943.298548] RBP: bdae493dbab0 R08: 00027040 R09: b57825b8 [ 943.298549] R10: fba45fce4bc0 R11: 0001 R12: [ 943.298550] R13: a10644187b98 R14: ff92 R15: a1075131a000 [ 943.298551] FS: 7f93c40d7700() GS:a1075ea0() knlGS: [ 943.298552] CS: 0010 DS: ES: CR0: 80050033 [ 943.298553] CR2: CR3: 0006f8a94004 CR4: 001606f0 [ 943.298553] Call Trace: [ 943.298557] usb_hcd_alloc_bandwidth+0x241/0x370 [ 943.298559] usb_set_interface+0xfc/0x380 [ 943.298565] uvc_video_start_transfer+0x155/0x4b0 [uvcvideo] [ 943.298568] uvc_video_start_streaming+0x7f/0xd0 [uvcvideo] [ 943.298570] uvc_start_streaming+0x28/0x70 [uvcvideo] [ 943.298573] vb2_start_streaming+0x6d/0x110 [videobuf2_common] [ 943.298575] vb2_core_streamon+0x59/0xc0 [videobuf2_common] [ 943.298578] vb2_streamon+0x18/0x30 [videobuf2_v4l2] [ 943.298580] uvc_queue_streamon+0x2e/0x50 [uvcvideo] [ 943.298582] uvc_ioctl_streamon+0x3f/0x60 [uvcvideo] [ 943.298588] v4l_streamon+0x20/0x30 [videodev] [ 943.298592] __video_do_ioctl+0x19a/0x3f0 [videodev] [ 943.298596] video_usercopy+0x1a6/0x660 [videodev] [ 943.298599] ? v4l_s_fmt+0x630/0x630 [videodev] [ 943.298603] video_ioctl2+0x15/0x20 [videodev] [ 943.298606] v4l2_ioctl+0x49/0x50 [videodev] [ 943.298608] do_vfs_ioctl+0xa9/0x640 [ 943.298610] ? __switch_to_asm+0x34/0x70 [ 943.298611] ? __switch_to_asm+0x40/0x70 [ 943.298612] ? __switch_to_asm+0x34/0x70 [ 943.298612] ? __switch_to_asm+0x40/0x70 [ 943.298613] ? __switch_to_asm+0x34/0x70 [ 943.298614] ? __switch_to_asm+0x40/0x70 [ 943.298615] ?
[Kernel-packages] [Bug 1907432] Re: Raspberry Pi 400 Kernel Panic
** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Groovy) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Triaged ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1907432 Title: Raspberry Pi 400 Kernel Panic Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Groovy: Triaged Bug description: When I power the Pi 400 down (with the key-combination on the pi 400 or with the navigation from the top right), a line like this is on screen: [59095.049506] reboot: Power down or that: [25784.810857] reboot: Power down Under this line, the cursor is frozen. After a while, suddenly, the text scrolls and stops after a while. I can read something about "Kernel Panic" on screen. I cannot power the device off. I have to pull the power plug to shut it down, or to re-plug it to reset it. The power-button (2sec) does not work, 10 seconds reset signal, neither. Here you can find my initial question to this phenomenon: https://answers.launchpad.net/ubuntu/+question/694349 This I should include: Linux version 5.8.0-1008-raspi (buildd@bos02-arm64-062) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #11-Ubuntu SMP PREEMPT Thu Nov 12 15:49:32 UTC 2020 I hope this report includes enough information. If not, please do not hesitate to contact me! Thanks so much for this project and thx for being a part of it! <3 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-1008-raspi 5.8.0-1008.11 ProcVersionSignature: Ubuntu 5.8.0-1008.11-raspi 5.8.17 Uname: Linux 5.8.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 9 10:40:08 2020 ImageMediaBuild: 20201022 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1907432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
