[Kernel-packages] [Bug 1901975] 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/1901975 Title: After upgrade to 20.10 got audio dummy output Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 20.10 repeatly got audio dummy output ,when I use sudo alsa force_reload and reboot system the audio come back .But after some days the problom reappear use the same method solved the audio issue .It maybe the kernel bug with this issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dell 5398 F pulseaudio dell 5402 F pipewire-media- /dev/snd/controlC1: dell 5402 F pipewire-media- /dev/snd/seq:dell 5397 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Oct 29 12:33:05 2020 HibernationDevice: RESUME=UUID=0c70f08b-8e7f-4c5d-a9d5-a0846776436b InstallationDate: Installed on 2018-06-15 (867 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. G7 7590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu ro quiet splash pti=off nouveau.modeset=0 nouveau.runpm=0 i915.enable_psr=0 init_on_alloc=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-17 (11 days ago) dmi.bios.date: 05/22/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.2 dmi.board.name: 0YC5C7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.2:bd05/22/2020:br1.13:svnDellInc.:pnG77590:pvr:rvnDellInc.:rn0YC5C7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G7 7590 dmi.product.sku: 08EB dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-07-18T14:15:17 mtime.conffile..etc.logrotate.d.apport: 2020-10-26T16:26:26.813657 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901976] [NEW] Introduce support for Systems Management Driver over WMI for Dell Systems
Public bug reported: The Dell WMI Systems Management Driver provides a sysfs interface for systems management to enable BIOS configuration capability on certain Dell Systems. This driver allows user to configure Dell systems with a uniform common interface. To facilitate this, the patch introduces a generic way for driver to be able to create configurable BIOS Attributes available in Setup (F2) screen. [Impact] This provides a huge benefit to Dell machines users to be able to manipulate BIOS settings from within Ubuntu. [Fix] By the patches: https://www.spinics.net/lists/platform-driver-x86/msg23302.html Maintainer has merged the code to his branch: https://www.spinics.net/lists/platform-driver-x86/msg23313.html [Test Case] [Regression Risk] This is a new driver and self-contained. ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1901976 Title: Introduce support for Systems Management Driver over WMI for Dell Systems Status in linux-oem package in Ubuntu: New Bug description: The Dell WMI Systems Management Driver provides a sysfs interface for systems management to enable BIOS configuration capability on certain Dell Systems. This driver allows user to configure Dell systems with a uniform common interface. To facilitate this, the patch introduces a generic way for driver to be able to create configurable BIOS Attributes available in Setup (F2) screen. [Impact] This provides a huge benefit to Dell machines users to be able to manipulate BIOS settings from within Ubuntu. [Fix] By the patches: https://www.spinics.net/lists/platform-driver-x86/msg23302.html Maintainer has merged the code to his branch: https://www.spinics.net/lists/platform-driver-x86/msg23313.html [Test Case] [Regression Risk] This is a new driver and self-contained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1901976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901975] [NEW] After upgrade to 20.10 got audio dummy output
Public bug reported: After upgrade to 20.10 repeatly got audio dummy output ,when I use sudo alsa force_reload and reboot system the audio come back .But after some days the problom reappear use the same method solved the audio issue .It maybe the kernel bug with this issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dell 5398 F pulseaudio dell 5402 F pipewire-media- /dev/snd/controlC1: dell 5402 F pipewire-media- /dev/snd/seq:dell 5397 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Oct 29 12:33:05 2020 HibernationDevice: RESUME=UUID=0c70f08b-8e7f-4c5d-a9d5-a0846776436b InstallationDate: Installed on 2018-06-15 (867 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. G7 7590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu ro quiet splash pti=off nouveau.modeset=0 nouveau.runpm=0 i915.enable_psr=0 init_on_alloc=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-17 (11 days ago) dmi.bios.date: 05/22/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.2 dmi.board.name: 0YC5C7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.2:bd05/22/2020:br1.13:svnDellInc.:pnG77590:pvr:rvnDellInc.:rn0YC5C7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G7 7590 dmi.product.sku: 08EB dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-07-18T14:15:17 mtime.conffile..etc.logrotate.d.apport: 2020-10-26T16:26:26.813657 ** Affects: linux (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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1901975 Title: After upgrade to 20.10 got audio dummy output Status in linux package in Ubuntu: New Bug description: After upgrade to 20.10 repeatly got audio dummy output ,when I use sudo alsa force_reload and reboot system the audio come back .But after some days the problom reappear use the same method solved the audio issue .It maybe the kernel bug with this issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dell 5398 F pulseaudio dell 5402 F pipewire-media- /dev/snd/controlC1: dell 5402 F pipewire-media- /dev/snd/seq:dell 5397 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Oct 29 12:33:05 2020 HibernationDevice: RESUME=UUID=0c70f08b-8e7f-4c5d-a9d5-a0846776436b InstallationDate: Installed on 2018-06-15 (867 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. G7 7590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu ro quiet splash pti=off nouveau.modeset=0 nouveau.runpm=0 i915.enable_psr=0 init_on_alloc=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-17 (11 days ago) dmi.bios.date: 05/22/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.2 dmi.board.name: 0YC5C7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.2:bd05/22/2020:br1.13:svnDellInc.:pnG77590:pvr:rvnDellInc.:rn0YC5C7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G7 7590 dmi.product.sku: 08EB dmi.sys.vendor: Dell Inc.
[Kernel-packages] [Bug 1897694] Re: alsa/hda: mic doesn't work on a HP AIO machine
** Changed in: linux-oem-5.6 (Ubuntu) Status: In Progress => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- 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/1897694 Title: alsa/hda: mic doesn't work on a HP AIO machine Status in HWE Next: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: This fix is only for oem-5.6 kernel, other kernels will merge this patch with stable update. Our oem project needs this patch to be merged ASAP, and I am going to have a 8 days public holiday, so sent this SRU. [Impact] We had a HP AIO machine, after plugging the headset and trying to record sound from Mic, but can't record any sound. [Fix] Set the auto detect mode for Mic, this patch is going to be merged by upstream, now backport it to oem-5.6 kernel. [Test Case] Boot the system, plug a headset and check the gnome-control-center, the Mic is active in the UI, and record the sound, it could record the sound. [Regression Risk] This patch could introduce audio jack detection problem on this HP machine, but the possibility is very low, since we have tested it on 3 SKUs of this machine, all worked well. And this patch only affects this HP machine since it specifies the subsystem id of this machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1897694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901971] Re: alsa/hda: mic can't be detect if booting with headset plugged on a HP machine
** Description changed: - This bug is for tracking purpose. + Since this patch is cced to stable kernel, I only send this patch + to oem-5.6 kernel, other ubuntu kernels will merge this patch with + stable update. + + [Impact] + On a HP machine, if we plug a headset before booting, after booting + to the desktop, the mic can't be detected. + + [Fix] + Realtek engineer submit a patch to usptream, I backport this patch + to ubuntu oem kernel. + + [Test] + Plug a headset, then power on the machine, after entering the gnome, + check the mic, it is detected, and use mic to record, it could record + the sound. + + [Regression Potential] + I could make the sound on that HP machine not work, but this possibility + is very low and this regression possibility is limited to this HP machine + since this patch use pin definition to apply the quirk. -- 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/1901971 Title: alsa/hda: mic can't be detect if booting with headset plugged on a HP machine Status in HWE Next: In Progress Status in linux-oem-5.6 package in Ubuntu: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Bug description: Since this patch is cced to stable kernel, I only send this patch to oem-5.6 kernel, other ubuntu kernels will merge this patch with stable update. [Impact] On a HP machine, if we plug a headset before booting, after booting to the desktop, the mic can't be detected. [Fix] Realtek engineer submit a patch to usptream, I backport this patch to ubuntu oem kernel. [Test] Plug a headset, then power on the machine, after entering the gnome, check the mic, it is detected, and use mic to record, it could record the sound. [Regression Potential] I could make the sound on that HP machine not work, but this possibility is very low and this regression possibility is limited to this HP machine since this patch use pin definition to apply the quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1901971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853991] Re: Make hotplugging docking station to Thunderbolt port more reliable
** Changed in: linux-oem (Ubuntu) Status: New => Fix Released ** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Won't Fix ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1853991 Title: Make hotplugging docking station to Thunderbolt port more reliable Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] Sometimes USB ports and USB ethernet on Thunderbolt Docking don't work after hotplugging. [Fix] Add proper link delay when PCIe devices transit out from D3cold. [Test] Tested with Dell WD19DC docking station on Dell XPS 9380. After applying the fix, the USB ports on docking always work after hotplugging. [Regression Potential] Low. This patch series adds proper delay required by PCIe spec, and only affects hotplug ports, i.e. Thunderbolt. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866734] Re: All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
** Changed in: linux-oem (Ubuntu) Status: New => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1866734 Title: All PS/2 ports on PS/2 Serial add-in bracket are not working after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] PS/2 ports on PS/2 Serial add-in card do not work after S3. [Fix] The i8042 controller selftest fails while resuming, adding retry fix this issue. [Test] Verified on the target machine, the ps/2 keyboard keeps working after S3 test 30 times. [Regression Potential] Low, there is a retry logic in controller selftest, but it returns directly if it fails to communicate with the controller. This commit make it retry 5 times before return fails. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1866734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855312] Re: Fix unusable USB hub on Dell TB16 after S3
** Changed in: linux-oem (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-oem-osp1 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1855312 Title: Fix unusable USB hub on Dell TB16 after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] Sometimes USB hub on Dell TB16 stop working after S3. [Fix] Attempt to power cycle USB device when a it's stuck at eSS.Disabled state, it's basically not recoverable. [Test] After applying the patch, USB ports and USB ethernet are still working after 100 times S3 stress test. Tested on other platforms and didn't observe any regression. However, I have never seen any other USB device stuck in eSS.Disabled state, so the code path wasn't executed at all. [Regression Potential] Low. This is a last resort attempt, in most cases this code path won't be reached. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901971] [NEW] alsa/hda: mic can't be detect if booting with headset plugged on a HP machine
Public bug reported: Since this patch is cced to stable kernel, I only send this patch to oem-5.6 kernel, other ubuntu kernels will merge this patch with stable update. [Impact] On a HP machine, if we plug a headset before booting, after booting to the desktop, the mic can't be detected. [Fix] Realtek engineer submit a patch to usptream, I backport this patch to ubuntu oem kernel. [Test] Plug a headset, then power on the machine, after entering the gnome, check the mic, it is detected, and use mic to record, it could record the sound. [Regression Potential] I could make the sound on that HP machine not work, but this possibility is very low and this regression possibility is limited to this HP machine since this patch use pin definition to apply the quirk. ** Affects: hwe-next Importance: Undecided Status: In Progress ** Affects: linux-oem-5.6 (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Critical Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-1896580 stella ** Changed in: linux-oem-5.6 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-5.6 (Ubuntu) Importance: High => Critical ** Tags added: oem-priority originate-from-1896580 stella ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => In Progress ** Changed in: hwe-next Status: New => In Progress ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) -- 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/1901971 Title: alsa/hda: mic can't be detect if booting with headset plugged on a HP machine Status in HWE Next: In Progress Status in linux-oem-5.6 package in Ubuntu: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Bug description: Since this patch is cced to stable kernel, I only send this patch to oem-5.6 kernel, other ubuntu kernels will merge this patch with stable update. [Impact] On a HP machine, if we plug a headset before booting, after booting to the desktop, the mic can't be detected. [Fix] Realtek engineer submit a patch to usptream, I backport this patch to ubuntu oem kernel. [Test] Plug a headset, then power on the machine, after entering the gnome, check the mic, it is detected, and use mic to record, it could record the sound. [Regression Potential] I could make the sound on that HP machine not work, but this possibility is very low and this regression possibility is limited to this HP machine since this patch use pin definition to apply the quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1901971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor
** Changed in: linux-oem (Ubuntu) Status: New => Fix Released ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1835001 Title: System does not auto detect disconnection of external monitor Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux-oem source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] System does not auto detect disconnection of external monitor Steps to reproduce: 1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS 2. open "system settings > display settings" 3. connect laptop to an external HDMI monitor via HDMI port & cable 4. unplug the HDMI cable 5. check if "display settings" automatically detects the removal of the external monitor Expected result: display settings should automatically detect the removal of external monitor when unplugging the HDMI cable Actual result: System does not automatically detect the removal of the external monitor when HDMI cable is removed. Sound setting also list HDMI audio in output tab after removal external monitor. Failure rate: 2/10 to 1/10 [Fix] two commits from upstream drm-intel-next-queued branch [Test case] see "steps to reproduce" [Regression potential] still possible, but for the distro only Eoan will get it. OEM kernels will get tested on systems that get it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862313] Re: Support Headset Mic on HP cPC
** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Fix Released ** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux-oem (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1862313 Title: Support Headset Mic on HP cPC Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem source package in Focal: Won't Fix Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] Two HP workstations can't detect headset microphone. [Fix] Apply vendor-specific coefficient to enable headset mic detection. [Test] Plug headset and see if the mic gets detected. Headset mic gets detected correctly after applying the patch. [Regression Potential] Low. The fix matches to very specific machines, so all other systems are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1862313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859561] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native backlight on Lenovo E41-25/45
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859561 Title: [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native backlight on Lenovo E41-25/45 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: SRU justification: [Impact] ACPI backlight control doesn't work on 2 Lenovo E41 laptops. [Fix] Use native backlight control instead. [Test] Verified on hardware with a positive result. [Regression Potential] Low. Add new DMI strings with positive verification. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859561] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native backlight on Lenovo E41-25/45
** Changed in: linux-oem (Ubuntu) Status: New => Fix Released ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859561 Title: [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native backlight on Lenovo E41-25/45 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: SRU justification: [Impact] ACPI backlight control doesn't work on 2 Lenovo E41 laptops. [Fix] Use native backlight control instead. [Test] Verified on hardware with a positive result. [Regression Potential] Low. Add new DMI strings with positive verification. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848491] Re: drm/i915: Add support for another CMP-H PCH
** Changed in: linux-oem (Ubuntu) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Eoan) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1848491 Title: drm/i915: Add support for another CMP-H PCH Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] There's a new PCH model for Comet Lake, and drm/i915 needs to know about it or otherwise graphics won't work. [Test case] Check that i915 loads and works properly. [Regression potential] None, adds a new pci-id. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
Verified focal version 1.2.2-2.1ubuntu2.1 on the machine with legacy HDA audio design: Installed the alsa-utils 1.2.2-1ubuntu2, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is muted. Installed the proposed libasound2 1.2.2-2.1ubuntu2.1, repeat the above steps, the audio is not muted anymore. Verified Pass on the machine with legacy HDA audio design. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: Invalid Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this results in the failure on setting the init mixer values for HDA sound card, and users experience the mute of audio after installing the 20.10. [Fix] Backport a patch from the latest alsa-lib (v1.2.3+) [Test] Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is muted. Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is not muted. [Regression Potential] This could make the ucm audio fail to initialize, but this possibility is very low, since this patch is from upstream, and I tested on a ucm based machine, the audio is good. On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
About the #72, I opened the URL, can't find any error on asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf) introduced by new alsa-lib (1.2.2-2.1ubuntu2.1), looks like rebuild make the error disappear. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: Invalid Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this results in the failure on setting the init mixer values for HDA sound card, and users experience the mute of audio after installing the 20.10. [Fix] Backport a patch from the latest alsa-lib (v1.2.3+) [Test] Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is muted. Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is not muted. [Regression Potential] This could make the ucm audio fail to initialize, but this possibility is very low, since this patch is from upstream, and I tested on a ucm based machine, the audio is good. On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901134] Re: P620 reported TPM errors on Ubuntu 20.04
*** This bug is a duplicate of bug 1897207 *** https://bugs.launchpad.net/bugs/1897207 ** This bug has been marked a duplicate of private bug 1897207 -- 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/1901134 Title: P620 reported TPM errors on Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Hi, Thinkstation P620 will report TPM initial errors as follows on Ubuntu 20.04 ~~ root@lenovo-INVALID:~# dmesg | grep -i tpm [2.052240] tpm tpm0: tpm_try_transmit: send(): error -5 [2.052257] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead It seems to be TPM IRQ. The same P620 BIOS, such issue doesn't happen on other OS. Regards, Jiqi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901134] Re: P620 reported TPM errors on Ubuntu 20.04
*** This bug is a duplicate of bug 1897207 *** https://bugs.launchpad.net/bugs/1897207 duplicated as follows issues: https://bugs.launchpad.net/sutton/+bug/1897207 -- 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/1901134 Title: P620 reported TPM errors on Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Hi, Thinkstation P620 will report TPM initial errors as follows on Ubuntu 20.04 ~~ root@lenovo-INVALID:~# dmesg | grep -i tpm [2.052240] tpm tpm0: tpm_try_transmit: send(): error -5 [2.052257] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead It seems to be TPM IRQ. The same P620 BIOS, such issue doesn't happen on other OS. Regards, Jiqi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899993] Re: EFI: Fails when BootCurrent entry does not exist
Ah:
commit 336af6a4686d885a067ecea8c3c3dd129ba4fc75 (refs/bisect/bad)
Author: Michael Schaller
Date: Fri Sep 25 09:45:02 2020 +0200
efivarfs: Replace invalid slashes with exclamation marks in dentries.
Without this patch efivarfs_alloc_dentry creates dentries with slashes in
their name if the respective EFI variable has slashes in its name. This in
turn causes EIO on getdents64, which prevents a complete directory listing
of /sys/firmware/efi/efivars/.
This patch replaces the invalid shlashes with exclamation marks like
kobject_set_name_vargs does for /sys/firmware/efi/vars/ to have consistently
named dentries under /sys/firmware/efi/vars/ and /sys/firmware/efi/efivars/.
Signed-off-by: Michael Schaller
Link: https://lore.kernel.org/r/20200925074502.150448-1-mi...@google.com
Signed-off-by: Ard Biesheuvel
--
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/183
Title:
EFI: Fails when BootCurrent entry does not exist
Status in curtin package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Triaged
Bug description:
Split out of bug 1894217.
We're seeing a situation where curtin fails when the variable
BootCurrent references does not exist.
At boot, efibootmgr -v shows:
BootCurrent: 0003
Timeout: 10 seconds
BootOrder: 0003,0004,0005,0006,0001
Note that there are actually no individual boot entries in this
output. BootCurrent and BootOrder are referencing Boot entries that do
not apepar to exist.
Later, curtin tries to set a new BootOrder that places the value of
BootCurrent at the front. This causes efibootmgr to error out,
apparently escalating to an installation failure:
UEFI efibootmgr output after install:
{'current': '0003', 'timeout': '10 seconds', 'order': [''],
'entries': {'': {'name
': 'ubuntu', 'path':
'HD(1,GPT,0937ffdf-628c-4161-8b2f-5920235669c6,0x800,0x10)/File(\\EFI\\ub
untu\\shimx64.efi)'}}}
Setting currently booted 0003 as the first UEFI loader.
New UEFI boot order: 0003,
Running command ['mount', '--bind', '/dev',
'/tmp/tmp6ha4_iz2/target/dev'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/proc',
'/tmp/tmp6ha4_iz2/target/proc'] with allowed
return codes [0] (capture=False)
Running command ['mount', '--bind', '/run',
'/tmp/tmp6ha4_iz2/target/run'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys',
'/tmp/tmp6ha4_iz2/target/sys'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars',
'/tmp/tmp6ha4_iz2/target/
sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmp6ha4_iz2/target',
'efibootmgr', '-o', '0003,'] with allowed return codes [0] (capture=False)
Invalid BootOrder order entry value0003
^
efibootmgr: entry 0003 does not exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901470] 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/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280
[Kernel-packages] [Bug 1901885] 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 1901885 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/1901885 Title: [ASRock H270M-ITX/ac] Line output device unavailable on KDE after reboot Status in linux package in Ubuntu: Incomplete Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac 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.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac 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.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1901947] Re: Boot failure (black screen) when Nvidia GPU is enabled
It also appears your upgrade has not completed because you have an older kernel still active. To correct that please run: sudo apt update sudo apt install linux-generic sudo apt full-upgrade and reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901947 Title: Boot failure (black screen) when Nvidia GPU is enabled Status in linux package in Ubuntu: Incomplete Bug description: I have a lenovo ideapad 330 with and intel and a nvidia card geforce1050. The nvidia driver was not used, no nvidia files in /dev, no output on nvidia-smi. The logs that you seee are from a boot with the intel GPU only otherwise I cannot boot to xorg by deselecting software chooses GPU on Bios. If I go to recovery mode a go into CLI I can see the card detected in ubuntu-devices and nvidia-smi. If I continue the boot process from there I get a black screen and gets stuck there. No splash screen. Black. When the boot process freezes I can still switch Caps lock and Num lock so it is not completely dead but I left it for 30 minutes and it doesn't move. The dots in the spash screen (plymouth) stop after a minute and that's it. This behaviour was happening with 20.04 LTS so I upgraded to the new gorilla thing one and no changes except that pulseaudio now crashes and there is no sound input or output. 1 last point, I do not see any drivers in Additional drivers in the software center when I get to boot to xorg succesfully with Intel only GPU. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:20:51 2020 DistUpgraded: 2020-10-28 19:08:21,380 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.23.04, 5.4.0-52-generic, x86_64: installed nvidia, 455.23.04, 5.8.0-26-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b629 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 03f0:0941 HP, Inc X500 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=cddaf19f-5264-46b1-9acb-11810749ed99 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1901947] Re: Boot failure (black screen) when Nvidia GPU is enabled
Please reproduce a failed boot again (with Nvidia enabled). Then reboot with Intel only and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Summary changed: - Xorg freeze + Boot failure (black screen) when Nvidia GPU is enabled ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** 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/1901947 Title: Boot failure (black screen) when Nvidia GPU is enabled Status in linux package in Ubuntu: Incomplete Bug description: I have a lenovo ideapad 330 with and intel and a nvidia card geforce1050. The nvidia driver was not used, no nvidia files in /dev, no output on nvidia-smi. The logs that you seee are from a boot with the intel GPU only otherwise I cannot boot to xorg by deselecting software chooses GPU on Bios. If I go to recovery mode a go into CLI I can see the card detected in ubuntu-devices and nvidia-smi. If I continue the boot process from there I get a black screen and gets stuck there. No splash screen. Black. When the boot process freezes I can still switch Caps lock and Num lock so it is not completely dead but I left it for 30 minutes and it doesn't move. The dots in the spash screen (plymouth) stop after a minute and that's it. This behaviour was happening with 20.04 LTS so I upgraded to the new gorilla thing one and no changes except that pulseaudio now crashes and there is no sound input or output. 1 last point, I do not see any drivers in Additional drivers in the software center when I get to boot to xorg succesfully with Intel only GPU. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:20:51 2020 DistUpgraded: 2020-10-28 19:08:21,380 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.23.04, 5.4.0-52-generic, x86_64: installed nvidia, 455.23.04, 5.8.0-26-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b629 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 03f0:0941 HP, Inc X500 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=cddaf19f-5264-46b1-9acb-11810749ed99 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Kernel-packages] [Bug 1901947] Re: Boot failure (black screen) when Nvidia GPU is enabled
Also, keep an eye on bug 1872159 because the fix for that might help here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901947 Title: Boot failure (black screen) when Nvidia GPU is enabled Status in linux package in Ubuntu: Incomplete Bug description: I have a lenovo ideapad 330 with and intel and a nvidia card geforce1050. The nvidia driver was not used, no nvidia files in /dev, no output on nvidia-smi. The logs that you seee are from a boot with the intel GPU only otherwise I cannot boot to xorg by deselecting software chooses GPU on Bios. If I go to recovery mode a go into CLI I can see the card detected in ubuntu-devices and nvidia-smi. If I continue the boot process from there I get a black screen and gets stuck there. No splash screen. Black. When the boot process freezes I can still switch Caps lock and Num lock so it is not completely dead but I left it for 30 minutes and it doesn't move. The dots in the spash screen (plymouth) stop after a minute and that's it. This behaviour was happening with 20.04 LTS so I upgraded to the new gorilla thing one and no changes except that pulseaudio now crashes and there is no sound input or output. 1 last point, I do not see any drivers in Additional drivers in the software center when I get to boot to xorg succesfully with Intel only GPU. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:20:51 2020 DistUpgraded: 2020-10-28 19:08:21,380 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.23.04, 5.4.0-52-generic, x86_64: installed nvidia, 455.23.04, 5.8.0-26-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b629 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 03f0:0941 HP, Inc X500 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=cddaf19f-5264-46b1-9acb-11810749ed99 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1901885] Re: [ASRock H270M-ITX/ac] Line output device unavailable on KDE after reboot
** Summary changed: - line output device unailable on kde after reboot + [ASRock H270M-ITX/ac] Line output device unavailable on KDE after reboot ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Tags added: regression-release -- 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/1901885 Title: [ASRock H270M-ITX/ac] Line output device unavailable on KDE after reboot Status in linux package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac 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.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac 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.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac 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.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1901947] [NEW] Boot failure (black screen) when Nvidia GPU is enabled
You have been subscribed to a public bug: I have a lenovo ideapad 330 with and intel and a nvidia card geforce1050. The nvidia driver was not used, no nvidia files in /dev, no output on nvidia-smi. The logs that you seee are from a boot with the intel GPU only otherwise I cannot boot to xorg by deselecting software chooses GPU on Bios. If I go to recovery mode a go into CLI I can see the card detected in ubuntu-devices and nvidia-smi. If I continue the boot process from there I get a black screen and gets stuck there. No splash screen. Black. When the boot process freezes I can still switch Caps lock and Num lock so it is not completely dead but I left it for 30 minutes and it doesn't move. The dots in the spash screen (plymouth) stop after a minute and that's it. This behaviour was happening with 20.04 LTS so I upgraded to the new gorilla thing one and no changes except that pulseaudio now crashes and there is no sound input or output. 1 last point, I do not see any drivers in Additional drivers in the software center when I get to boot to xorg succesfully with Intel only GPU. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:20:51 2020 DistUpgraded: 2020-10-28 19:08:21,380 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.23.04, 5.4.0-52-generic, x86_64: installed nvidia, 455.23.04, 5.8.0-26-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b629 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 03f0:0941 HP, Inc X500 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=cddaf19f-5264-46b1-9acb-11810749ed99 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze groovy possible-manual-nvidia-install third-party-packages ubuntu -- Boot failure (black screen) when Nvidia GPU is enabled https://bugs.launchpad.net/bugs/1901947 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 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
Thanks. Looks like this is also a kernel bug... ** Summary changed: - resolution not listed in xrandr from ASUS ROG PG278QR via HDMI + [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => 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/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500
[Kernel-packages] [Bug 1901885] [NEW] [ASRock H270M-ITX/ac] Line output device unavailable on KDE after reboot
You have been subscribed to a public bug: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac 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.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac 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.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac 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.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac: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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected groovy package-from-proposed -- [ASRock H270M-ITX/ac] Line output device unavailable on KDE after reboot https://bugs.launchpad.net/bugs/1901885 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
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
It appears the kernel work is done and we are waiting on PulseAudio now. To join or monitor that conversation go to: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #776 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776 -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@smurf, After you switch the bt profile to hsp/hfp mode, please run hciconfig, let us see if the bt driver could recevie the sco packets? And BTW, what is your WiFi module's name (BT and WiFi usually co-exist on a physical module), I will check if there is a machine with the same module in our office. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Ok, Intel hardware has a solution, but other hardware? I have Realtek, has mentioned above, and the problem persist. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853050] Re: Realtek RTL8822BE [10ec:b822] Subsystem [1a3b:2950] Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)
Linux Jupiter 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Oct 25 12:07:25 Jupiter kernel: [ 36.542858] [ cut here ] Oct 25 12:07:25 Jupiter kernel: [ 36.542859] purge skb(s) not reported by firmware Oct 25 12:07:25 Jupiter kernel: [ 36.542877] WARNING: CPU: 11 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:162 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Oct 25 12:07:25 Jupiter kernel: [ 36.542878] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg ipt_REJECT nf_reject_ipv4 bnep xt_recent xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp xt_limit ipt able_filter bpfilter p_lkrg(OE) intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp nvidia_uvm(OE) kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd mei_hdcp nvidia_drm(POE) cryptd nvidia_modeset(POE) glue_helper snd_seq_midi snd_seq_midi _event snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_rawmidi snd_hda_intel snd_intel_dspcfg rtwpci snd_hda_codec rtw88 snd_hda_core snd_hwdep snd_pcm mac80211 btusb rapl snd_seq btrtl btbcm btintel eeepc_wmi snd_seq_device asus_wmi intel_cstate bluetooth s parse_keymap wmi_bmof mxm_wmi nvidia(POE) libarc4 snd_timer ecdh_generic joydev mei_me ecc input_leds mei drm_kms_helper snd fb_sys_fops syscopyarea sysfillrect soundcore sysimgblt mac_hid acpi_pad sch_fq overlay coretemp Oct 25 12:07:25 Jupiter kernel: [ 36.542906] tcp_bbr cfg80211 kyber_iosched bfq parport_pc ppdev lp parport drm ip_tables x_tables autofs4 xfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear hid_ge neric usbhid hid raid1 crc32_pclmul e1000e nvme ahci nvme_core libahci wmi video Oct 25 12:07:25 Jupiter kernel: [ 36.542914] CPU: 11 PID: 0 Comm: swapper/11 Tainted: P OE 5.4.0-52-generic #57-Ubuntu Oct 25 12:07:25 Jupiter kernel: [ 36.542914] Hardware name: System manufacturer System Product Name/ROG STRIX Z370-E GAMING, BIOS 2401 07/12/2019 Oct 25 12:07:25 Jupiter kernel: [ 36.542917] RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Oct 25 12:07:25 Jupiter kernel: [ 36.542918] Code: 0f 1f 44 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 98 09 1d c2 e8 e6 f5 b4 ed <0f> 0b 4c 8d 6b d8 4c 89 ef e8 7d 76 58 ee 48 8d 7b e0 49 89 c4 e8 Oct 25 12:07:25 Jupiter kernel: [ 36.542919] RSP: 0018:b0488035ce48 EFLAGS: 00010286 Oct 25 12:07:25 Jupiter kernel: [ 36.542919] RAX: RBX: 924689ba97f8 RCX: 0006 Oct 25 12:07:25 Jupiter kernel: [ 36.542920] RDX: 0007 RSI: 0082 RDI: 924696ad78c0 Oct 25 12:07:25 Jupiter kernel: [ 36.542920] RBP: b0488035ce60 R08: 04da R09: 0003 Oct 25 12:07:25 Jupiter kernel: [ 36.542921] R10: R11: 0001 R12: 924696adba80 Oct 25 12:07:25 Jupiter kernel: [ 36.542921] R13: 924689ba97f8 R14: c2152180 R15: 924689ba97f8 Oct 25 12:07:25 Jupiter kernel: [ 36.542921] FS: () GS:924696ac() knlGS: Oct 25 12:07:25 Jupiter kernel: [ 36.542922] CS: 0010 DS: ES: CR0: 80050033 Oct 25 12:07:25 Jupiter kernel: [ 36.542922] CR2: 7f463994d018 CR3: 000673a0a005 CR4: 003606e0 Oct 25 12:07:25 Jupiter kernel: [ 36.542923] DR0: DR1: DR2: Oct 25 12:07:25 Jupiter kernel: [ 36.542923] DR3: DR6: fffe0ff0 DR7: 0400 Oct 25 12:07:25 Jupiter kernel: [ 36.542924] Call Trace: Oct 25 12:07:25 Jupiter kernel: [ 36.542924] Oct 25 12:07:25 Jupiter kernel: [ 36.542927] call_timer_fn+0x32/0x130 Oct 25 12:07:25 Jupiter kernel: [ 36.542928] __run_timers.part.0+0x180/0x280 Oct 25 12:07:25 Jupiter kernel: [ 36.542930] ? timerqueue_add+0x9b/0xb0 Oct 25 12:07:25 Jupiter kernel: [ 36.542930] ? enqueue_hrtimer+0x3d/0x90 Oct 25 12:07:25 Jupiter kernel: [ 36.542932] ? recalibrate_cpu_khz+0x10/0x10 Oct 25 12:07:25 Jupiter kernel: [ 36.542932] ? ktime_get+0x3e/0xa0 Oct 25 12:07:25 Jupiter kernel: [ 36.542934] run_timer_softirq+0x2a/0x50 Oct 25 12:07:25 Jupiter kernel: [ 36.542934] __do_softirq+0xe1/0x2d6 Oct 25 12:07:25 Jupiter kernel: [ 36.542935] ? hrtimer_interrupt+0x13b/0x220 Oct 25 12:07:25 Jupiter kernel: [ 36.542937] irq_exit+0xae/0xb0 Oct 25 12:07:25 Jupiter kernel: [ 36.542937] smp_apic_timer_interrupt+0x7b/0x140 Oct 25 12:07:25 Jupiter kernel: [ 36.542938] apic_timer_interrupt+0xf/0x20 Oct 25 12:07:25 Jupiter kernel: [ 36.542938] Oct 25 12:07:25 Jupiter kernel: [ 36.542940] RIP: 0010:cpuidle_enter_state+0xc5/0x450 Oct 25 12:07:25 Jupiter kernel: [ 36.542940] Code: ff e8 bf cc 80 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f
[Kernel-packages] [Bug 1889637] Re: Raspberry Pi 3B hangs - dev_pm_opp_set_rate: failed to find current OPP, Failed to get throttled, Failed to change plib frequency; mmc timeout waiting for hardware
** Attachment added: "`apport-cli linux` output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889637/+attachment/5428751/+files/launchpad.bug
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1889637
Title:
Raspberry Pi 3B hangs - dev_pm_opp_set_rate: failed to find current
OPP, Failed to get throttled, Failed to change plib frequency; mmc
timeout waiting for hardware interrupt
Status in linux package in Ubuntu:
Confirmed
Bug description:
### uname -a (64-bit ARM, official image):
`Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020
aarch64 aarch64 aarch64 GNU/Linux`
### LSB release (Ubuntu *Server*, focal):
Description: Ubuntu 20.04.1 LTS
### Interesting packages installed
- zfs-dkms (with initramfs support) @ 0.8.3-1ubuntu12.2
* spl-dkms @ 0.8.3-1ubuntu12.2
- dphys-swapfile
### Hardware model:
Raspberry Pi 3 Model B
- 32 GiB SD card with root partition
* had a swap partition; now unused
* migrated to dphys-swapfile
- Attached 32 GiB USB stick as zpool for storage (not root FS)
- Current PSU reportedly outputs 2.4A supply for the Pi
* Still have occasional undervolt warnings (formally requires 2.5A)
* Lightning indicator not present however
- Connected over wireless networking
## Issue
- When under significant computational load at some point, the machine
appears to freeze.
* I usually log in in a headless manner via ssh, so externally the machine
is frozen and I need to pull the power cable
- Connectig the HDMI monitor the following messsages appear, in various
orders each time:
```terminal
cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq
9,223,372,036,854,775,698 ({illegible on my photograph, presumably -110})
hwmon hwmon1: Failed to get throttled (-110)
raspberrypi-clk firmware clocks: Failed to change plib frequency: -110
mmc0: timeout waiting for hardware interrupt
# mmc0 would be the root partition
### ... typically later on in the output
rcu: INFO: rcu_sched detected stalls on CPU/tasks
rcu: $1-...0: (1 GPs behind) idle=.../1/0x4{more 0s...}02
softirq=66377/66378 {or 26106/26107} fqs={this value varies}
INFO: task kworker/{...} blocked for more than 120 seconds
TAINTED: PWC OE 5.4.0-1015-raspi #15-ubuntu
watchdog: BUG: soft lockup - CPU #3 stuck for 22s!
```
The OPP frequency above looks to me like it may be the cause of the
issue, I have added the commas myself to the output but it would
appear to be a rubbish value;
[this](https://lkml.org/lkml/2020/7/24/683) mailing list archive I
found whilst searching for terms found in the messages appears to back
up my belief that we should be seeing a sensible CPU frequency here,
expressed in integer Hz; the above would be 9.2 EHz assuming Hertz are
the base unit, higher still if it's k/M/GHz etc. My most sensible
guess is this value has been brought up somewhere as garbage, and
understandably the system fails to scale the clock speed, with the
resultant crashes presumably due to this.
Beyond this point, there is no kernel panic, however the machine locks
up externally; does not respond to USB keyboard NumLock and is
invisible on the network, with more and more errors gradually being
output to the console via the HDMI display; the most notable being the
SD card is not responding
Just before encountering this issue I had added a swap aprtition, to
the SD card, as I had none by default and the system seemed to be
hanging when it presumably was sending bad_allocs to userland
processes as it failed to allocate memory. As the SD card was
mentioned, I have tried a variety of power supplies (as I was getting
several undervolt warnings) and eventually removed the swap partition
and used a swapfile with `dphys-swapfile` knowing that the way the Pi
accesses the SD card is somewhat different from a typical machine.
However, neither of these two seems to have resolved the issue, giving
further evidence that the frequency scaling may well be the primary
issue and the rest is simply the carnage that ensues.
## Steps to Reproduce
- Seems to happen sporadically when the machine is under stress, within 5-25
minutes
- Currently I am trying to set up a rootless docker compose file
* Attempting to pull the images eventually leads to the issue
* The images are being downloaded to the zpool on the USB stick and *not*
the SD card
- The system seems to hang initially waiting on the SDcard to respond to an
IRQ
- however I believe that the CPU scaling message seems to be the root cause
- Do not have any of the importat messages in the `syslog`, I need an
external HDMI monitor to get the output on screen from the kernel ring buffer
## Links
-
[Kernel-packages] [Bug 1878007] Re: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off
Experiencing the same problem with Ubuntu 20.04 on Dell Inspiron 7370 (Bios Version 1.13.1, but I don't know it matters.) -- 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/1878007 Title: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off Status in linux package in Ubuntu: Expired Bug description: This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron 7373. When the screen is turned off (so, the suspend or screen lock features are affected), the system freeze and I need to force the laptop turn off and on again. There are some cases when it turn off the screen without issues, but most of the time it freezes. Even "SysRq REISUB" does not work for rebooting when system crash. I can reproduce the issue using `xset dpms force off`. Initially this bug report was filled thinking it was a suspend issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144 Syslog or systemd journal does not provide any error information about the crash. "lsb_release -rd" output: Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cccaballero 2023 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-06-09 (344 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7373 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=d8203f53-c2e5-4934-8616-0a71507c9190 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-02 (16 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0JW0D6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd09/06/2019:svnDellInc.:pnInspiron7373:pvr:rvnDellInc.:rn0JW0D6:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7373 dmi.product.sku: 07EB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Update: I realized I forgot to test `5.9.0-2002.3+lp1879633.2`. This does not produce the same crash as the other 3 kernels, but it also fails to load any hardware drivers rendering the trackpad, brightness control, usb ethernet, and other hardware unusable in addition to the wlan. -- 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/1879633 Title: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable Status in HWE Next: New Status in linux package in Ubuntu: Incomplete 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: Incomplete Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: Invalid 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 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
It seems in both 20.04 and 20.10 placing the firmware files in `/lib/firmware/ath11k/QCA6390/hw2.0` causes the aforementioned kernels to hang on start up. I have tested all kernels linked in the above PPA as well as https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tag/?h=ath-202010281344 with the same result. Removing the firmware allows successful boot, but without the firmware files the WLAN card remains unusable. I tested this on both fresh installs of ubuntu and xubuntu 20.04 and 20.10 with the same results. -- 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/1879633 Title: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable Status in HWE Next: New Status in linux package in Ubuntu: Incomplete 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: Incomplete Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: Invalid 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 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.10-rc1. commit 2628089b74d5a64bd0bcb5d247a18f78d7b6f4d0 Author: Xiao Ni Date: Tue Aug 25 13:42:59 2020 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/2628089b74d5a64bd0bcb5d247a18f78d7b6f4d0 commit 8650a889017cb1f6ea6813ccf83a2e9f6fa49dd3 Author: Xiao Ni Date: Tue Aug 25 13:43:00 2020 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/8650a889017cb1f6ea6813ccf83a2e9f6fa49dd3 commit f046f5d0d79cdb968f219ce249e497fd1accf484 Author: Xiao Ni Date: Tue Aug 25 13:43:01 2020 +0800 Subject: md/raid10: pull codes that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f046f5d0d79cdb968f219ce249e497fd1accf484 commit bcc90d280465ebd51ab8688be86e1f00c62dccf9 Author: Xiao Ni Date: Wed Sep 2 20:00:22 2020 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/bcc90d280465ebd51ab8688be86e1f00c62dccf9 commit d3ee2d8415a6256c1c41e1be36e80e640c3e6359 Author: Xiao Ni Date: Wed Sep 2 20:00:23 2020 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/d3ee2d8415a6256c1c41e1be36e80e640c3e6359 There is also an additional commit which is required, and was merged after "md/raid10: improve raid10 discard request" was merged. The following commits enable Radid10 to use large discards, instead of splitting into many bios, since the technical hurdles have now been removed. commit e0910c8e4f87bb9f767e61a778b0d9271c4dc512 Author: Mike Snitzer Date: Thu Sep 24 13:14:52 2020 -0400 Subject: dm raid: fix discard limits for raid1 and raid10 Link: https://github.com/torvalds/linux/commit/e0910c8e4f87bb9f767e61a778b0d9271c4dc512 commit f0e90b6c663a7e3b4736cb318c6c7c589f152c28 Author: Mike Snitzer Date: Thu Sep 24 16:40:12 2020 -0400 Subject: dm raid: remove unnecessary discard limits for raid10 Link: https://github.com/torvalds/linux/commit/f0e90b6c663a7e3b4736cb318c6c7c589f152c28 All the commits mentioned follow a similar strategy which was implemented in Raid0 in the below commit, which was merged in 4.12-rc2, which fixed block discard performance issues in Raid0: commit 29efc390b9462582ae95eb9a0b8cd17ab956afc0 Author: Shaohua Li Date: Sun May 7 17:36:24 2017 -0700 Subject: md/md0: optimize raid0 discard handling Link: https://github.com/torvalds/linux/commit/29efc390b9462582ae95eb9a0b8cd17ab956afc0 The commits more or less cherry pick to the 5.8, 5.4 and 4.15 kernels, with the following minor fixups: 1)
[Kernel-packages] [Bug 1899993] Re: EFI: Fails when BootCurrent entry does not exist
I tried to prove whether or not this is a firmware issue or, perhaps, a
bug in efibootmgr or curtin's calling of it. I deployed an affected
system w/ MAAS w/ init=/bin/bash on the cmdline, and was surprised to
see that efibootmgr showed the full expected set of Boot variables.
However, if I ssh'd in while MAAS was deploying, efibootmgr was missing
some. Turns out this depends on which virtual file system efibootmgr is
using.
efivarfs is commonly mounted under /sys/firmware/efi/efivars, and is
what efibootmgr prefers:
$ ls /sys/firmware/efi/efivars | grep ^Boot
ls: reading directory '/sys/firmware/efi/efivars': Input/output error
Boot mode select-7683c190-9523-4402-81ff-a11e93dc389c
Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
If /sys/firmware/efi/efivars is not there, efibootmgr appears to
fallback to /sys/firmware/efi/vars which the kernel always exposes:
$ ls /sys/firmware/efi/vars | grep ^Boot
Boot mode select-7683c190-9523-4402-81ff-a11e93dc389c
Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0006-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
With init=/bin/bash, efivarfs is not yet mounted, which is why I see the
full set at that point.
So why are these variables not visible in efivarfs? And does the
"Input/output error" ls reports have something to do with it?
strace shows that the -EIO is coming from a getdents64() call:
openat(AT_FDCWD, "/sys/firmware/efi/efivars/",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
getdents64(3, /* 65 entries */, 32768) = 4800
getdents64(3, 0x5625e2d36510, 32768)= -1 EIO (Input/output error)
I built a 5.10-rc1+ kernel to see if this is maybe a kernel but that was
already fixed upstream.
Turns out, the issue goes away there:
$ ls /sys/firmware/efi/efivars | grep ^Boot
Boot mode select-7683c190-9523-4402-81ff-a11e93dc389c
Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0006-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
I'm now trying to determine what changed in the kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
EFI: Fails when BootCurrent entry does not exist
Status in curtin package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Triaged
Bug description:
Split out of bug 1894217.
We're seeing a situation where curtin fails when the variable
BootCurrent references does not exist.
At boot, efibootmgr -v shows:
BootCurrent: 0003
Timeout: 10 seconds
BootOrder: 0003,0004,0005,0006,0001
Note that there are actually no individual boot entries in this
output. BootCurrent and BootOrder are referencing Boot entries that do
not apepar to exist.
Later, curtin tries to set a new BootOrder that places the value of
BootCurrent at the front. This causes efibootmgr to error out,
apparently escalating to an installation failure:
UEFI efibootmgr output after install:
{'current': '0003', 'timeout': '10 seconds', 'order': [''],
'entries': {'': {'name
': 'ubuntu', 'path':
'HD(1,GPT,0937ffdf-628c-4161-8b2f-5920235669c6,0x800,0x10)/File(\\EFI\\ub
untu\\shimx64.efi)'}}}
Setting currently booted 0003 as the first UEFI loader.
New UEFI boot order: 0003,
Running command ['mount', '--bind', '/dev',
'/tmp/tmp6ha4_iz2/target/dev'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/proc',
'/tmp/tmp6ha4_iz2/target/proc'] with allowed
return codes [0] (capture=False)
Running command ['mount', '--bind', '/run',
'/tmp/tmp6ha4_iz2/target/run'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys',
'/tmp/tmp6ha4_iz2/target/sys'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars',
'/tmp/tmp6ha4_iz2/target/
sys/firmware/efi/efivars'] with allowed return codes [0]
[Kernel-packages] [Bug 1895406] Re: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1895406 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: gfx card NVIDIA RTX 2070 8 GB VRAM ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 12 14:44:52 2020 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-09-12 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1895406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901139] Re: No Intel HD sound 9th Gen Acer Swift 3 Notebook (possibly others)
Updated Linux image 5.8.0-26 also not working. ** Description changed: Just upgraded from Kubuntu 20.04 to 20.10 to find no audio device detected. lsmod shows module loaded, but alsa/pulse/etc is not picking up the audio device. If I boot using the old kernel that was left behind, it works (5.4.0-52 from 20.04). It does not work with shipped - kernel (5.8.0-52) & does not work with kernel 5.9.1-050901 (the current + kernel (5.8.0-25) & does not work with kernel 5.9.1-050901 (the current unsigned kernel from mainline). lspci shows the device regardless of what I boot. lsmod also shows the driver loading, but I don't see the codec portion of the driver loading on the current and testing kernels. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.25.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: andrew 1108 F pulseaudio - andrew 1112 F pipewire-media- - /dev/snd/seq:andrew 1107 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: andrew 1108 F pulseaudio + andrew 1112 F pipewire-media- + /dev/snd/seq:andrew 1107 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Oct 23 00:59:27 2020 InstallationDate: Installed on 2019-11-16 (341 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Swift SF315-52G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=821af7d8-e605-4db1-aaef-f6d17905aeec ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-52-generic N/A - linux-backports-modules-5.4.0-52-generic N/A - linux-firmware1.190 + linux-restricted-modules-5.4.0-52-generic N/A + linux-backports-modules-5.4.0-52-generic N/A + linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago) dmi.bios.date: 12/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.08 dmi.board.asset.tag: Default string dmi.board.name: Erdinger_KL dmi.board.vendor: KBL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.08:bd12/21/2018:svnAcer:pnSwiftSF315-52G:pvrV1.08:rvnKBL:rnErdinger_KL:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Swift 3 dmi.product.name: Swift SF315-52G dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer -- 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/1901139 Title: No Intel HD sound 9th Gen Acer Swift 3 Notebook (possibly others) Status in linux package in Ubuntu: Confirmed Bug description: Just upgraded from Kubuntu 20.04 to 20.10 to find no audio device detected. lsmod shows module loaded, but alsa/pulse/etc is not picking up the audio device. If I boot using the old kernel that was left behind, it works (5.4.0-52 from 20.04). It does not work with shipped kernel (5.8.0-25) & does not work with kernel 5.9.1-050901 (the current unsigned kernel from mainline). lspci shows the device regardless of what I boot. lsmod also shows the driver loading, but I don't see the codec portion of the driver loading on the current and testing kernels. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.25.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 1108 F pulseaudio andrew 1112 F pipewire-media- /dev/snd/seq:andrew 1107 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Oct 23 00:59:27 2020 InstallationDate: Installed on 2019-11-16 (341 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Swift SF315-52G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=821af7d8-e605-4db1-aaef-f6d17905aeec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago) dmi.bios.date: 12/21/2018
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
The issue is still reproducible under 20.10 i.e. under kernel
5.8.0-26-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
How do we get the Kernel maintainers to approve the remaining patches? I thought it might be fixed in 20.10 (KUbuntu), but it is not. I would think there is at least one kernel approver within Canonical? If not, who do I get in touch to talk about this? -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901779] Re: Wireless-AC 9560 not working after reboot
** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428132/+files/Lsusb.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428126/+files/AlsaInfo.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428127/+files/CRDA.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428128/+files/CurrentDmesg.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428129/+files/IwConfig.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428130/+files/Lspci.txt ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428131/+files/Lspci-vt.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428133/+files/Lsusb-t.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428134/+files/Lsusb-v.txt ** Attachment removed: "PaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428135/+files/PaInfo.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428136/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428137/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428138/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428139/+files/ProcModules.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428140/+files/RfKill.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428141/+files/UdevDb.txt ** Attachment removed: "acpidump.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+attachment/5428143/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901779 Title: Wireless-AC 9560 not working after reboot Status in linux package in Ubuntu: Confirmed Bug description: Hello. I had Laptop Dell Inspiron 7786 Ubuntu 5.8.0-25.26-generic 5.8.14 After turn down and start the system WiFi work normally. Kernel boot log: iwlwifi :00:14.3: enabling device ( -> 0002) iwlwifi :00:14.3: WRT: Overriding region id 0 iwlwifi :00:14.3: WRT: Overriding region id 1 iwlwifi :00:14.3: WRT: Overriding region id 2 iwlwifi :00:14.3: WRT: Overriding region id 3 iwlwifi :00:14.3: WRT: Overriding region id 4 iwlwifi :00:14.3: WRT: Overriding region id 6 iwlwifi :00:14.3: WRT: Overriding region id 8 iwlwifi :00:14.3: WRT: Overriding region id 9 iwlwifi :00:14.3: WRT: Overriding region id 10 iwlwifi :00:14.3: WRT: Overriding region id 11 iwlwifi :00:14.3: WRT: Overriding region id 15 iwlwifi :00:14.3: WRT: Overriding region id 16 iwlwifi :00:14.3: WRT: Overriding region id 18 iwlwifi :00:14.3: WRT: Overriding region id 19 iwlwifi :00:14.3: WRT: Overriding region id 20 iwlwifi :00:14.3: WRT: Overriding region id 21 iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM iwlwifi :00:14.3: Found debug configuration: 0 iwlwifi :00:14.3: loaded firmware version 46.8902351f.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm iwlwifi :00:14.3: Direct firmware load for iwl-debug-yoyo.bin failed with error -2 iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x318 iwlwifi :00:14.3: base HW address: 18:1d:ea:7e:f4:4b iwlwifi :00:14.3 wlo1: renamed from wlan0 But if I reboot the system I got "No WiFi Adapter available" Kernel boot log (after reboot): iwlwifi :00:14.3: enabling device ( -> 0002) iwlwifi :00:14.3: WRT: Overriding region id 0 iwlwifi :00:14.3: WRT: Overriding region id 1 iwlwifi :00:14.3: WRT: Overriding region id 2 iwlwifi :00:14.3: WRT: Overriding region id 3 iwlwifi :00:14.3: WRT: Overriding region id 4 iwlwifi :00:14.3: WRT: Overriding region id 6 iwlwifi :00:14.3: WRT: Overriding region id 8 iwlwifi :00:14.3: WRT: Overriding region id 9 iwlwifi :00:14.3: WRT: Overriding region id 10 iwlwifi :00:14.3: WRT: Overriding region id 11 iwlwifi :00:14.3: WRT: Overriding
Re: [Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I've got a DG60 dongle (a slightly bigger cousin), and my experiences with a headset that does only have SBC/MP3 codecs (Aftershokz Aeropex) - It switches attached to my Linux (Ubuntu 18.04) automatically to HFP/HSP profile (mono + microphone, but in good quality) when my laptop starts to use the microphone. - You can switch mode manually (for the very seldom case where it somehow does not realize that it should switch). Andreas Am Mi., 28. Okt. 2020 um 19:30 Uhr schrieb Falc <1838...@bugs.launchpad.net >: > I can only speak to the one that I linked, but yes it has talk/list > switch. The talk mode is only for talking (the music quality is BAD), > the lisen mode is only for listening (the music quality is good). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1838151 > > Title: > Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing > wide band speech support (Bluetooth A2DP codecs). > > To manage notifications about this bug go to: > https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions > -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I can only speak to the one that I linked, but yes it has talk/list switch. The talk mode is only for talking (the music quality is BAD), the lisen mode is only for listening (the music quality is good). -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Have a question about USB bluetooth transmitters mentioned above. Both models include Talk/Listen switches. Do you have to use them to get decent quality for music and for calls? Or is music quality good even in Talk mode? -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Hui: thanks for the update :) @Benny: the issue with pulseaudio and bt sound quality is a neverending story... e.g.: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776 https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838151 I'm considering an USB audio adapter (as someone is suggesting in the other threads) since it's almost impossible to have a decent conversation using my laptop and my bt headset... ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #776 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776 -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901919] Re: Missing module bochs-drm: no display on QEMU -vga std
** Description changed: The bochs-drm module is not enabled in the build config of the linux-kvm kernel. Therefore, there is no display output when running in QEMU with -vga std. The image I used is focal-server-cloudimg-amd64-disk-kvm.img from cloud-images.ubuntu.com. + Steps to reproduce: + 1. curl -LO https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img + 2. qemu-system-x86_64 -enable-kvm -hda focal-server-cloudimg-amd64-disk-kvm.img -vga std + 3. Observe the screen stay on the boot message + + The missing Kconfig is CONFIG_DRM_BOCHS=y Ubuntu release: Ubuntu 20.04.1 LTS linux-kvm version: 5.4.0.1026.24 (amd64) + + Corresponding bug for the linux package: + https://bugs.launchpad.net/bugs/1872863 -- 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/1901919 Title: Missing module bochs-drm: no display on QEMU -vga std Status in linux-kvm package in Ubuntu: New Bug description: The bochs-drm module is not enabled in the build config of the linux- kvm kernel. Therefore, there is no display output when running in QEMU with -vga std. The image I used is focal-server-cloudimg-amd64-disk-kvm.img from cloud-images.ubuntu.com. Steps to reproduce: 1. curl -LO https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img 2. qemu-system-x86_64 -enable-kvm -hda focal-server-cloudimg-amd64-disk-kvm.img -vga std 3. Observe the screen stay on the boot message The missing Kconfig is CONFIG_DRM_BOCHS=y Ubuntu release: Ubuntu 20.04.1 LTS linux-kvm version: 5.4.0.1026.24 (amd64) Corresponding bug for the linux package: https://bugs.launchpad.net/bugs/1872863 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1901919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901919] [NEW] Missing module bochs-drm: no display on QEMU -vga std
Public bug reported: The bochs-drm module is not enabled in the build config of the linux-kvm kernel. Therefore, there is no display output when running in QEMU with -vga std. The image I used is focal-server-cloudimg-amd64-disk-kvm.img from cloud-images.ubuntu.com. The missing Kconfig is CONFIG_DRM_BOCHS=y Ubuntu release: Ubuntu 20.04.1 LTS linux-kvm version: 5.4.0.1026.24 (amd64) ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- 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/1901919 Title: Missing module bochs-drm: no display on QEMU -vga std Status in linux-kvm package in Ubuntu: New Bug description: The bochs-drm module is not enabled in the build config of the linux- kvm kernel. Therefore, there is no display output when running in QEMU with -vga std. The image I used is focal-server-cloudimg-amd64-disk-kvm.img from cloud-images.ubuntu.com. The missing Kconfig is CONFIG_DRM_BOCHS=y Ubuntu release: Ubuntu 20.04.1 LTS linux-kvm version: 5.4.0.1026.24 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1901919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Hui Wang After I powered off the machine instead of a reboot, the HSP/HFP mode is now working. However there are two things to note, that might be related to this problem: 1. In the sound settings menu (I'm using Linux Mint Ulyana) I cannot play a test sound in HSP/HFP mode, only in A2DP mode. 2. The sound quality is significantly worse when using HSP/HFP. It really sounds like using a telephone / landline connection. As soon as I switch to A2DP, the sound ist normal again. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Update: If the bluetooth module is 8087:0029 or 8087:0026, the firmware in the 20.04 has some problem, we need to update the firmware, and I found the most import is *.ddc instead of *.sfi, For 8087:0029, please update ibt-20-1-3.sfi and ibt-20-1-3.ddc from 20.10 or latest upstream For 8087:0026, please update ibt-19-0-4.sfi and ibt-19-0-4.ddc from 20.10 or latest upstream After update, please poweroff the machine (not reboot), this could guarantee the bt driver will reload the firmware (sfi and ddc), then power on the machine, test the hsp/hfp mode. I have tested, after update the ddc, hsp/hfp could work with 8087:0029 and 8087:0026 now. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Marco and Hui Wang My Dell Latitude 5411 also contains an Intel BT Module 8087:0026. I can also reproduce the problem with my Sony WH-CH700N headphones. A2DP is fine, HSP/HFP is broken. I also tried Marco's fix and copied the newer firmware (https://launchpad.net/ubuntu/+source/linux-firmware/1.190) for ibt-19-0-4, but just like Hui Wang the problem still exists. I can also confirm the hciconfig behaviour, every time I switch to HSP/HFP, the TX sco counter increases by one, but the RX sco counter stays at 0. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Marco On my machine with BT moudle 8087:0026, I reproduced the problem, and replaced with 20.10 firmware ibt-19-0-4.sfi, but still could not work in hsp/hfp mode. What I found is the bt driver can't receive the SCO packet, the returned packet length is always 0. And if the bt headset can't work in the hsp/hfp mode, please run hci config, if the output like below (RX bytes: sco:0 TX bytes: sco:1), that means the bt driver can't receive SCO packets, as a result the headset can't work in hsp/hfp mode since hsp/hfp mode depends on SCO link. hci0: Type: Primary Bus: USB BD Address: D4:D2:52:3D:49:E6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:23638 acl:85 sco:0 events:3463 errors:0 TX bytes:980646 acl:323 sco:1 commands:3121 errors:0 -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
For those who are using the laptop with Intel BT module 8087:0029: The firmware in the current 20.04 is: md5sum 8cadd1fa93ab9790f61165f384466b0d ibt-20-1-3.sfi The firmware in the current 20.10 is: md5sum a2ebb8594804b5230a406b536804988c ibt-20-1-3.sfi The hsp/hfp could work in the 20.10 but couldn't work in the current 20.04 due to the firmware difference. There are 3 new commits applied to 20.10 firmware: commit b7849f7ccf268a909a80b090db131ab22ca160b9 Author: Kiran K Date: Fri Jul 10 19:51:29 2020 +0530 linux-firmware: Update firmware file for Intel Bluetooth AX200 This patch adds new firmware file for Intel Bluetooth AX200 Also it is known as Intel CyclonePeak (CcP). FW Build: REL9916 Release Version: 21.110.0.3 Signed-off-by: Kiran K Signed-off-by: Josh Boyer commit 887d2a103c2bdd267dbca5bed39b1b493d6cbe13 Author: Amit K Bag Date: Wed May 27 15:30:49 2020 +0530 linux-firmware: Update firmware file for Intel Bluetooth AX200 This patch updates new firmware file for Intel Bluetooth AX200 Also it is known as Intel CyclonePeak (CcP). FW Build: REL8301 Release Version: 21.90.3.2 Signed-off-by: Amit K Bag Signed-off-by: Josh Boyer commit b2cad6a2d733d9b10d25a31874a51d96908d6e89 Author: Amit K Bag Date: Wed Apr 22 15:02:44 2020 +0530 linux-firmware: Update firmware file for Intel Bluetooth AX200 This patch updates new firmware file for Intel Bluetooth AX200 Also it is known as Intel CyclonePeak (CcP). FW Build: REL6356 Release Version: 21.90.0.3 Signed-off-by: Amit K Bag Signed-off-by: Josh Boyer -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Still seeing this with that kernel: kernel: [ cut here ] kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out kernel: WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:442 dev_watchdog+0x25b/0x270 kernel: Modules linked in: xt_comment iptable_mangle iptable_nat bpfilter xt_CHECKSUM xt_MASQUERADE dummy xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfne> kernel: xor raid6_pq libcrc32c dm_crypt hid_logitech_hidpp hid_microsoft hid_logitech_dj ff_memless hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_i> kernel: CPU: 8 PID: 0 Comm: swapper/8 Tainted: P OE 5.8.0-24-generic #25~lp1874464 kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 kernel: RIP: 0010:dev_watchdog+0x25b/0x270 kernel: Code: 85 c0 75 e5 eb 9c 4c 89 ff c6 05 36 85 1c 01 01 e8 2a 93 fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 7c e8 8c 48 89 c2 e8 ca 30 64 ff <0f> 0b e9 7a ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f kernel: RSP: 0018:bd1800348e78 EFLAGS: 00010286 kernel: RAX: RBX: 95808d02dc00 RCX: 95808ee18cd8 kernel: RDX: ffd8 RSI: 0027 RDI: 95808ee18cd0 kernel: RBP: bd1800348ea8 R08: 0004 R09: 0554 kernel: R10: R11: 0001 R12: 95808d02dc80 kernel: R13: R14: 95808c9be480 R15: 95808c9be000 kernel: FS: () GS:95808ee0() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 7ffd799aee88 CR3: 0003ac6d8000 CR4: 003406e0 kernel: Call Trace: kernel: kernel: ? pfifo_fast_enqueue+0x150/0x150 kernel: call_timer_fn+0x32/0x130 kernel: __run_timers.part.0+0x184/0x280 kernel: ? lapic_next_event+0x21/0x30 kernel: ? clockevents_program_event+0x8f/0xe0 kernel: run_timer_softirq+0x2a/0x50 kernel: __do_softirq+0xd0/0x2a1 kernel: asm_call_irq_on_stack+0x12/0x20 kernel: kernel: do_softirq_own_stack+0x3d/0x50 kernel: irq_exit_rcu+0x95/0xd0 kernel: sysvec_apic_timer_interrupt+0x3b/0x90 kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 kernel: RIP: 0010:cpuidle_enter_state+0xb7/0x3f0 kernel: Code: 4f fb c6 73 e8 5a 5d 74 ff 48 89 45 d0 0f 1f 44 00 00 31 ff e8 0a 69 74 ff 80 7d c7 00 0f 85 d3 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 df 01 00 00 49 63 d4 48 8d 04 52 48 8d 0c d5 00 00 kernel: RSP: 0018:bd1800167e48 EFLAGS: 0246 kernel: RAX: 95808ee2c6c0 RBX: 958079782400 RCX: 001f kernel: RDX: RSI: 239f5376 RDI: kernel: RBP: bd1800167e88 R08: 000853f09bec R09: kernel: R10: 0a06 R11: 95808ee2b364 R12: 0002 kernel: R13: 8d577ba0 R14: 0002 R15: kernel: ? cpuidle_enter_state+0xa6/0x3f0 kernel: cpuidle_enter+0x2e/0x40 kernel: cpuidle_idle_call+0x145/0x200 kernel: do_idle+0x7a/0xe0 kernel: cpu_startup_entry+0x20/0x30 kernel: start_secondary+0xe6/0x100 kernel: secondary_startup_64+0xb6/0xc0 kernel: ---[ end trace 7dcae081a07b21ec ]--- -- 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23
[Kernel-packages] [Bug 1901890] 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 1901890 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 ** Tags added: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901890 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.4-28 Status in linux package in Ubuntu: Incomplete Bug description: My recent upgrade to Focal (20.04) using 5.4.0-28 version of the kernel kills wifi. Wifi was working properly under 19.10 (using 5.3.0-68). The issue persists using both rtw88 and rtwpci (which work under 19.10). 20.04 live CD has the same issue. I also tried installing 20.10 and found the same issue. On startup wireless works for a little while, allowing to see and connect to networks, but stops working shortly thereafter (mere seconds). Further, just trying the 20.04 live CD appears to mess the wireless card when returning to 19.10 (which is installed on a proper drive in my laptop). Needed to reinstall the kernel (same version: 5.3.0-51-generic) in 19.10 to get it working again. I have no idea what this means. I have followed several of the suggestions in: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133 (which seems to be the same bug for a previous kernel version, so may be this is a reversion?), to no avail. My wireless adapter is an RTL8822BE which shows up in lspci and lshw -C network, although under 5.4.0-28 lshw shows it as disabled (as I said, it appears to work for a few seconds after startup). dsmeg shows some issues with changing the power mode of the device although I am too much of a noob to understand it. In order to post this I rolled back to 19.10, so I no longer have access to a machine experiencing this issue (and cannot post the logs), but can reboot on the live CD and obtain them if there is any useful debugging to be done. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901894] 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/1901894
Title:
One or more monitors turns off but system usable until monitor
orientation change
Status in linux package in Ubuntu:
Confirmed
Bug description:
I'm having random lockups, sort of.
When this happens, usually one monitor out of 3 (including laptop
display) will turn off (one of the external monitors) sometimes both
external monitors. Usually I can spawn new applications and the system
is usable but if I try to detect the displays again or if I undock,
all remaining screens go blank (normal) but don't return like usual.
I'm unable to change to a new virtual console so all I can do is
reboot. Sometimes I'm able to do a soft reboot (with power button),
other times I have to hold the power button to do a hard shutdown.
I'm not sure if it's related but I get this error in dmesg:
[1.001281] BERT: Error records from previous boot:
[1.001281] [Hardware Error]: event severity: fatal
[1.001282] [Hardware Error]: Error 0, type: fatal
[1.001283] [Hardware Error]: section type: unknown,
81212a96-09ed-4996-9471-8d729c8e69ed
[1.001284] [Hardware Error]: section length: 0xc20
[1.001285] [Hardware Error]: : 0201
01002001 . ..
[1.001286] [Hardware Error]: 0010:
[1.001286] [Hardware Error]: 0020: 01002001 0006 527ed301
022b . ~R+...
[1.001287] [Hardware Error]: 0030: 0002 004e 090a004c
83ff N...L...
[1.001288] [Hardware Error]: 0040: 02002080 7f05fe03 0001
. ..
[1.001288] [Hardware Error]: 0050: 2200 0120 10002031
4000 ...".. .1 ...@..
[1.001289] [Hardware Error]: 0060: 0102 c7000200 ff0b0204
ff01f08b
[1.001289] [Hardware Error]: 0070: 750e687b 9a002000 0011
2000 {h.u. ... ..
[1.001290] [Hardware Error]: 0080: 0400 00502881
000ecf1a .(P.
[1.001291] [Hardware Error]: 0090: 00035d00 0001 5af3f070
1020003c .]..p..Z<. .
[1.001291] [Hardware Error]: 00a0: 00c6 fef3f900 de3717fc
ff477ecf ..7..~G.
[1.001292] [Hardware Error]: 00b0: 7cf3f8ff 18321000 034178cf
5af3f01e ...|..2..xAZ
[1.001292] [Hardware Error]: 00c0: 103c 00c6
<...
[1.001293] [Hardware Error]: 00d0: c4302000 08241cfc
010c . 0...$.
[1.001293] [Hardware Error]: 00e0: 010c0700 21c80003 00b88030
18001800 ...!0...
[1.001294] [Hardware Error]: 00f0: 024166c0
.fA.
[1.001295] [Hardware Error]: 0100: 10c0 4200
0114b800 .B..
[1.001295] [Hardware Error]: 0110: 0002 0009 0080
4880bf01 ...H
[1.001296] [Hardware Error]: 0120: 883f0080 b27f40e3 77c0c90f
4880bffc ..?..@.w...H
[1.001296] [Hardware Error]: 0130: 883f0080 990290e3 003b1816
0001 ..?...;.
[1.001297] [Hardware Error]: 0140: 0001 8101 00333833
0001 383.
[1.001298] [Hardware Error]: 0150: 0001 9801 ff063506
ff0f .5..
[1.001298] [Hardware Error]: 0160: ff0f 800f ff0db303
ff0f
[1.001299] [Hardware Error]: 0170: ff0f 000f
[1.001299] [Hardware Error]: 0180:
[1.001300] [Hardware Error]: 0190:
[1.001300] [Hardware Error]: 01a0: 0001 0001 0001
8201
[1.001301] [Hardware Error]: 01b0: 004018f6 0001 0001
ff01 ..@.
[1.001301] [Hardware Error]: 01c0: ff0f ff0f ff0f
810f
[1.001302] [Hardware Error]: 01d0: ff00ec06 ff0f ff0f
000f
[1.001302] [Hardware Error]: 01e0:
[1.001303] [Hardware Error]: 01f0:
[1.001303] [Hardware Error]: 0200:
[1.001304] [Hardware Error]: 0210: 0920
dec90002 .. .
[1.001304] [Hardware Error]: 0220: fc0c020e 015e00a9 3900301e
..^..0.9
[1.001305]
[Kernel-packages] [Bug 1901894] [NEW] One or more monitors turns off but system usable until monitor orientation change
Public bug reported:
I'm having random lockups, sort of.
When this happens, usually one monitor out of 3 (including laptop
display) will turn off (one of the external monitors) sometimes both
external monitors. Usually I can spawn new applications and the system
is usable but if I try to detect the displays again or if I undock, all
remaining screens go blank (normal) but don't return like usual. I'm
unable to change to a new virtual console so all I can do is reboot.
Sometimes I'm able to do a soft reboot (with power button), other times
I have to hold the power button to do a hard shutdown.
I'm not sure if it's related but I get this error in dmesg:
[1.001281] BERT: Error records from previous boot:
[1.001281] [Hardware Error]: event severity: fatal
[1.001282] [Hardware Error]: Error 0, type: fatal
[1.001283] [Hardware Error]: section type: unknown,
81212a96-09ed-4996-9471-8d729c8e69ed
[1.001284] [Hardware Error]: section length: 0xc20
[1.001285] [Hardware Error]: : 0201
01002001 . ..
[1.001286] [Hardware Error]: 0010:
[1.001286] [Hardware Error]: 0020: 01002001 0006 527ed301
022b . ~R+...
[1.001287] [Hardware Error]: 0030: 0002 004e 090a004c
83ff N...L...
[1.001288] [Hardware Error]: 0040: 02002080 7f05fe03 0001
. ..
[1.001288] [Hardware Error]: 0050: 2200 0120 10002031
4000 ...".. .1 ...@..
[1.001289] [Hardware Error]: 0060: 0102 c7000200 ff0b0204
ff01f08b
[1.001289] [Hardware Error]: 0070: 750e687b 9a002000 0011
2000 {h.u. ... ..
[1.001290] [Hardware Error]: 0080: 0400 00502881
000ecf1a .(P.
[1.001291] [Hardware Error]: 0090: 00035d00 0001 5af3f070
1020003c .]..p..Z<. .
[1.001291] [Hardware Error]: 00a0: 00c6 fef3f900 de3717fc
ff477ecf ..7..~G.
[1.001292] [Hardware Error]: 00b0: 7cf3f8ff 18321000 034178cf
5af3f01e ...|..2..xAZ
[1.001292] [Hardware Error]: 00c0: 103c 00c6
<...
[1.001293] [Hardware Error]: 00d0: c4302000 08241cfc
010c . 0...$.
[1.001293] [Hardware Error]: 00e0: 010c0700 21c80003 00b88030
18001800 ...!0...
[1.001294] [Hardware Error]: 00f0: 024166c0
.fA.
[1.001295] [Hardware Error]: 0100: 10c0 4200
0114b800 .B..
[1.001295] [Hardware Error]: 0110: 0002 0009 0080
4880bf01 ...H
[1.001296] [Hardware Error]: 0120: 883f0080 b27f40e3 77c0c90f
4880bffc ..?..@.w...H
[1.001296] [Hardware Error]: 0130: 883f0080 990290e3 003b1816
0001 ..?...;.
[1.001297] [Hardware Error]: 0140: 0001 8101 00333833
0001 383.
[1.001298] [Hardware Error]: 0150: 0001 9801 ff063506
ff0f .5..
[1.001298] [Hardware Error]: 0160: ff0f 800f ff0db303
ff0f
[1.001299] [Hardware Error]: 0170: ff0f 000f
[1.001299] [Hardware Error]: 0180:
[1.001300] [Hardware Error]: 0190:
[1.001300] [Hardware Error]: 01a0: 0001 0001 0001
8201
[1.001301] [Hardware Error]: 01b0: 004018f6 0001 0001
ff01 ..@.
[1.001301] [Hardware Error]: 01c0: ff0f ff0f ff0f
810f
[1.001302] [Hardware Error]: 01d0: ff00ec06 ff0f ff0f
000f
[1.001302] [Hardware Error]: 01e0:
[1.001303] [Hardware Error]: 01f0:
[1.001303] [Hardware Error]: 0200:
[1.001304] [Hardware Error]: 0210: 0920
dec90002 .. .
[1.001304] [Hardware Error]: 0220: fc0c020e 015e00a9 3900301e
..^..0.9
[1.001305] [Hardware Error]: 0230:
[1.001305] [Hardware Error]: 0240:
[1.001306] [Hardware Error]: 0250:
[1.001306] [Hardware Error]: 0260:
[1.001307] [Hardware Error]: 0270:
[1.001307]
[Kernel-packages] [Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads
So it looks like focal will inherit this problem when HWE starts rolling out. ** Summary changed: - Cannot boot with thunderbolt dock connected before kernel loads + Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays through the dock (HDMI and VGA). My system uses graphical boot via plymouth. Dell logo remains on screen while ubuntu loads into gdm3 (when it is booting normally). I'm using LUKS. This is a regression from focal and kernel 5.4. If I boot the laptop with the thunderbolt dock connected, the system will get past the Dell logo, go to a black screen and remain there. The screen is powered up as I can see some light on the edges. It won't boot up or respond to any keys. After force-shutdown via power key long press, on the next boot the grub menu will appear. The system will boot normally then (with the dock still connected). If I boot the system with the dock disconnected, it will correctly go into disk encryption password prompt. If at that point I connect the dock and wait without entering the password, the system will correctly set up the dock: the displays lit up and the mouse and keyboard plugged into it become active. The system boots normally. I'm trying to bisect in which kernel version this happened. I'll put results in a comment. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.25.30 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luis 3332 F pulseaudio /dev/snd/controlC0: luis 3332 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 23 16:27:30 2020 InstallationDate: Installed on 2019-08-17 (432 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=/dev/mapper/vglinux-root ro quiet splash 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.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads
I had to do a clean-reinstall of 20.04 as there were other issues (my brother scan not working among others) that were deal breakers to me. I noticed the 5.8.0 kernel is available for install via the metapackage linux-generic-hwe-20.04-edge (installs linux-image-5.8.0-25-generic and related packages) To cut a long story short, the error occurs in focal with the groovy kernel as well. -- 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/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays through the dock (HDMI and VGA). My system uses graphical boot via plymouth. Dell logo remains on screen while ubuntu loads into gdm3 (when it is booting normally). I'm using LUKS. This is a regression from focal and kernel 5.4. If I boot the laptop with the thunderbolt dock connected, the system will get past the Dell logo, go to a black screen and remain there. The screen is powered up as I can see some light on the edges. It won't boot up or respond to any keys. After force-shutdown via power key long press, on the next boot the grub menu will appear. The system will boot normally then (with the dock still connected). If I boot the system with the dock disconnected, it will correctly go into disk encryption password prompt. If at that point I connect the dock and wait without entering the password, the system will correctly set up the dock: the displays lit up and the mouse and keyboard plugged into it become active. The system boots normally. I'm trying to bisect in which kernel version this happened. I'll put results in a comment. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.25.30 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luis 3332 F pulseaudio /dev/snd/controlC0: luis 3332 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 23 16:27:30 2020 InstallationDate: Installed on 2019-08-17 (432 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=/dev/mapper/vglinux-root ro quiet splash 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.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901842] Re: Ubuntu 20.04 - multicast counter is not increased in ip -s
Patch exists upstream in 5.9. So Hirsute should be good, will need backport for
Groovy and Focal.
** Project changed: kernel-sru-workflow => linux (Ubuntu)
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hirsute)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901842
Title:
Ubuntu 20.04 - multicast counter is not increased in ip -s
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
Invalid
Bug description:
[Impact]
on a mlx5 device rx-mcast counter is not increased in ip -s after receiving
mcast packets.
Rx-packets counter is increased normally.
[test case]
send multicast packets to a mlx5 device using mcast address (like 224.0.0.1)
# iperf --client 224.0.0.1 -u --bind 15.194.5.1
see that before and after sending the mcast counter remains the same
before:
# ip -s l show ens5f0
10: ens5f0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
1350216893 0 0 0 0
TX: bytes packets errors dropped carrier collsns
16221 94 0 0 0 0
after
# ip -s l show ens5f0
10: ens5f0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
27004321786 0 0 0 0
TX: bytes packets errors dropped carrier collsns
16221 94 0 0 0 0
[Fix]
The issue is solved with upstream commit:
commit 47c97e6b10a1e3680cad539929da092bfa535446
Author: Ron Diskin
Date: Sun May 10 14:39:51 2020 +0300
net/mlx5e: Fix multicast counter not up-to-date in "ip -s"
Currently the FW does not generate events for counters other than error
counters. Unlike ".get_ethtool_stats", ".ndo_get_stats64" (which ip -s
uses) might run in atomic context, while the FW interface is non atomic.
Thus, 'ip' is not allowed to issue FW commands, so it will only display
cached counters in the driver.
Add a SW counter (mcast_packets) in the driver to count rx multicast
packets. The counter also counts broadcast packets, as we consider it a
special case of multicast.
Use the counter value when calling "ip -s"/"ifconfig".
Fixes: f62b8bb8f2d3 ("net/mlx5: Extend mlx5_core to support ConnectX-4
Ethernet functionality")
Signed-off-by: Ron Diskin
Reviewed-by: Tariq Toukan
Reviewed-by: Moshe Shemesh
Signed-off-by: Saeed Mahameed
after applying this patch the mcast counter is increased.
before sending mcast packets
# ip -s l show ens5f0
10: ens5f0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
0 00 0 0 0
TX: bytes packets errors dropped carrier collsns
7182 41 0 0 0 0
after sending mcast packets
# ip -s l show ens5f0
10: ens5f0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
1350216893 0 0 0 893
TX: bytes packets errors dropped carrier collsns
9860 58 0 0 0 0
The patch is applied with 2 rejected hunks that need to be inserted
manually with no changes.
[Regression Potential]
Regression risk is low since this patch is small and inserts only minor
changes to the statistics mechanism.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901842/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901890] [NEW] realtek r8822be kernel module fails after update to linux kernel-headers 5.0.4-28
Public bug reported: My recent upgrade to Focal (20.04) using 5.4.0-28 version of the kernel kills wifi. Wifi was working properly under 19.10 (using 5.3.0-68). The issue persists using both rtw88 and rtwpci (which work under 19.10). 20.04 live CD has the same issue. I also tried installing 20.10 and found the same issue. On startup wireless works for a little while, allowing to see and connect to networks, but stops working shortly thereafter (mere seconds). Further, just trying the 20.04 live CD appears to mess the wireless card when returning to 19.10 (which is installed on a proper drive in my laptop). Needed to reinstall the kernel (same version: 5.3.0-51-generic) in 19.10 to get it working again. I have no idea what this means. I have followed several of the suggestions in: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133 (which seems to be the same bug for a previous kernel version, so may be this is a reversion?), to no avail. My wireless adapter is an RTL8822BE which shows up in lspci and lshw -C network, although under 5.4.0-28 lshw shows it as disabled (as I said, it appears to work for a few seconds after startup). dsmeg shows some issues with changing the power mode of the device although I am too much of a noob to understand it. In order to post this I rolled back to 19.10, so I no longer have access to a machine experiencing this issue (and cannot post the logs), but can reboot on the live CD and obtain them if there is any useful debugging to be done. Thanks! ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901890 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.4-28 Status in linux package in Ubuntu: New Bug description: My recent upgrade to Focal (20.04) using 5.4.0-28 version of the kernel kills wifi. Wifi was working properly under 19.10 (using 5.3.0-68). The issue persists using both rtw88 and rtwpci (which work under 19.10). 20.04 live CD has the same issue. I also tried installing 20.10 and found the same issue. On startup wireless works for a little while, allowing to see and connect to networks, but stops working shortly thereafter (mere seconds). Further, just trying the 20.04 live CD appears to mess the wireless card when returning to 19.10 (which is installed on a proper drive in my laptop). Needed to reinstall the kernel (same version: 5.3.0-51-generic) in 19.10 to get it working again. I have no idea what this means. I have followed several of the suggestions in: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133 (which seems to be the same bug for a previous kernel version, so may be this is a reversion?), to no avail. My wireless adapter is an RTL8822BE which shows up in lspci and lshw -C network, although under 5.4.0-28 lshw shows it as disabled (as I said, it appears to work for a few seconds after startup). dsmeg shows some issues with changing the power mode of the device although I am too much of a noob to understand it. In order to post this I rolled back to 19.10, so I no longer have access to a machine experiencing this issue (and cannot post the logs), but can reboot on the live CD and obtain them if there is any useful debugging to be done. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901842] [NEW] Ubuntu 20.04 - multicast counter is not increased in ip -s
You have been subscribed to a public bug:
[Impact]
on a mlx5 device rx-mcast counter is not increased in ip -s after receiving
mcast packets.
Rx-packets counter is increased normally.
[test case]
send multicast packets to a mlx5 device using mcast address (like 224.0.0.1)
# iperf --client 224.0.0.1 -u --bind 15.194.5.1
see that before and after sending the mcast counter remains the same
before:
# ip -s l show ens5f0
10: ens5f0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
1350216893 0 0 0 0
TX: bytes packets errors dropped carrier collsns
16221 94 0 0 0 0
after
# ip -s l show ens5f0
10: ens5f0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
27004321786 0 0 0 0
TX: bytes packets errors dropped carrier collsns
16221 94 0 0 0 0
[Fix]
The issue is solved with upstream commit:
commit 47c97e6b10a1e3680cad539929da092bfa535446
Author: Ron Diskin
Date: Sun May 10 14:39:51 2020 +0300
net/mlx5e: Fix multicast counter not up-to-date in "ip -s"
Currently the FW does not generate events for counters other than error
counters. Unlike ".get_ethtool_stats", ".ndo_get_stats64" (which ip -s
uses) might run in atomic context, while the FW interface is non atomic.
Thus, 'ip' is not allowed to issue FW commands, so it will only display
cached counters in the driver.
Add a SW counter (mcast_packets) in the driver to count rx multicast
packets. The counter also counts broadcast packets, as we consider it a
special case of multicast.
Use the counter value when calling "ip -s"/"ifconfig".
Fixes: f62b8bb8f2d3 ("net/mlx5: Extend mlx5_core to support ConnectX-4
Ethernet functionality")
Signed-off-by: Ron Diskin
Reviewed-by: Tariq Toukan
Reviewed-by: Moshe Shemesh
Signed-off-by: Saeed Mahameed
after applying this patch the mcast counter is increased.
before sending mcast packets
# ip -s l show ens5f0
10: ens5f0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
0 00 0 0 0
TX: bytes packets errors dropped carrier collsns
7182 41 0 0 0 0
after sending mcast packets
# ip -s l show ens5f0
10: ens5f0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether ec:0d:9a:d4:2d:fc brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
1350216893 0 0 0 893
TX: bytes packets errors dropped carrier collsns
9860 58 0 0 0 0
The patch is applied with 2 rejected hunks that need to be inserted
manually with no changes.
[Regression Potential]
Regression risk is low since this patch is small and inserts only minor changes
to the statistics mechanism.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Ubuntu 20.04 - multicast counter is not increased in ip -s
https://bugs.launchpad.net/bugs/1901842
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 1901884] 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/1901884 Title: package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux package in Ubuntu: Confirmed Bug description: Just logged in, unsure what triggered this. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 AptOrdering: linux-modules-5.4.0-52-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 26 06:39:45 2020 Dependencies: DpkgTerminalLog: dpkg: error processing package linux-modules-5.4.0-52-generic (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2020-10-12 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp0s3no wireless extensions. docker0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=cb71cd6b-cb86-4be9-b4ac-093d7d947e2a ro debug PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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: grub-pc 2.04-1ubuntu26.4 RfKill: SourcePackage: linux Title: package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901884] [NEW] package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt
Public bug reported: Just logged in, unsure what triggered this. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 AptOrdering: linux-modules-5.4.0-52-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 26 06:39:45 2020 Dependencies: DpkgTerminalLog: dpkg: error processing package linux-modules-5.4.0-52-generic (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2020-10-12 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp0s3no wireless extensions. docker0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=cb71cd6b-cb86-4be9-b4ac-093d7d947e2a ro debug PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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: grub-pc 2.04-1ubuntu26.4 RfKill: SourcePackage: linux Title: package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901884 Title: package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux package in Ubuntu: Confirmed Bug description: Just logged in, unsure what triggered this. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 AptOrdering: linux-modules-5.4.0-52-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 26 06:39:45 2020 Dependencies: DpkgTerminalLog: dpkg: error processing package linux-modules-5.4.0-52-generic (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2020-10-12 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp0s3no wireless extensions. docker0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=cb71cd6b-cb86-4be9-b4ac-093d7d947e2a ro debug PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18,
[Kernel-packages] [Bug 1867588] Re: [SFC-0316]sync mainline kernel 5.7rc1 SFC patchset into ubuntu HWE kernel branch
** Tags removed: tairadar -- 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/1867588 Title: [SFC-0316]sync mainline kernel 5.7rc1 SFC patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] SFC patchset have merged into mainline 5.7RC1rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] spi: HiSilicon v3xx: Use DMI quirk to set controller buswidth override bits spi: HiSilicon v3xx: Properly set CMD_CONFIG for Dual/Quad modes spi: Allow SPI controller override device buswidth To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901880] Re: rtl88x2BU won't build in 20.10
Here is the make log ** Attachment added: "Make log" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1901880/+attachment/5428455/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1901880 Title: rtl88x2BU won't build in 20.10 Status in dkms package in Ubuntu: New Bug description: I have a USB wifi adapter, I installed rtl88x2BU and for every kernel update in 20.04 dkms built it automatically without any problems. Now I have updated to 20.10 I would expect this to happen but the build fails: Building module: cleaning build area... make -j4 KERNELRELEASE=5.8.0-26-generic KVER=5.8.0-26-generic src=/usr/src/rtl88x2bu-5.3.1...(bad exit status: 2) ERROR (dkms apport): binary package for rtl88x2bu: 5.3.1 not found Error! Bad return status for module build on kernel: 5.8.0-26-generic (x86_64) Consult /var/lib/dkms/rtl88x2bu/5.3.1/build/make.log for more information. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dkms 2.8.3-4 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 11:43:38 2020 InstallationDate: Installed on 2015-06-21 (1955 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to groovy on 2020-10-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1901880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901880] [NEW] rtl88x2BU won't build in 20.10
Public bug reported: I have a USB wifi adapter, I installed rtl88x2BU and for every kernel update in 20.04 dkms built it automatically without any problems. Now I have updated to 20.10 I would expect this to happen but the build fails: Building module: cleaning build area... make -j4 KERNELRELEASE=5.8.0-26-generic KVER=5.8.0-26-generic src=/usr/src/rtl88x2bu-5.3.1...(bad exit status: 2) ERROR (dkms apport): binary package for rtl88x2bu: 5.3.1 not found Error! Bad return status for module build on kernel: 5.8.0-26-generic (x86_64) Consult /var/lib/dkms/rtl88x2bu/5.3.1/build/make.log for more information. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dkms 2.8.3-4 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 11:43:38 2020 InstallationDate: Installed on 2015-06-21 (1955 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to groovy on 2020-10-23 (4 days ago) ** Affects: dkms (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 dkms in Ubuntu. https://bugs.launchpad.net/bugs/1901880 Title: rtl88x2BU won't build in 20.10 Status in dkms package in Ubuntu: New Bug description: I have a USB wifi adapter, I installed rtl88x2BU and for every kernel update in 20.04 dkms built it automatically without any problems. Now I have updated to 20.10 I would expect this to happen but the build fails: Building module: cleaning build area... make -j4 KERNELRELEASE=5.8.0-26-generic KVER=5.8.0-26-generic src=/usr/src/rtl88x2bu-5.3.1...(bad exit status: 2) ERROR (dkms apport): binary package for rtl88x2bu: 5.3.1 not found Error! Bad return status for module build on kernel: 5.8.0-26-generic (x86_64) Consult /var/lib/dkms/rtl88x2bu/5.3.1/build/make.log for more information. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dkms 2.8.3-4 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 11:43:38 2020 InstallationDate: Installed on 2015-06-21 (1955 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to groovy on 2020-10-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1901880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894017] Re: Keyboard not working
@burritojohn, if you are seeing this on an Asus device then you are hit by a different variant of what is in essence the same bug. The Asus case is fixed by this upstream commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1797d588af15174d4a4e7159dac8c800538e4f8c Which has also been cherry-picked into the 5.8.y stable series (it is there since the v5.8.15 release). So to fix this for you (and many many other Asus users!) the Ubuntu kernels should pickup the upstream fix for this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool
Excellent news.
--
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/1814983
Title:
zfs poor sustained read performance from ssd pool
Status in Native ZFS for Linux:
Unknown
Status in zfs-linux package in Ubuntu:
Invalid
Bug description:
Hello,
I'm seeing substantially slower read performance from an ssd pool than
I expected.
I have two pools on this computer; one ('fst') is four sata ssds, the
other ('srv') is nine spinning metal drives.
With a long-running ripgrep process on the fst pool, performance
started out really good and grew to astonishingly good (iirc ~30kiops,
as measured by zpool iostat -v 1). However after a few hours the
performance has dropped to 30-40 iops. top reports an arc_reclaim and
many arc_prune processes to be consuming most of the CPU time.
I've included a screenshot of top, some output from zpool iostat -v 1,
and arc_summary, with "===" to indicate the start of the next
command's output:
===
top (memory in gigabytes):
top - 16:27:53 up 70 days, 16:03, 3 users, load average: 35.67, 35.81, 35.58
Tasks: 809 total, 19 running, 612 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 58.1 sy, 0.0 ni, 39.2 id, 2.6 wa, 0.0 hi, 0.0 si, 0.0
st
GiB Mem : 125.805 total,0.620 free, 96.942 used, 28.243 buff/cache
GiB Swap:5.694 total,5.688 free,0.006 used. 27.840 avail Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
1523 root 20 00.0m 0.0m 0.0m R 100.0 0.0 290:52.26
arc_reclaim
4484 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:18.79 arc_prune
6225 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:11.92 arc_prune
7601 root 20 00.0m 0.0m 0.0m S 56.2 0.0 2:50.25 arc_prune
30891 root 20 00.0m 0.0m 0.0m S 56.2 0.0 1:33.08 arc_prune
3057 root 20 00.0m 0.0m 0.0m S 55.9 0.0 9:00.95 arc_prune
3259 root 20 00.0m 0.0m 0.0m R 55.9 0.0 3:16.84 arc_prune
24008 root 20 00.0m 0.0m 0.0m S 55.9 0.0 1:55.71 arc_prune
1285 root 20 00.0m 0.0m 0.0m R 55.6 0.0 3:20.52 arc_prune
5345 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:15.99 arc_prune
30121 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:35.50 arc_prune
31192 root 20 00.0m 0.0m 0.0m S 55.6 0.0 6:17.16 arc_prune
32287 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:28.02 arc_prune
32625 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:27.34 arc_prune
22572 root 20 00.0m 0.0m 0.0m S 55.3 0.0 10:02.92 arc_prune
31989 root 20 00.0m 0.0m 0.0m R 55.3 0.0 1:28.03 arc_prune
3353 root 20 00.0m 0.0m 0.0m R 54.9 0.0 8:58.81 arc_prune
10252 root 20 00.0m 0.0m 0.0m R 54.9 0.0 2:36.37 arc_prune
1522 root 20 00.0m 0.0m 0.0m S 53.9 0.0 158:42.45 arc_prune
3694 root 20 00.0m 0.0m 0.0m R 53.9 0.0 1:20.79 arc_prune
13394 root 20 00.0m 0.0m 0.0m R 53.9 0.0 10:35.78 arc_prune
24592 root 20 00.0m 0.0m 0.0m R 53.9 0.0 1:54.19 arc_prune
25859 root 20 00.0m 0.0m 0.0m S 53.9 0.0 1:51.71 arc_prune
8194 root 20 00.0m 0.0m 0.0m S 53.6 0.0 0:54.51 arc_prune
18472 root 20 00.0m 0.0m 0.0m R 53.6 0.0 2:08.73 arc_prune
29525 root 20 00.0m 0.0m 0.0m R 53.6 0.0 1:35.81 arc_prune
32291 root 20 00.0m 0.0m 0.0m S 53.6 0.0 1:28.00 arc_prune
3156 root 20 00.0m 0.0m 0.0m R 53.3 0.0 3:17.68 arc_prune
6224 root
[Kernel-packages] [Bug 1894017] Re: Keyboard not working
Affected too, with an asus x751BP laptop on groovy. Blacklisting intel_vbtn doesn't change anything (not active with lsmod after the blacklist bug the bug's still there). Still there with the latest kernel from the update manager (5.8.0-26-generic) received today. The integrated keyboard/mouse work fine with 5.4.0-52-generic, and "cat /sys/class/dmi/id/chassis_type" returns 10. Thanks for reading me ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894613] Re: risc-v 5.8 kernel oops on ftrace tests
Fix: commit 4230e2deaa484b385aa01d598b2aea8e7f2660a6 from https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ** Description changed: - 5.8.0-1-generic (buildd@riscv64-qemu-lcy01-015) (gcc (Ubuntu + == SRU Groovy == + + Running the ftrace self tests results in null pointer dereference oops + on RISC-V and also on ARM64. + + == Fix == + + Upstream commit + https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4230e2deaa484b385aa01d598b2aea8e7f2660a6 + + == Testcase == + + Run the kernel ftrace selftest. Without the fix ftrace oopses on RISC-V + and ARM64 and can also hang on ARM64 too. With the fix, tests run + without oopsing or hanging. + + == Regression Potential == + + This fix marks two functions as notrace, so the functionality of the + functions is not actually altered so the risk is negligible. The only + chage is the the functions are no longer traceable via ftrace, which is + the desired operation. + + + - + + 5.8.0-1-generic (buildd@riscv64-qemu-lcy01-015) (gcc (Ubuntu 10.2.0-5ubuntu2) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35) #1-Ubuntu SMP Thu Aug 27 19:51:38 UTC 2020 (Ubuntu 5.8.0-1.1-generic 5.8.4 - 18:30:06 DEBUG| [stdout] # selftests: ftrace: ftracetest^M^M 18:30:07 DEBUG| [stdout] # === Ftrace unit tests ===^M^M 18:30:10 DEBUG| [stdout] # [1] Basic trace file check [PASS]^M^M [17433.113458] Unable to handle kernel NULL pointer dereference at virtual address ^M^M [17433.113533] Unable to handle kernel NULL pointer dereference at virtual address ^M^M [17433.113552] Unable to handle kernel NULL pointer dereference at virtual address ^M^M [17433.113573] Unable to handle kernel NULL pointer dereference at virtual address ^M^M [17433.113591] Unable to handle kernel NULL pointer dereference at virtual address ^M^M [17433.114290] Unable to handle kernel NULL pointer dereference at virtual address ^M^M [17433.114306] Unable to handle kernel NULL pointer dereference at virtual address ^M^M [17433.114315] Oops [#1]^M^M [17433.114630] Unable to handle kernel NULL pointer dereference at virtual address ^M^M [17433.114690] Modules linked in: virtio_rng binfmt_misc uio_pdrv_genirq uio drm sch_fq_codel drm_panel_orientation_quirks backlight ip_tables x_tables autofs4 virtio_net net_failover virtio_blk failover [last unloaded: signpost]^M^M [17433.115296] CPU: 1 PID: 15 Comm: migration/1 Tainted: GW OE 5.8.0-1-generic #1-Ubuntu^M^M [17433.115419] epc: ra : sp : ffe1f5c67d90^M^M [17433.115442] gp : ffe001722298 tp : ffe1f5c3ae00 t0 : ^M^M [17433.115459] t1 : 6000 t2 : 000bbc00 s0 : 0022^M^M [17433.115475] s1 : ffe0002b7c12 a0 : ffe000963a64 a1 : 0022^M^M [17433.115491] a2 : a3 : a4 : ^M^M [17433.115507] a5 : ffe1fec95580 a6 : 00ff a7 : 0001^M^M [17433.115523] s2 : 0001 s3 : ffe9d580 s4 : ffe001724210^M^M [17433.115540] s5 : ffe1fec9a3b8 s6 : s7 : 0001^M^M [17433.115556] s8 : ffe0016f07cb s9 : ffe1e909bb80 s10: ffe0002b7ba6^M^M [17433.115573] s11: ffe1e909bba8 t3 : 006c t4 : 002c73ba^M^M [17433.115586] t5 : 001f7fa8 t6 : ffe000c02d1c^M^M [17433.115603] status: 0120 badaddr: cause: 000c^M^M ** Description changed: == SRU Groovy == Running the ftrace self tests results in null pointer dereference oops on RISC-V and also on ARM64. == Fix == Upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4230e2deaa484b385aa01d598b2aea8e7f2660a6 == Testcase == Run the kernel ftrace selftest. Without the fix ftrace oopses on RISC-V and ARM64 and can also hang on ARM64 too. With the fix, tests run without oopsing or hanging. == Regression Potential == This fix marks two functions as notrace, so the functionality of the functions is not actually altered so the risk is negligible. The only chage is the the functions are no longer traceable via ftrace, which is the desired operation. - - 5.8.0-1-generic (buildd@riscv64-qemu-lcy01-015) (gcc (Ubuntu 10.2.0-5ubuntu2) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35) #1-Ubuntu SMP Thu Aug 27 19:51:38 UTC 2020 (Ubuntu 5.8.0-1.1-generic 5.8.4 18:30:06 DEBUG| [stdout] # selftests: ftrace: ftracetest^M^M 18:30:07 DEBUG| [stdout] # === Ftrace unit tests ===^M^M 18:30:10 DEBUG| [stdout] # [1] Basic trace file check [PASS]^M^M [17433.113458] Unable to handle kernel NULL pointer dereference at virtual address ^M^M
[Kernel-packages] [Bug 1901755] Re: "btrfs subvolume list" sporadically segfaults with linux-image-5.4.0-52-generic
Hello Martin, thanks for your bug report, the fix mentioned in the quote (1c78544eaa46 btrfs: fix wrong address when faulting in pages in the search ioctl) has already been applied to the Focal master-next branch via stable update process in bug 1896824. It's expected to have this fix available in -updates after the upcoming SRU cycle. I will keep this report open to make it easier for others to find it. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901755 Title: "btrfs subvolume list" sporadically segfaults with linux- image-5.4.0-52-generic Status in linux package in Ubuntu: Fix Committed Bug description: On a BTRFS volume with a lot of subvolumes, I get sporadic segfaults on "btrfs subvolume list", about 1/3 of the time. This is on Ubuntu 20.04. linux-image-5.4.0-48-generic does not experience those segfaults. On #btrfs on freenode, it was pointed out that 5.4.0-52.57 seems to have a regression but not the fix for it committed. To quote from the IRC message: > 5.4.0-52.57 has a regression (a48b73eca4ce btrfs: fix potential deadlock in the search ioctl) and not the fix (1c78544eaa46 btrfs: fix wrong address when faulting in pages in the search ioctl) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882268] Re: [linux-azure] Request for two CIFS commits in 16.04
** No longer affects: linux-azure (Ubuntu)
** No longer affects: linux-azure (Ubuntu Xenial)
** No longer affects: linux-azure (Ubuntu Bionic)
** No longer affects: linux-azure-4.15 (Ubuntu Xenial)
--
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/1882268
Title:
[linux-azure] Request for two CIFS commits in 16.04
Status in linux-azure-4.15 package in Ubuntu:
Invalid
Status in linux-azure-4.15 source package in Bionic:
In Progress
Bug description:
[Impact]
There was a previous bug requesting the following two commits in
18.04:
84a1f5b1cc6f ("cifs: Fix potential softlockups while refreshing DFS cache")
2084ed57167c ("CIFS: Only send SMB2_NEGOTIATE command on new TCP connections")
There is an issue now, which requires these commits in the 4.15 based
16.04 kernel.
Can these two commits be applied to 16.04?
(Those changes were include to 5.4 via the upstream stable updates
previously)
[Test Case]
The issue is hard to reproduce since it is related to issues during
reconnects. I will rely on Microsoft to test and also review the
changes.
[Regression Potential]
The changes affect only CIFS, so it would only affect linux-azure
systems that makes use of CIFS.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure-4.15/+bug/1882268/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
Sounds like a plan, if it works. Just patch the kernel to choose a more sane default. ** Changed in: mutter (Ubuntu) Status: New => Invalid ** Changed in: mutter (Ubuntu) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in HWE Next: New Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Invalid Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install 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-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
apparently fixed by the series ending at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=181567aa9f0d297804f1ea5d3ff4ba4518e05f2c included in 5.10-rc1 -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in HWE Next: New Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install 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-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Marco, I just have a lenovo laptop with the usb bluetooth module 8087:0026, I will test if it could work on my laptop. @Istvan, Yes, most of this kind of issues are in the bluetooth firmware or kernel driver, and nearly has nothing to do with pulseaudio. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894896] Re: [linux-azure][hibernation] Mellanox CX4 NIC's TX/RX packets stop increasing after hibernation/resume
** Changed in: linux-azure (Ubuntu) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium -- 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/1894896 Title: [linux-azure][hibernation] Mellanox CX4 NIC's TX/RX packets stop increasing after hibernation/resume Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Focal: In Progress Bug description: [Impact] Description of problem: In a VM with CX4 VF NIC on Azure, after hibernation/resume, the TX/RX packet counters stop increaseing. This issue doesn't exist in VM with a CX3 VF NIC. This happens to the latest stable release of the linux-azure 5.4.0-1023.23 kernel and the latest mainline linux kernel. [Test Case] How reproducible: 100% Steps to Reproduce: 1. Start a VM in Azure that supports Accelerated Networking, and enable hibernation properly (please refer to https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 ). Please make sure the VF NIC is CX-4 since the issue doesn't happen to CX-3. 2. Do hibernation from serial console # systemctl hibernate 3. After the VM resumes back, check the MSI interrupt counters in /proc/interrupts for the CX-4 NIC, and also check “ifconfig” (e.g. “ifconfig enP2642s2”) for the RX/TX counters. These counters stop increasing while they should. [Regression Potential] The change touches netvsc and has potential to affect any instances using accelerated networking. However the fix is straightforward and it's a clean cherry-pick from 5.9. [Other Info] BUG FIX: The fix is in the net.git tree now: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=19162fd4063a3211843b997a454b505edb81d5ce To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1894896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Hi all, throwing in my experience: Sony WH-H910N, ThinkPad P1 Gen 2, Bus 001 Device 007: ID 8087:0029 Intel Corp. Worked under 18.04 When upgraded to 20.04 rcX (before it was released), still kept working. Not much later - already on released 20.04 - with a fw/kernel/whatever upgrade it stopped working in HSP/HFP mode. Since there were errors in dmesg related to the FW loading, I downloaded upstream FW from git, put them under /lib/firmware, and added a dpkg-diversion for the package provided versions, so that it survives an upgrade: dpkg-divert --list | grep ibt local diversion of /lib/firmware/intel/ibt-20-1-3.sfi to /lib/firmware/intel/ibt-20-1-3.sfi.dist local diversion of /lib/firmware/intel/ibt-20-1-3.ddc to /lib/firmware/intel/ibt-20-1-3.ddc.dist Headphones Sony WH-H910N do work out of the box on a different system with the same distro - with BT HW 8087:0a2a. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Markus was faster :-) verified waiting for the SRU aging period ... -- 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/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be "EPYC") by default it will pick the latest subversion that applies. In this case the behavior will
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Pre: root@f:~# grep EPYC /usr/share/libvirt/cpu_map/index.xml root@f:~# virsh domcapabilities | grep EPYC EPYC-IBPB EPYC root@f:~# cat test.xml test 4194304 4194304 4 hvm EPYC-Rome /usr/bin/qemu-system-x86_64 root@f:~# virsh define test.xml Domain test defined from test.xml root@f:~# virsh start test error: Failed to start domain test error: internal error: Unknown CPU model EPYC-Rome Upgrade: root@f:~# v=6.0.0-0ubuntu8.5; apt install libvirt-daemon-system=$v libvirt-clients=$v libvirt-daemon=$v libvirt0=$v libvirt-daemon-driver-qemu=$v libvirt-daemon-driver-storage-rbd=$v Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: geoip-database libgd3 libgeoip1 libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1 libxengnttab1 libxenmisc4.11 libxenstore3.0 libxentoolcore1 libxentoollog1 libxpm4 Use 'apt autoremove' to remove them. Suggested packages: libvirt-daemon-driver-lxc libvirt-daemon-driver-vbox libvirt-daemon-driver-xen libvirt-daemon-driver-storage-gluster libvirt-daemon-driver-storage-zfs numad auditd pm-utils radvd systemtap zfsutils The following packages will be upgraded: libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt0 6 upgraded, 0 newly installed, 0 to remove and 53 not upgraded. Need to get 2892 kB of archives. After this operation, 8192 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.5 [605 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.5 [28.3 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.5 [67.5 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.5 [344 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.5 [1443 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.5 [405 kB] Fetched 2892 kB in 1s (2314 kB/s) Preconfiguring packages ... (Reading database ... 77297 files and directories currently installed.) Preparing to unpack .../0-libvirt-daemon-driver-qemu_6.0.0-0ubuntu8.5_amd64.deb ... Unpacking libvirt-daemon-driver-qemu (6.0.0-0ubuntu8.5) over (6.0.0-0ubuntu8.4) ... Preparing to unpack .../1-libvirt-daemon-driver-storage-rbd_6.0.0-0ubuntu8.5_amd64.deb ... Unpacking libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu8.5) over (6.0.0-0ubuntu8.4) ... Preparing to unpack .../2-libvirt-daemon-system_6.0.0-0ubuntu8.5_amd64.deb ... Unpacking libvirt-daemon-system (6.0.0-0ubuntu8.5) over (6.0.0-0ubuntu8.4) ... Preparing to unpack .../3-libvirt-clients_6.0.0-0ubuntu8.5_amd64.deb ... Unpacking libvirt-clients (6.0.0-0ubuntu8.5) over (6.0.0-0ubuntu8.4) ... Preparing to unpack .../4-libvirt0_6.0.0-0ubuntu8.5_amd64.deb ... Unpacking libvirt0:amd64 (6.0.0-0ubuntu8.5) over (6.0.0-0ubuntu8.4) ... Preparing to unpack .../5-libvirt-daemon_6.0.0-0ubuntu8.5_amd64.deb ... Unpacking libvirt-daemon (6.0.0-0ubuntu8.5) over (6.0.0-0ubuntu8.4) ... Setting up libvirt0:amd64 (6.0.0-0ubuntu8.5) ... Setting up libvirt-clients (6.0.0-0ubuntu8.5) ... Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu8.5) ... Setting up libvirt-daemon (6.0.0-0ubuntu8.5) ... Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu8.5) ... Setting up libvirt-daemon-system (6.0.0-0ubuntu8.5) ... Job failed. See "journalctl -xe" for details. virtlockd.service is a disabled or a static unit, not starting it. virtlogd.service is a disabled or a static unit, not starting it. Setting up libvirt-daemon dnsmasq configuration. Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Processing triggers for man-db (2.9.1-1) ... Post upgrade: root@f:~# grep EPYC /usr/share/libvirt/cpu_map/index.xml root@f:~# ll /usr/share/libvirt/cpu_map/x86_EPYC-Rome.xml -rw-r--r-- 1 root root 2289 Oct 8 05:36 /usr/share/libvirt/cpu_map/x86_EPYC-Rome.xml root@f:~# virsh domcapabilities | grep EPYC EPYC-Rome EPYC-IBPB EPYC root@f:~# virsh start test error: Failed to start domain test error: the CPU is incompatible with host CPU: Host CPU does not provide required features: clwb, sha-ni, rdpid, mmxext, fxsr_opt, svm, cr8legacy, sse4a, misalignsse, osvw, perfctr_core, clzero, xsaveerptr, wbnoinvd, npt, nrip-save While I had no Rome cpu around one can see it now knew how to make one up (showing me what features I miss). This LGTM and also had shown no issues in the regression and migration tests. Up to @Markus to give this a final verification on the respective CPU then we can call it verified. -- You received this bug
[Kernel-packages] [Bug 1900883] Re: Add new iwlwifi firmware to solve AX201 hang
The change is proposed on - [PATCH 0/1] Add new iwlwifi firmware to solve AX201 hang - https://lists.ubuntu.com/archives/kernel- team/2020-October/114185.html -- 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/1900883 Title: Add new iwlwifi firmware to solve AX201 hang Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Confirmed Bug description: [Impact] Intel AX201 firmware crashes or hardware RX ring buffer hangs after S3. [Fix] Use new firmware from linux-firmware.git can solve the issue. [Test] WiFi works for each cycle of 1000 S3 cycles. [Regression Potential] Both Focal 5.4 and OEM 5.6 kernel use this firmware, so it might regress current 5.4 users. I did a smoke test with this firmware on Focal 5.4, and I didn't see any regression. Instead of cherry-pick the commit, only add the firmware needed for AX201 to minimize the regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Hui, Here's my device: Bus 003 Device 004: ID 8087:0026 Intel Corp. Marco. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Same tests as above. Still working as intended ** Tags removed: patch verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be
[Kernel-packages] [Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.
Like I mentioned, the kernel drivers seem fine. It appears to be a userspace software regression, either in bluez or in the gnome components that call bluez. the adaptor seems dead after resuming from sleep, until the gnome bluetooth settings panel is opened. this must call some sort of refresh function, and then everything works fine again. whatever this function is, it must've been called after resume previously in 20.04, and isn't being called now in 20.10, hence the regression. i don't know anything about bluez or the gnome internals, but i'm happy to provide whatever logs would be helpful in identifying the root cause and getting it fixed, since it's making my current desktop usage a nightmare. -- 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/1246981 Title: Bluetooth devices fail to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.
If it's a kernel regression, please bisect the kernel: https://wiki.ubuntu.com/Kernel/KernelBisection -- 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/1246981 Title: Bluetooth devices fail to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.
Well, that's sort of irrelevant for those of us having this problem. I just checked, and mine is a Broadcom BCM20702A0, so not exactly a niche vendor. I'm especially concerned since it seems like it's just not correctly re-scanning for bluetooth devices after waking from sleep due to some sort of software screw up since the 20.10 update, and there's nothing wrong with the controller. For those of us who depend on bluetooth, this is a major regression. -- 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/1246981 Title: Bluetooth devices fail to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
