[Kernel-packages] [Bug 1894355] 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/1894355 Title: Ubuntu 20.04 Microphone Background Noise Status in linux package in Ubuntu: Confirmed Bug description: The microphone sounds just fine when I booted up with Windows 10, but in Ubuntu 20.04 the background noise is pretty loud. I have already tried enabling noise cancellation with PulseAudio, but it doesn't seem to work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jerwellescusa 4380 F pulseaudio /dev/snd/pcmC0D0c: jerwellescusa 4380 F...m pulseaudio /dev/snd/pcmC0D0p: jerwellescusa 4380 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 5 12:39:31 2020 InstallationDate: Installed on 2020-08-06 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5a02 IMC Networks EasyCamera Bus 001 Device 002: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81G2 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=d6d16fb4-3439-4299-985d-5b1592314d74 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8KCN16WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0K13455 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-14IKB dmi.modalias: dmi:bvnLENOVO:bvr8KCN16WW:bd04/13/2018:svnLENOVO:pn81G2:pvrLenovoideapad330-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0K13455WIN:cvnLENOVO:ct10:cvrLenovoideapad330-14IKB: dmi.product.family: ideapad 330-14IKB dmi.product.name: 81G2 dmi.product.sku: LENOVO_MT_81G2_BU_idea_FM_ideapad 330-14IKB dmi.product.version: Lenovo ideapad 330-14IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894355] [NEW] Ubuntu 20.04 Microphone Background Noise
Public bug reported: The microphone sounds just fine when I booted up with Windows 10, but in Ubuntu 20.04 the background noise is pretty loud. I have already tried enabling noise cancellation with PulseAudio, but it doesn't seem to work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jerwellescusa 4380 F pulseaudio /dev/snd/pcmC0D0c: jerwellescusa 4380 F...m pulseaudio /dev/snd/pcmC0D0p: jerwellescusa 4380 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 5 12:39:31 2020 InstallationDate: Installed on 2020-08-06 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5a02 IMC Networks EasyCamera Bus 001 Device 002: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81G2 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=d6d16fb4-3439-4299-985d-5b1592314d74 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8KCN16WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0K13455 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-14IKB dmi.modalias: dmi:bvnLENOVO:bvr8KCN16WW:bd04/13/2018:svnLENOVO:pn81G2:pvrLenovoideapad330-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0K13455WIN:cvnLENOVO:ct10:cvrLenovoideapad330-14IKB: dmi.product.family: ideapad 330-14IKB dmi.product.name: 81G2 dmi.product.sku: LENOVO_MT_81G2_BU_idea_FM_ideapad 330-14IKB dmi.product.version: Lenovo ideapad 330-14IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894355 Title: Ubuntu 20.04 Microphone Background Noise Status in linux package in Ubuntu: New Bug description: The microphone sounds just fine when I booted up with Windows 10, but in Ubuntu 20.04 the background noise is pretty loud. I have already tried enabling noise cancellation with PulseAudio, but it doesn't seem to work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jerwellescusa 4380 F pulseaudio /dev/snd/pcmC0D0c: jerwellescusa 4380 F...m pulseaudio /dev/snd/pcmC0D0p: jerwellescusa 4380 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 5 12:39:31 2020 InstallationDate: Installed on 2020-08-06 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5a02 IMC Networks EasyCamera Bus 001 Device 002: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81G2 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=d6d16fb4-3439-4299-985d-5b1592314d74 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8KCN16WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0K13455 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-14IKB dmi.modalias: dmi:bvnLENOVO:bvr8KCN16WW:bd04/13/2018:svnLENOVO:pn81G2:pvrLenovoideapad330-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0K13455WIN:cvnLENOVO:ct10:cvrLenovoideapad330-14IKB: dmi.product.family: ideapad 330-14IKB dmi.product.name: 81G2
[Kernel-packages] [Bug 1882447] Re: Touchpad and sound doesn't work after the kernel update
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882447 Title: Touchpad and sound doesn't work after the kernel update Status in linux package in Ubuntu: Expired Bug description: My laptop: Lenovo IdeaPad 5 14IIL05 This appeared after update, that I had made 06.06.2020. Sound is disappeared too. Then I reinstall Ubuntu and don't upgrade it. But touchpad doesn't work. And doesn't detect in /proc/bus/input/devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leschev2331 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 21:10:47 2020 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=b86f12a0-6a3e-48db-a62a-5246a95afc77 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN22WW(V1.08) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN22WW(V1.08):bd03/06/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886246] Re: Sometimes on my lock screen, my mouse stops for a moment
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886246 Title: Sometimes on my lock screen, my mouse stops for a moment Status in linux package in Ubuntu: Expired Bug description: Sometimes on my lock screen, my mouse stops for a moment Please send me the solution I had recently sifted form windows to ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 10:22:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] [1002:9838] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8240 / R3 Series] [1025:104b] InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire ES1-520 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=01e0d428-3558-4f95-a0f0-994b27c807c3 ro quiet splash i8042.nopnp vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Bellemere_BE dmi.board.vendor: Acer dmi.board.version: V1.06 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-520:pvrV1.06:rvnAcer:rnBellemere_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion: dmi.product.family: KB dmi.product.name: Aspire ES1-520 dmi.product.sku: Aspire ES1-520_104B_V1.06 dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885574] Re: Lenovo Ideapad S740 touchscreen is not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885574 Title: Lenovo Ideapad S740 touchscreen is not working Status in linux package in Ubuntu: Expired Bug description: 5.4.0-39-lowlatency on Ubuntu 20.04 LTS Computer is lenovo ideapad s740 I tried to sudo usbhid-dump -es and touch the screen but no output. I've opened a ticket with lenovo: https://forums.lenovo.com/t5/Lenovo- IdeaPad-1xx-3xx-5xx-7xx-Edge-LaVie-Z-Flex-Notebooks/Ideapad-s740 -touchscreen-not-working/m-p/5023332 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886331] Re: [amdgpu] Cannot boot sometimes - black screen with a mouse pointer.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886331 Title: [amdgpu] Cannot boot sometimes - black screen with a mouse pointer. Status in linux package in Ubuntu: Expired Bug description: Cannot boot sometimes - black screen with a mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 18:47:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-39-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615] InstallationDate: Installed on 2020-06-05 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Laptop 15-cw1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a88d53cb-0507-4895-a6b9-15550b8ec4e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2019 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8615 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.34:bd07/31/2019:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cw1xxx dmi.product.sku: 6QF12EA#AB7 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) ,
on my windows 10 ,
it report error!
Microsoft Windows [Version 10.0.19042.450]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>logman create trace -n HID_WPP -o
%SystemRoot%\Tracing\HID_WPP.etl -nb 128 640 -bs 128
Error:
Data Collector already exists.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{E742C27D-29B1-4E4B-94EE-074D3AD72836} 0x7FFF 0xFF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman stop -n HID_WPP
Error:
Data Collector Set is not running.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{47c779cd-4efd-49d7-9b10-9f16e5c25d06} 0x7FFF 0xFF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{896f2806-9d0e-4d5f-aa25-7acdbf4eaf2c} 0x7FFF 0xFF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{07699FF6-D2C0-4323-B927-2C53442ED29B} 0x7FFF 0xFF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{0107cf95-313a-473e-9078-e73cd932f2fe} 0x7FFF 0xF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman stop -n HID_WPP
Error:
Data Collector Set is not running.
C:\WINDOWS\system32>
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Confirmed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
[Kernel-packages] [Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy
** Tags added: 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/1752251 Title: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy Status in linux package in Ubuntu: Confirmed Status in mcelog package in Ubuntu: Confirmed Bug description: There is no mcelog package in bionic. $ sudo apt install mcelog Reading package lists... Done Building dependency tree Reading state information... Done Package mcelog is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'mcelog' has no installation candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Confirming, only Blender is affected in my case. Kernel 5.4.0-42, Intel UHD Graphics 620 (rev 07). -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Released Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Forgot to say please un-blacklist elan_i2c. -- 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17
Indeed it got overwritten on the update! My "5.4.0-42-generic" also started to freeze. Because before (and now again after the update) the "sof-cfl.ri" was just a symbolic link to "sof-cnl.ri" which is a symbolic link to "signed/sof-cnl-signed-intel.ri". I put the new "sof-cfl.ri" now and "5.4.0-45-generic" is not freezing. -- 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/1892714 Title: Microphone not working on HP Omen 17 Status in linux-firmware package in Ubuntu: Triaged Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1892714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
And for those who have the Synaptics touchpad, I've found a way to make
the touchpad almost work. You can apply the following patch which will
make kernel use hid-rmi handle the device without blacklisting hid-
mulitouch,
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index a8e3b2796be8..9984e31c8914 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -1102,6 +1102,7 @@
#define I2C_VENDOR_ID_SYNAPTICS 0x06cb
#define I2C_PRODUCT_ID_SYNAPTICS_SYNA2393 0x7a13
+#define I2C_PRODUCT_ID_SYNAPTICS_SYNA7f28 0x7f28
#define USB_VENDOR_ID_SYNAPTICS0x06cb
#define USB_DEVICE_ID_SYNAPTICS_TP 0x0001
diff --git a/drivers/hid/hid-quirks.c b/drivers/hid/hid-quirks.c
index a65aef6a322f..a11366f6ccd8 100644
--- a/drivers/hid/hid-quirks.c
+++ b/drivers/hid/hid-quirks.c
@@ -568,6 +568,7 @@ static const struct hid_device_id hid_have_special_driver[]
= {
{ HID_USB_DEVICE(USB_VENDOR_ID_LENOVO, USB_DEVICE_ID_LENOVO_X1_COVER) },
{ HID_USB_DEVICE(USB_VENDOR_ID_RAZER, USB_DEVICE_ID_RAZER_BLADE_14) },
{ HID_USB_DEVICE(USB_VENDOR_ID_PRIMAX, USB_DEVICE_ID_PRIMAX_REZEL) },
+ { HID_I2C_DEVICE(I2C_VENDOR_ID_SYNAPTICS,
I2C_PRODUCT_ID_SYNAPTICS_SYNA7f28) },
#endif
#if IS_ENABLED(CONFIG_HID_ROCCAT)
{ HID_USB_DEVICE(USB_VENDOR_ID_ROCCAT, USB_DEVICE_ID_ROCCAT_ARVO) },
diff --git a/drivers/hid/hid-rmi.c b/drivers/hid/hid-rmi.c
index 7f41213d5ae3..e74b54f1b0c4 100644
--- a/drivers/hid/hid-rmi.c
+++ b/drivers/hid/hid-rmi.c
@@ -759,6 +759,7 @@ static const struct hid_device_id rmi_id[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_PRIMAX, USB_DEVICE_ID_PRIMAX_REZEL) },
{ HID_USB_DEVICE(USB_VENDOR_ID_SYNAPTICS,
USB_DEVICE_ID_SYNAPTICS_ACER_SWITCH5),
.driver_data = RMI_DEVICE_OUTPUT_SET_REPORT },
+ { HID_I2C_DEVICE(I2C_VENDOR_ID_SYNAPTICS,
I2C_PRODUCT_ID_SYNAPTICS_SYNA7f28) },
{ HID_DEVICE(HID_BUS_ANY, HID_GROUP_RMI, HID_ANY_ID, HID_ANY_ID) },
{ }
};
One left issue is the single clicking is not sensitive enough. I need to
let my finger linger on the touchpad for a while (like 0.5s). I'll send
the patches upstream after fixing this issue.
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Confirmed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi Stefano Galassi (iltoga) and wangjun (biggerchina) Thank you for providing the info! So this ELAN touchpad's HID reporter descriptors could be read and parsed but it couldn't be started at all since no HID reports are received. Now the only way I can think of to tackle this issue is to install Windows Driver Kit to capture HID reports to see what reports are sent/received from/by the Windows driver while playing with the touchpad under Windows? But my laptop comes with the Synnaptics touchpad, I couldn't do this on my own computer. Is it possible for you to do it for me? Here's the how-to https://techcommunity.microsoft.com/t5/microsoft-usb-blog/how-to-capture-and-read-hid-traces-in-windows-8-1/ba-p/270839. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Nothing new happened. It still doesn't work I attached the new dmesg.log file ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5407766/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
The attachment "zfs_patch" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in zfs-linux package in Ubuntu:
New
Bug description:
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Please try this: https://people.canonical.com/~khfeng/lp1853277-hack-4/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] 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/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 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP:
[Kernel-packages] [Bug 1894334] 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/1894334 Title: GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel Status in linux package in Ubuntu: Confirmed Bug description: When migrating from the Kernel 5.4.0-42-lowlatency to 5.4.0-45-lowlatency my Graphic card stopped working properly. My second Monitor went dark. even little things like moving the mouse was just a slide show. When using Grub to load with the previus Kernel (5.4.0-42-lowlatency) my Graphics card worked just fine again. My Bios version is "heavily outdated" as I was told. I'll try to update it to V2.13 soon, maybe that helps run newer Kernel in the future. My Hardware: Mainboard: Z77A-G43 the command "sudo dmidecode -s bios-version" returned: "V2.5" Graphic card: Geforce GTX 760 GTK Driver package: NVIDIA driver metapackage nvidia-driver-435 UbuntuStudio 20.04.1 LTS Kernel 5.4.0-45-lowlatency PS: Thanks for your awesome Work. 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: XFCE Date: Fri Sep 4 20:51:16 2020 InstallationDate: Installed on 2020-01-26 (222 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: MSI MS-7758 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=58aefce8-42fe-4333-81ae-31d2c867846e 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 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-21 (75 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI 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: 2020-01-28T17:00:58.663417 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894334] [NEW] GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel
Public bug reported: When migrating from the Kernel 5.4.0-42-lowlatency to 5.4.0-45-lowlatency my Graphic card stopped working properly. My second Monitor went dark. even little things like moving the mouse was just a slide show. When using Grub to load with the previus Kernel (5.4.0-42-lowlatency) my Graphics card worked just fine again. My Bios version is "heavily outdated" as I was told. I'll try to update it to V2.13 soon, maybe that helps run newer Kernel in the future. My Hardware: Mainboard: Z77A-G43 the command "sudo dmidecode -s bios-version" returned: "V2.5" Graphic card: Geforce GTX 760 GTK Driver package: NVIDIA driver metapackage nvidia-driver-435 UbuntuStudio 20.04.1 LTS Kernel 5.4.0-45-lowlatency PS: Thanks for your awesome Work. 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: XFCE Date: Fri Sep 4 20:51:16 2020 InstallationDate: Installed on 2020-01-26 (222 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: MSI MS-7758 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=58aefce8-42fe-4333-81ae-31d2c867846e 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 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-21 (75 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI 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: 2020-01-28T17:00:58.663417 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894334 Title: GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel Status in linux package in Ubuntu: Confirmed Bug description: When migrating from the Kernel 5.4.0-42-lowlatency to 5.4.0-45-lowlatency my Graphic card stopped working properly. My second Monitor went dark. even little things like moving the mouse was just a slide show. When using Grub to load with the previus Kernel (5.4.0-42-lowlatency) my Graphics card worked just fine again. My Bios version is "heavily outdated" as I was told. I'll try to update it to V2.13 soon, maybe that helps run newer Kernel in the future. My Hardware: Mainboard: Z77A-G43 the command "sudo dmidecode -s bios-version" returned: "V2.5" Graphic card: Geforce GTX 760 GTK Driver package: NVIDIA driver metapackage nvidia-driver-435 UbuntuStudio 20.04.1 LTS Kernel 5.4.0-45-lowlatency PS: Thanks for your awesome Work. 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: XFCE Date: Fri Sep 4 20:51:16 2020 InstallationDate: Installed on 2020-01-26 (222 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: MSI MS-7758 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=58aefce8-42fe-4333-81ae-31d2c867846e 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 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-21 (75 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
(Moved the groovy task back to New, not sure if that's the right process!) -- 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: New Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: New 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 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d4016fe38 EFLAGS:
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
And this is what I see on 5.9.0-050900rc3-generic: Sep 04 15:05:02 surprise kernel: [ cut here ] Sep 04 15:05:02 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Sep 04 15:05:02 surprise kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:442 dev_watchdog+0x25b/0x270 Sep 04 15:05:02 surprise kernel: Modules linked in: xt_comment iptable_mangle iptable_nat bpfilter dummy xt_CHECKSUM xt_MASQUERADE 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> Sep 04 15:05:02 surprise kernel: xor raid6_pq libcrc32c dm_crypt hid_logitech_hidpp hid_logitech_dj hid_microsoft ff_memless hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper i2c_piix4 r8169 nvme i2c_nvidia_gpu rea> Sep 04 15:05:02 surprise kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.9.0-050900rc3-generic #202008302030 Sep 04 15:05:02 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Sep 04 15:05:02 surprise kernel: RIP: 0010:dev_watchdog+0x25b/0x270 Sep 04 15:05:02 surprise kernel: Code: 85 c0 75 e5 eb 9c 4c 89 ff c6 05 3a 29 1d 01 01 e8 5a 7c fa ff 44 89 e9 4c 89 fe 48 c7 c7 b0 9b a5 ac 48 89 c2 e8 aa 21 64 ff <0f> 0b e9 7a ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f Sep 04 15:05:02 surprise kernel: RSP: 0018:b1c340003e78 EFLAGS: 00010286 Sep 04 15:05:02 surprise kernel: RAX: RBX: 9a27782a RCX: Sep 04 15:05:02 surprise kernel: RDX: 9a278cc28fe0 RSI: 9a278cc18cc0 RDI: 0300 Sep 04 15:05:02 surprise kernel: RBP: b1c340003ea8 R08: 0004 R09: 053a Sep 04 15:05:02 surprise kernel: R10: R11: 0001 R12: 9a27782a0080 Sep 04 15:05:02 surprise kernel: R13: R14: 9a278ab9a480 R15: 9a278ab9a000 Sep 04 15:05:02 surprise kernel: FS: () GS:9a278cc0() knlGS: Sep 04 15:05:02 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Sep 04 15:05:02 surprise kernel: CR2: 55b1cb035468 CR3: 000400f86000 CR4: 003506f0 Sep 04 15:05:02 surprise kernel: Call Trace: Sep 04 15:05:02 surprise kernel: Sep 04 15:05:02 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Sep 04 15:05:02 surprise kernel: call_timer_fn+0x32/0x130 Sep 04 15:05:02 surprise kernel: __run_timers.part.0+0x1eb/0x270 Sep 04 15:05:02 surprise kernel: run_timer_softirq+0x2a/0x50 Sep 04 15:05:02 surprise kernel: __do_softirq+0xd0/0x2a5 Sep 04 15:05:02 surprise kernel: asm_call_on_stack+0x12/0x20 Sep 04 15:05:02 surprise kernel: Sep 04 15:05:02 surprise kernel: do_softirq_own_stack+0x3f/0x50 Sep 04 15:05:02 surprise kernel: irq_exit_rcu+0x95/0xd0 Sep 04 15:05:02 surprise kernel: sysvec_call_function_single+0x3d/0xa0 Sep 04 15:05:02 surprise kernel: asm_sysvec_call_function_single+0x12/0x20 Sep 04 15:05:02 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc2/0x390 Sep 04 15:05:02 surprise kernel: Code: f4 22 07 54 e8 ff 77 74 ff 48 89 45 d0 0f 1f 44 00 00 31 ff e8 bf 83 74 ff 80 7d c7 00 0f 85 48 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 54 01 00 00 49 63 d5 48 8d 04 52 48 8d 0c d5 00 00 Sep 04 15:05:02 surprise kernel: RSP: 0018:ad003de8 EFLAGS: 0246 Sep 04 15:05:02 surprise kernel: RAX: 9a278cc2c680 RBX: 9a2779308c00 RCX: 001f Sep 04 15:05:02 surprise kernel: RDX: RSI: 239f5376 RDI: Sep 04 15:05:02 surprise kernel: RBP: ad003e28 R08: 000a3c3a75d2 R09: Sep 04 15:05:02 surprise kernel: R10: 0f5e R11: 9a278cc2b324 R12: ad180b80 Sep 04 15:05:02 surprise kernel: R13: 0002 R14: ad180c68 R15: 0002 Sep 04 15:05:02 surprise kernel: ? cpuidle_enter_state+0xb1/0x390 Sep 04 15:05:02 surprise kernel: cpuidle_enter+0x2e/0x40 Sep 04 15:05:02 surprise kernel: cpuidle_idle_call+0x132/0x1d0 Sep 04 15:05:02 surprise kernel: do_idle+0x7a/0xe0 Sep 04 15:05:02 surprise kernel: cpu_startup_entry+0x20/0x30 Sep 04 15:05:02 surprise kernel: rest_init+0xae/0xb0 Sep 04 15:05:02 surprise kernel: arch_call_rest_init+0xe/0x1b Sep 04 15:05:02 surprise kernel: start_kernel+0x43a/0x45a Sep 04 15:05:02 surprise kernel: x86_64_start_reservations+0x24/0x26 Sep 04 15:05:02 surprise kernel: x86_64_start_kernel+0x8b/0x8f Sep 04 15:05:02 surprise kernel: secondary_startup_64+0xb6/0xc0 Sep 04 15:05:02 surprise kernel: ---[ end trace 02799b4d7b644ce5 ]--- ** Changed in: linux (Ubuntu Groovy) 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** Attachment added: "IMG_20200904_114219409.jpg"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+attachment/5407727/+files/IMG_20200904_114219409.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in zfs-linux package in Ubuntu:
New
Bug description:
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** Attachment added: "IMG_20200904_130202967.jpg"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+attachment/5407726/+files/IMG_20200904_130202967.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in zfs-linux package in Ubuntu:
New
Bug description:
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I saw this traceback on the 4.15.18 mainline build: Sep 04 14:47:41 surprise kernel: [ cut here ] Sep 04 14:47:41 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Sep 04 14:47:41 surprise kernel: WARNING: CPU: 11 PID: 0 at /home/kernel/COD/linux/net/sched/sch_generic.c:323 dev_watchdog+0x221/0x230 Sep 04 14:47:41 surprise kernel: Modules linked in: devlink nft_meta nft_compat ipt_REJECT nf_reject_ipv4 xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp nft_chain_route_ipv6 iptable_mangle iptable_nat nft_chain_nat_ipv6 nf_conntrack_ipv6 nf_def> Sep 04 14:47:41 surprise kernel: videodev joydev input_leds media snd_seq snd_seq_device irqbypass snd_timer k10temp wmi_bmof snd ccp nvidia_uvm(OE) 8250 soundcore 8250_base shpchp mac_hid wmi iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables parpor> Sep 04 14:47:41 surprise kernel: CPU: 11 PID: 0 Comm: swapper/11 Tainted: P OE4.15.18-041518-generic #201804190330 Sep 04 14:47:41 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Sep 04 14:47:41 surprise kernel: RIP: 0010:dev_watchdog+0x221/0x230 Sep 04 14:47:41 surprise kernel: RSP: 0018:96204e8c3e58 EFLAGS: 00010286 Sep 04 14:47:41 surprise kernel: RAX: RBX: RCX: Sep 04 14:47:41 surprise kernel: RDX: 00040400 RSI: 00f6 RDI: 0300 Sep 04 14:47:41 surprise kernel: RBP: 96204e8c3e88 R08: 0001 R09: 04c6 Sep 04 14:47:41 surprise kernel: R10: 96204e8c3ee0 R11: R12: 0001 Sep 04 14:47:41 surprise kernel: R13: 96204e32e000 R14: 96204e32e478 R15: 96203bd19880 Sep 04 14:47:41 surprise kernel: FS: () GS:96204e8c() knlGS: Sep 04 14:47:41 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Sep 04 14:47:41 surprise kernel: CR2: 7f564479a0c0 CR3: 00040adb CR4: 003406e0 Sep 04 14:47:41 surprise kernel: Call Trace: Sep 04 14:47:41 surprise kernel: Sep 04 14:47:41 surprise kernel: ? dev_deactivate_queue.constprop.33+0x60/0x60 Sep 04 14:47:41 surprise kernel: call_timer_fn+0x30/0x130 Sep 04 14:47:41 surprise kernel: run_timer_softirq+0x3fb/0x450 Sep 04 14:47:41 surprise kernel: ? ktime_get+0x43/0xa0 Sep 04 14:47:41 surprise kernel: ? lapic_next_event+0x20/0x30 Sep 04 14:47:41 surprise kernel: __do_softirq+0xdf/0x2b2 Sep 04 14:47:41 surprise kernel: irq_exit+0xb6/0xc0 Sep 04 14:47:41 surprise kernel: smp_apic_timer_interrupt+0x71/0x130 Sep 04 14:47:41 surprise kernel: apic_timer_interrupt+0x84/0x90 Sep 04 14:47:41 surprise kernel: Sep 04 14:47:41 surprise kernel: RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 Sep 04 14:47:41 surprise kernel: RSP: 0018:abdc019fbe68 EFLAGS: 0246 ORIG_RAX: ff11 Sep 04 14:47:41 surprise kernel: RAX: 96204e8e2880 RBX: 0013b8893c67 RCX: 001f Sep 04 14:47:41 surprise kernel: RDX: 0013b8893c67 RSI: fffc216ba992 RDI: Sep 04 14:47:41 surprise kernel: RBP: abdc019fbea8 R08: 000105ec R09: 0018 Sep 04 14:47:41 surprise kernel: R10: abdc019fbe38 R11: 386e R12: 96203cae1800 Sep 04 14:47:41 surprise kernel: R13: 0002 R14: b1f80098 R15: Sep 04 14:47:41 surprise kernel: ? cpuidle_enter_state+0x97/0x2f0 Sep 04 14:47:41 surprise kernel: cpuidle_enter+0x17/0x20 Sep 04 14:47:41 surprise kernel: call_cpuidle+0x23/0x40 Sep 04 14:47:41 surprise kernel: do_idle+0x18c/0x1f0 Sep 04 14:47:41 surprise kernel: cpu_startup_entry+0x73/0x80 Sep 04 14:47:41 surprise kernel: start_secondary+0x1a6/0x200 Sep 04 14:47:41 surprise kernel: secondary_startup_64+0xa5/0xb0 Sep 04 14:47:41 surprise kernel: Code: 39 00 49 63 4e e8 eb 92 4c 89 ef c6 05 87 d7 d9 00 01 e8 83 39 fd ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 c8 68 b8 b1 e8 ff a4 81 ff <0f> 0b eb c0 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 Sep 04 14:47:41 surprise kernel: ---[ end trace a02a9c8ad08e0a55 ]--- -- 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: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete 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
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
I tried it but still not working. I attached the new dmesg.log file ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5407723/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I just saw this again on 5.8.0-18-generic, and this time I did not manually modify my networking state; I installed the new kernel and rebooted into it, and the problem exhibited immediately. (Fortunately, for whatever reason, a reboot into Windows and back to -18 _has_ come up with networking, so it isn't happening on every boot.) I'll try a 4.15 kernel as requested in the last comment, and see what happens. -- 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: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete 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 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel:
[Kernel-packages] [Bug 1894329] [NEW] ZFS revert from grub menu not working.
Public bug reported:
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't
have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started with
executable stack.
After this an empty uid is returned which explains the dataset without a proper
suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy
** Patch added: "zfs_patch"
https://bugs.launchpad.net/bugs/1894329/+attachment/5407720/+files/zfs_patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in zfs-linux package in Ubuntu:
New
Bug description:
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I just saw this again on 5.8.0-18-generic, and this time I did not manually modify my networking state; I installed the new kernel and rebooted into it, and the problem exhibited immediately. (Fortunately, for whatever reason, a reboot into Windows and back to -18 _has_ come up with networking, so it isn't happening on every boot.) I'll try a 4.15 kernel as requested in the last comment, and see what happens. -- 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: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete 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 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel:
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Can you please try this one? https://people.canonical.com/~khfeng/lp1853277-hack-3/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894321] 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/1894321 Title: linux-libc-dev: linux/errno.h referrs to non-existing asm/errno.h Status in linux package in Ubuntu: Confirmed Bug description: It's a duplication of #1771309 though, as I am not an author, I can't add log there. /usr/include/asm does not exist on my machine - only /usr/include/asm-generic. This seems to be a common problem: (https://stackoverflow.com/questions/14795608/asm-errno-h-no-such-file-or-directory ) The relevant packages I have installed: dpkg -l | egrep "linux-(headers|libc)" ii linux-headers-4.15.0-115 4.15.0-115.116 all Header files related to Linux kernel version 4.15.0 ii linux-headers-4.15.0-115-generic 4.15.0-115.116 amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-5.4.0-42-generic 5.4.0-42.46~18.04.1 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-headers-5.4.0-45-generic 5.4.0-45.49~18.04.2 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-headers-generic 4.15.0.115.103 amd64Generic Linux kernel headers ii linux-headers-generic-hwe-18.04 5.4.0.45.49~18.04.38amd64Generic Linux kernel headers ii linux-headers-generic-hwe-18.04-edge 5.4.0.45.49~18.04.38amd64Generic Linux kernel headers ii linux-libc-dev:amd64 4.15.0-115.116 amd64Linux Kernel Headers for development ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-libc-dev 4.15.0-115.116 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afiergol 9070 F pulseaudio /dev/snd/controlC0: afiergol 9070 F pulseaudio /dev/snd/pcmC0D0p: afiergol 9070 F...m pulseaudio CurrentDesktop: GNOME Date: Fri Sep 4 19:28:56 2020 Dependencies: HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c InstallationDate: Installed on 2018-04-05 (883 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: LENOVO 20L6S04200 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager i915.enable_gvt=1 kvm.ignore_msrs=1 nouveau.blacklist=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-22 (744 days ago) dmi.bios.date: 06/02/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET59W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S04200 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET59W(1.34):bd06/02/2020:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNODPK:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S04200 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hi Kai, I checked your new Kernel and touchpad is still not recognized. Attached is dmesg.log ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5407704/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894321] [NEW] linux-libc-dev: linux/errno.h referrs to non-existing asm/errno.h
Public bug reported: It's a duplication of #1771309 though, as I am not an author, I can't add log there. /usr/include/asm does not exist on my machine - only /usr/include/asm-generic. This seems to be a common problem: (https://stackoverflow.com/questions/14795608/asm-errno-h-no-such-file-or-directory ) The relevant packages I have installed: dpkg -l | egrep "linux-(headers|libc)" ii linux-headers-4.15.0-1154.15.0-115.116 all Header files related to Linux kernel version 4.15.0 ii linux-headers-4.15.0-115-generic4.15.0-115.116 amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-5.4.0-42-generic 5.4.0-42.46~18.04.1 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-headers-5.4.0-45-generic 5.4.0-45.49~18.04.2 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-headers-generic 4.15.0.115.103 amd64Generic Linux kernel headers ii linux-headers-generic-hwe-18.04 5.4.0.45.49~18.04.38amd64Generic Linux kernel headers ii linux-headers-generic-hwe-18.04-edge 5.4.0.45.49~18.04.38amd64Generic Linux kernel headers ii linux-libc-dev:amd644.15.0-115.116 amd64Linux Kernel Headers for development ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-libc-dev 4.15.0-115.116 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afiergol 9070 F pulseaudio /dev/snd/controlC0: afiergol 9070 F pulseaudio /dev/snd/pcmC0D0p: afiergol 9070 F...m pulseaudio CurrentDesktop: GNOME Date: Fri Sep 4 19:28:56 2020 Dependencies: HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c InstallationDate: Installed on 2018-04-05 (883 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: LENOVO 20L6S04200 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager i915.enable_gvt=1 kvm.ignore_msrs=1 nouveau.blacklist=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-22 (744 days ago) dmi.bios.date: 06/02/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET59W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S04200 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET59W(1.34):bd06/02/2020:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNODPK:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S04200 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1894321 Title: linux-libc-dev: linux/errno.h referrs to non-existing asm/errno.h Status in linux package in Ubuntu: New Bug description: It's a duplication of #1771309 though, as I am not an author, I can't add log there. /usr/include/asm does not exist on my machine - only /usr/include/asm-generic. This seems to be a common problem: (https://stackoverflow.com/questions/14795608/asm-errno-h-no-such-file-or-directory ) The relevant packages I have installed: dpkg -l | egrep "linux-(headers|libc)" ii linux-headers-4.15.0-115 4.15.0-115.116 all Header files related to Linux kernel version 4.15.0 ii linux-headers-4.15.0-115-generic 4.15.0-115.116 amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-5.4.0-42-generic 5.4.0-42.46~18.04.1 amd64Linux kernel headers for version
[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition
Can you please attach `lspci -nn`? -- 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/1872383 Title: blk_update_request error when mount nvme partition Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] Got below error message after upgraded Focal kernel(v5.4) [ 576.793852] blk_update_request: operation not supported error, dev nvme1n1, sector 4218887 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 This issue was introduced by below commit which added write zeros command 6e02318eaea5 nvme: add support for the Write Zeroes command SK hynix firmware has a bug that it treats NLB as max value instead of a range, so the NLB passed isn't a valid value to the firmware. [Fix] Add a quirk to disable write zeros support [Test] Verified on the machine with SK hynix PC400 nvme machine. [Regression Potential] Low, it's a quirk to a specific PCI ID. == Can't install on this nvme with a focal server installer. As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel endless blk_update_request error will exists in kernel dmesg. the nvme module: PC400 NVMe SK hynix 512GB While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (11 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT mode device Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: Dell Inc. Precision 3930 Rack Package: linux-generic 5.4.0.21.25 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: Precision dmi.product.name: Precision 3930 Rack dmi.product.sku: 0873 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1872383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Please try this kernel and attach dmesg: https://people.canonical.com/~khfeng/lp1853277-hack-2/ -- 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894227] 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/1894227 Title: Problems with wifi Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu recently on my machine im new to this OS so i dont know if i did something wrong but i've been getting a very weak signal from wifi even though im standing next to my router. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ricardo32d853 F pulseaudio /dev/snd/controlC1: ricardo32d853 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 14:11:16 2020 InstallationDate: Installed on 2020-09-03 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550LD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=b6e7a05c-987f-4e2f-a373-ba49fa1ddbb6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LD 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.:bvrX550LD.308:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550LD dmi.product.sku: ASUS-NotebookSKU 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/1894227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894227] Re: Problems with wifi
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894227 Title: Problems with wifi Status in linux package in Ubuntu: New Bug description: I installed ubuntu recently on my machine im new to this OS so i dont know if i did something wrong but i've been getting a very weak signal from wifi even though im standing next to my router. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ricardo32d853 F pulseaudio /dev/snd/controlC1: ricardo32d853 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 14:11:16 2020 InstallationDate: Installed on 2020-09-03 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550LD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=b6e7a05c-987f-4e2f-a373-ba49fa1ddbb6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LD 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.:bvrX550LD.308:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550LD dmi.product.sku: ASUS-NotebookSKU 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/1894227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894227] [NEW] Problems with wifi
You have been subscribed to a public bug: I installed ubuntu recently on my machine im new to this OS so i dont know if i did something wrong but i've been getting a very weak signal from wifi even though im standing next to my router. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ricardo32d853 F pulseaudio /dev/snd/controlC1: ricardo32d853 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 14:11:16 2020 InstallationDate: Installed on 2020-09-03 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550LD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=b6e7a05c-987f-4e2f-a373-ba49fa1ddbb6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LD 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.:bvrX550LD.308:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550LD dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Problems with wifi https://bugs.launchpad.net/bugs/1894227 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 1888703] Re: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons p
On 9/4/2020 auto updated to kernel 5.4.0-45. This did not fix the display issue. Still operating under 5.3.0-62 as a workaround. -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894232] 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 1894232 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/1894232 Title: blank black screen or cursor on top left corner on a black screen problem Status in linux package in Ubuntu: Incomplete Bug description: i am currently using linux mint 20 ulyana with linux version 5.4.0-45 in which i am facing a problem of a blank black screen on boot or either a black screen with a dash on top left corner.Its been happening for last one week since i just started using linux this very week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894230] Re: Device queue depth should be 31 not 32
Uncomfortable dumping logs I can't view.
** 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/1894230
Title:
Device queue depth should be 31 not 32
Status in linux package in Ubuntu:
Confirmed
Bug description:
Setting drive device/queue_depth to 31 from 32 resolved an issue
whereby I had numerous zpool and ATA errors but only under high load
(zpool scrub) or when trimming the drives. Was able to reduce
incidence by setting to libata.force=noncqtrim, and resolve with
libata.force=noncq, but with an obvious performance impact.
Upstream kernel seems to be aware of this issue, so I'm assuming this
is a downstream or udev configuration issue, see:
https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ
Scrub repaired all errors, but, because repairs were made, it seems
like it's not just a communications issue, and that there is the
potential for DATA LOSS on non-redundant and/or non-ZFS
configurations.
Sample syslog error:
[ 33.688898] ata1.00: exception Emask 0x50 SAct 0x1003000 SErr 0x4c0900
action 0x6 frozen
[ 33.688908] ata1.00: irq_stat 0x0800, interface fatal error
[ 33.688913] ata1: SError: { UnrecovData HostInt CommWake 10B8B Handshk }
[ 33.688917] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688923] ata1.00: cmd 61/00:60:df:28:3d/01:00:2a:00:00/40 tag 12 ncq
dma 131072 out
[ 33.688929] ata1.00: status: { DRDY }
[ 33.688931] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688937] ata1.00: cmd 61/08:68:18:a9:d2/00:00:04:00:00/40 tag 13 ncq
dma 4096 out
[ 33.688942] ata1.00: status: { DRDY }
[ 33.688945] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688951] ata1.00: cmd 61/00:c0:df:27:3d/01:00:2a:00:00/40 tag 24 ncq
dma 131072 out
[ 33.688956] ata1.00: status: { DRDY }
[ 33.688963] ata1: hard resetting link
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894230/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894230] Re: Device queue depth should be 31 not 32
FYI, the drives are super common:
=== START OF INFORMATION SECTION ===
Model Family: Crucial/Micron BX/MX1/2/3/500, M5/600, 1100 SSDs
Device Model: Crucial_CT1050MX300SSD1
Serial Number:164914EE5DDD
LU WWN Device Id: 5 00a075 114ee5ddd
Firmware Version: M0CR031
User Capacity:1,050,214,588,416 bytes [1.05 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate:Solid State Device
Form Factor: 2.5 inches
Device is:In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Fri Sep 4 08:48:51 2020 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD30EFRX-68EUZN0
Serial Number:WD-WCC4N5VD5C7Z
LU WWN Device Id: 5 0014ee 263d50d79
Firmware Version: 82.00A82
User Capacity:3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate:5400 rpm
Device is:In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Fri Sep 4 08:49:19 2020 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
--
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/1894230
Title:
Device queue depth should be 31 not 32
Status in linux package in Ubuntu:
Confirmed
Bug description:
Setting drive device/queue_depth to 31 from 32 resolved an issue
whereby I had numerous zpool and ATA errors but only under high load
(zpool scrub) or when trimming the drives. Was able to reduce
incidence by setting to libata.force=noncqtrim, and resolve with
libata.force=noncq, but with an obvious performance impact.
Upstream kernel seems to be aware of this issue, so I'm assuming this
is a downstream or udev configuration issue, see:
https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ
Scrub repaired all errors, but, because repairs were made, it seems
like it's not just a communications issue, and that there is the
potential for DATA LOSS on non-redundant and/or non-ZFS
configurations.
Sample syslog error:
[ 33.688898] ata1.00: exception Emask 0x50 SAct 0x1003000 SErr 0x4c0900
action 0x6 frozen
[ 33.688908] ata1.00: irq_stat 0x0800, interface fatal error
[ 33.688913] ata1: SError: { UnrecovData HostInt CommWake 10B8B Handshk }
[ 33.688917] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688923] ata1.00: cmd 61/00:60:df:28:3d/01:00:2a:00:00/40 tag 12 ncq
dma 131072 out
[ 33.688929] ata1.00: status: { DRDY }
[ 33.688931] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688937] ata1.00: cmd 61/08:68:18:a9:d2/00:00:04:00:00/40 tag 13 ncq
dma 4096 out
[ 33.688942] ata1.00: status: { DRDY }
[ 33.688945] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688951] ata1.00: cmd 61/00:c0:df:27:3d/01:00:2a:00:00/40 tag 24 ncq
dma 131072 out
[ 33.688956] ata1.00: status: { DRDY }
[ 33.688963] ata1: hard resetting link
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894230/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894232] [NEW] blank black screen or cursor on top left corner on a black screen problem
Public bug reported: i am currently using linux mint 20 ulyana with linux version 5.4.0-45 in which i am facing a problem of a blank black screen on boot or either a black screen with a dash on top left corner.Its been happening for last one week since i just started using linux this very week. ** 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/1894232 Title: blank black screen or cursor on top left corner on a black screen problem Status in linux package in Ubuntu: New Bug description: i am currently using linux mint 20 ulyana with linux version 5.4.0-45 in which i am facing a problem of a blank black screen on boot or either a black screen with a dash on top left corner.Its been happening for last one week since i just started using linux this very week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894230] [NEW] Device queue depth should be 31 not 32
Public bug reported:
Setting drive device/queue_depth to 31 from 32 resolved an issue whereby
I had numerous zpool and ATA errors but only under high load (zpool
scrub) or when trimming the drives. Was able to reduce incidence by
setting to libata.force=noncqtrim, and resolve with libata.force=noncq,
but with an obvious performance impact.
Upstream kernel seems to be aware of this issue, so I'm assuming this is
a downstream or udev configuration issue, see:
https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ
Scrub repaired all errors, but, because repairs were made, it seems like
it's not just a communications issue, and that there is the potential
for DATA LOSS on non-redundant and/or non-ZFS configurations.
Sample syslog error:
[ 33.688898] ata1.00: exception Emask 0x50 SAct 0x1003000 SErr 0x4c0900
action 0x6 frozen
[ 33.688908] ata1.00: irq_stat 0x0800, interface fatal error
[ 33.688913] ata1: SError: { UnrecovData HostInt CommWake 10B8B Handshk }
[ 33.688917] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688923] ata1.00: cmd 61/00:60:df:28:3d/01:00:2a:00:00/40 tag 12 ncq dma
131072 out
[ 33.688929] ata1.00: status: { DRDY }
[ 33.688931] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688937] ata1.00: cmd 61/08:68:18:a9:d2/00:00:04:00:00/40 tag 13 ncq dma
4096 out
[ 33.688942] ata1.00: status: { DRDY }
[ 33.688945] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688951] ata1.00: cmd 61/00:c0:df:27:3d/01:00:2a:00:00/40 tag 24 ncq dma
131072 out
[ 33.688956] ata1.00: status: { DRDY }
[ 33.688963] ata1: hard resetting link
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/bugs/1894230/+attachment/5407655/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894230
Title:
Device queue depth should be 31 not 32
Status in linux package in Ubuntu:
Incomplete
Bug description:
Setting drive device/queue_depth to 31 from 32 resolved an issue
whereby I had numerous zpool and ATA errors but only under high load
(zpool scrub) or when trimming the drives. Was able to reduce
incidence by setting to libata.force=noncqtrim, and resolve with
libata.force=noncq, but with an obvious performance impact.
Upstream kernel seems to be aware of this issue, so I'm assuming this
is a downstream or udev configuration issue, see:
https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ
Scrub repaired all errors, but, because repairs were made, it seems
like it's not just a communications issue, and that there is the
potential for DATA LOSS on non-redundant and/or non-ZFS
configurations.
Sample syslog error:
[ 33.688898] ata1.00: exception Emask 0x50 SAct 0x1003000 SErr 0x4c0900
action 0x6 frozen
[ 33.688908] ata1.00: irq_stat 0x0800, interface fatal error
[ 33.688913] ata1: SError: { UnrecovData HostInt CommWake 10B8B Handshk }
[ 33.688917] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688923] ata1.00: cmd 61/00:60:df:28:3d/01:00:2a:00:00/40 tag 12 ncq
dma 131072 out
[ 33.688929] ata1.00: status: { DRDY }
[ 33.688931] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688937] ata1.00: cmd 61/08:68:18:a9:d2/00:00:04:00:00/40 tag 13 ncq
dma 4096 out
[ 33.688942] ata1.00: status: { DRDY }
[ 33.688945] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688951] ata1.00: cmd 61/00:c0:df:27:3d/01:00:2a:00:00/40 tag 24 ncq
dma 131072 out
[ 33.688956] ata1.00: status: { DRDY }
[ 33.688963] ata1: hard resetting link
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894230/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894230] 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 1894230
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/1894230
Title:
Device queue depth should be 31 not 32
Status in linux package in Ubuntu:
Incomplete
Bug description:
Setting drive device/queue_depth to 31 from 32 resolved an issue
whereby I had numerous zpool and ATA errors but only under high load
(zpool scrub) or when trimming the drives. Was able to reduce
incidence by setting to libata.force=noncqtrim, and resolve with
libata.force=noncq, but with an obvious performance impact.
Upstream kernel seems to be aware of this issue, so I'm assuming this
is a downstream or udev configuration issue, see:
https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ
Scrub repaired all errors, but, because repairs were made, it seems
like it's not just a communications issue, and that there is the
potential for DATA LOSS on non-redundant and/or non-ZFS
configurations.
Sample syslog error:
[ 33.688898] ata1.00: exception Emask 0x50 SAct 0x1003000 SErr 0x4c0900
action 0x6 frozen
[ 33.688908] ata1.00: irq_stat 0x0800, interface fatal error
[ 33.688913] ata1: SError: { UnrecovData HostInt CommWake 10B8B Handshk }
[ 33.688917] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688923] ata1.00: cmd 61/00:60:df:28:3d/01:00:2a:00:00/40 tag 12 ncq
dma 131072 out
[ 33.688929] ata1.00: status: { DRDY }
[ 33.688931] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688937] ata1.00: cmd 61/08:68:18:a9:d2/00:00:04:00:00/40 tag 13 ncq
dma 4096 out
[ 33.688942] ata1.00: status: { DRDY }
[ 33.688945] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688951] ata1.00: cmd 61/00:c0:df:27:3d/01:00:2a:00:00/40 tag 24 ncq
dma 131072 out
[ 33.688956] ata1.00: status: { DRDY }
[ 33.688963] ata1: hard resetting link
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894230/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894230] Re: Device queue depth should be 31 not 32
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894230/+attachment/5407656/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894230
Title:
Device queue depth should be 31 not 32
Status in linux package in Ubuntu:
Incomplete
Bug description:
Setting drive device/queue_depth to 31 from 32 resolved an issue
whereby I had numerous zpool and ATA errors but only under high load
(zpool scrub) or when trimming the drives. Was able to reduce
incidence by setting to libata.force=noncqtrim, and resolve with
libata.force=noncq, but with an obvious performance impact.
Upstream kernel seems to be aware of this issue, so I'm assuming this
is a downstream or udev configuration issue, see:
https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ
Scrub repaired all errors, but, because repairs were made, it seems
like it's not just a communications issue, and that there is the
potential for DATA LOSS on non-redundant and/or non-ZFS
configurations.
Sample syslog error:
[ 33.688898] ata1.00: exception Emask 0x50 SAct 0x1003000 SErr 0x4c0900
action 0x6 frozen
[ 33.688908] ata1.00: irq_stat 0x0800, interface fatal error
[ 33.688913] ata1: SError: { UnrecovData HostInt CommWake 10B8B Handshk }
[ 33.688917] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688923] ata1.00: cmd 61/00:60:df:28:3d/01:00:2a:00:00/40 tag 12 ncq
dma 131072 out
[ 33.688929] ata1.00: status: { DRDY }
[ 33.688931] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688937] ata1.00: cmd 61/08:68:18:a9:d2/00:00:04:00:00/40 tag 13 ncq
dma 4096 out
[ 33.688942] ata1.00: status: { DRDY }
[ 33.688945] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.688951] ata1.00: cmd 61/00:c0:df:27:3d/01:00:2a:00:00/40 tag 24 ncq
dma 131072 out
[ 33.688956] ata1.00: status: { DRDY }
[ 33.688963] ata1: hard resetting link
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894230/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894229] [NEW] oops occurred starting up QEMU KVM VMs on amd64 host with 5.8.0-18-generic
Public bug reported: Just started up some QEMU KVM VMs and I got the following splats with amd64 5.8.0-18-generic: [ 923.230491] BUG: kernel NULL pointer dereference, address: 03d8 [ 923.230529] #PF: supervisor read access in kernel mode [ 923.230548] #PF: error_code(0x) - not-present page [ 923.230568] PGD 0 P4D 0 [ 923.230582] Oops: [#1] SMP PTI [ 923.230598] CPU: 3 PID: 1996 Comm: thermald Tainted: P OE 5.8.0-18-generic #19-Ubuntu [ 923.230631] Hardware name: Intel Corporation Intel\xae Server Board S1200V3RPS UEFI Development Kit/ROMLEY, BIOS 7.0 09/06/2016 [ 923.230675] RIP: 0010:cpufreq_set_cur_state.part.0.isra.0+0x9c/0x150 [ 923.230699] Code: 48 8b 14 d5 a0 49 a9 aa 48 8b 04 c5 a0 49 a9 aa 0f b7 8c 1a ea 00 00 00 66 39 8c 18 ea 00 00 00 75 ba 48 8b 4d c0 4c 8b 24 08 <49> 8b 84 24 d8 03 00 00 48 85 c0 74 a5 48 3d 00 f0 ff ff 77 9d 44 [ 923.230761] RSP: 0018:bf9442173d90 EFLAGS: 00010246 [ 923.230782] RAX: 9fa4efc0 RBX: 00011260 RCX: 0002a408 [ 923.230807] RDX: 9fa4efc8 RSI: RDI: ab272be0 [ 923.230833] RBP: bf9442173dd0 R08: R09: [ 923.230859] R10: 000a R11: f000 R12: [ 923.230886] R13: 0002 R14: R15: [ 923.230911] FS: 7f55c9654700() GS:9fa4efcc() knlGS: [ 923.230940] CS: 0010 DS: ES: CR0: 80050033 [ 923.230962] CR2: 03d8 CR3: 00041df88001 CR4: 001626e0 [ 923.230988] Call Trace: [ 923.231003] ? cpufreq_driver_resolve_freq+0x150/0x150 [ 923.231024] processor_set_cur_state+0xbc/0x140 [ 923.231043] cur_state_store+0x72/0xd0 [ 923.231061] dev_attr_store+0x17/0x30 [ 923.231078] sysfs_kf_write+0x3f/0x50 [ 923.231093] kernfs_fop_write+0xda/0x1b0 [ 923.231110] vfs_write+0xc9/0x200 [ 923.231124] ksys_write+0x67/0xe0 [ 923.231139] __x64_sys_write+0x1a/0x20 [ 923.231156] do_syscall_64+0x52/0xc0 [ 923.231172] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 923.231192] RIP: 0033:0x7f55cc32d2cf [ 923.231207] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48 [ 923.231274] RSP: 002b:7f55c96525e0 EFLAGS: 0293 ORIG_RAX: 0001 [ 923.231302] RAX: ffda RBX: 7f55cc52f790 RCX: 7f55cc32d2cf [ 923.231329] RDX: 0001 RSI: 7f55c96526e0 RDI: 0009 [ 923.231355] RBP: 0009 R08: R09: 0013 [ 923.231381] R10: R11: 0293 R12: 7f55c9652610 [ 923.231407] R13: 7f55c96526d0 R14: 7f55c96526b0 R15: 7f55cc52f740 [ 923.231434] Modules linked in: vhost_net vhost tap vhost_iotlb xt_conntrack ipt_REJECT nf_reject_ipv4 xt_CHECKSUM nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter xt_tcpudp nft_compat bridge stp vboxnetadp(OE) llc vboxnetflt(OE) nf_tables vboxdrv(OE) nfnetlink binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) asix usbnet mii joydev input_leds snd_soc_rt5640 snd_soc_rl6231 snd_soc_core snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_compress ac97_bus snd_hda_core snd_pcm_dmaengine snd_hwdep ppdev intel_rapl_msr snd_pcm at24 snd_timer intel_rapl_common snd parport_pc x86_pkg_temp_thermal intel_powerclamp intel_pch_thermal intel_hid intel_vbtn mac_hid soundcore acpi_als kfifo_buf coretemp ipmi_si parport industrialio ipmi_devintf ie31200_edac efi_pstore ipmi_msghandler sparse_keymap kvm_intel kvm rapl intel_cstate acpi_pad nfsd sch_fq_codel [ 923.231468] auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul mgag200 hid_generic crc32_pclmul drm_kms_helper ghash_clmulni_intel syscopyarea ahci sysfillrect sysimgblt aesni_intel fb_sys_fops cec usbhid rc_core crypto_simd hid cryptd glue_helper igb i2c_i801 libahci drm e1000e lpc_ich i2c_smbus dca i2c_algo_bit video [ 923.238215] CR2: 03d8 [ 923.239115] ---[ end trace 5a28929742201640 ]--- [ 923.290723] RIP: 0010:cpufreq_set_cur_state.part.0.isra.0+0x9c/0x150 [ 923.291755] Code: 48 8b 14 d5 a0 49 a9 aa 48 8b 04 c5 a0 49 a9 aa 0f b7 8c 1a ea 00 00 00 66 39 8c 18 ea 00 00 00 75 ba 48 8b 4d c0 4c 8b 24 08 <49> 8b 84 24 d8 03 00 00 48 85 c0 74 a5 48 3d 00 f0 ff ff 77 9d 44 [ 923.293538] RSP: 0018:bf9442173d90 EFLAGS: 00010246 [ 923.294435] RAX: 9fa4efc0 RBX: 00011260 RCX: 0002a408 [ 923.295318] RDX: 9fa4efc8 RSI: RDI: ab272be0 [
[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17
But when booting with 5.4.0-42-generic it works without freezing. -- 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/1892714 Title: Microphone not working on HP Omen 17 Status in linux-firmware package in Ubuntu: Triaged Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1892714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891437] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-04 08:39 EDT--- *** Bug 184194 has been marked as a duplicate of this bug. *** -- 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/1891437 Title: [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: SRU Justification: == [Impact] * If a NVMe drive is assigned/hotplugged to a Linux on s390x LPAR, a bug in lib/list_debug.c is hit and the device is not accessible. * The reason is a missing /dev/ file -- lspci does not report it either. [Fix] * 3047766bc6ec9c6bc9ece85b45a41ff401e8d988 3047766bc6ec "s390/pci: fix enabling a reserved PCI function" [Test Case] * Assign a NMVe drive to your LPAR (using the HMC) * Unassign the NVMe drive from your LPAR * Reassign it to your LPAR again * Look at dmesg for 'kernel BUG at lib/list_debug.c' [Regression Potential] * There is some regression risk with having code changes in the zPCI sub-system. * zPCI is the PCI implementation on s390x, modifications here do not affect any other architecture. * It could be that PCI events do not work anymore and NVMe devices don't IPL (boot) on s390x anymore. * However, the code changes below to a single file: arch/s390/pci/pci_event.c * and IPL from NVMe is brand new in Ubuntu for s390x, * and zPCI devices are less wide-spread compared to ccw devices on s390x. * On top a test kernel was build and made available for further testing. [Other] * Since the fix/patch got upstream accepted with kernel v5.8-rc5, it's already in the groovy proposed kernel 5.8, hence this SRU is for focal only. __ When a NVMe drive is assigned/hotplugged to a Linux LPAR then a bug is hit in lib/list_debug.c. And the device is not accessible, there is no /dev/ file and lspci does not report it also. [ 1681.564462] list_add double add: new=eed0f808, prev=eed0f808, next=4070a300. [ 1681.564489] [ cut here ] [ 1681.564490] kernel BUG at lib/list_debug.c:31! [ 1681.564504] monitor event: 0040 ilc:2 [#1] SMP [ 1681.564507] Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter s390_trng ghash_s390 prng aes_s390 des_s390 libdes sha512_s390 vfio_ccw sha1_s390 vfio_mdev mdev chsc_sch vfio_iommu_type1 eadm_sch vfio ip_tables dm_service_time nvme crc32_vx_s390 sha256_s390 sha_common nvme_core qeth_l2 zfcp qeth scsi_transport_fc qdio ccwgroup dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt [ 1681.564534] CPU: 6 PID: 139 Comm: kmcheck Not tainted 5.8.0-rc1+ #2 [ 1681.564535] Hardware name: IBM 8561 T01 701 (LPAR) [ 1681.564536] Krnl PSW : 0704c0018000 3ffcadb8 (__list_add_valid+0x70/0xa8) [ 1681.564544]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 1681.564545] Krnl GPRS: 0040 0027 0058 0007 [ 1681.564546]3ffcadb4 03e0051a7ce0 [ 1681.564547]4070a300 eed0f808 eed0f808 4070a300 [ 1681.564548]f56a2000 40c2c788 3ffcadb4 03e0051a7bc8 [ 1681.564583] Krnl Code: 3ffcada8: c02000302b09larl %r2,405d03ba 3ffcadae: c0e5ffdd30b1brasl %r14,3fb70f10 #3ffcadb4: af00mc 0,0 >3ffcadb8: b9040054lgr %r5,%r4 3ffcadbc: c02000302aadlarl %r2,405d0316 3ffcadc2: b9040041lgr %r4,%r1 3ffcadc6: c0e5ffdd30a5brasl %r14,3fb70f10 3ffcadcc: af00mc 0,0 [ 1681.564592] Call Trace: [ 1681.564594] [<3ffcadb8>] __list_add_valid+0x70/0xa8 [ 1681.564596] ([<3ffcadb4>] __list_add_valid+0x6c/0xa8) [ 1681.564599] [<3faf2920>] zpci_create_device+0x60/0x1b0 [ 1681.564601] [<3faf704a>] zpci_event_availability+0x282/0x2f0 [ 1681.564605]
[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: perf-tools-unstable (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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Fix Released Status in perf-tools-unstable package in Ubuntu: Confirmed Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man
[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal
Re: PermissionError: [Errno 1] Operation not permitted: '/sys/kernel/debug/tracing/../kprobes/blacklist' This can be fixed by a patch to the bpfcc libs found at: https://github.com/iovisor/bcc/commit/5558e36bd97ace7bc3efe3a70d0c9d4fc0d34e2a?branch=5558e36bd97ace7bc3efe3a70d0c9d4fc0d34e2a=unified #diff-978dbb2c496647b4b9907f64485be957R614 Please incorporate into next update of python3-bpfcc. This is ridiculous. Wonder how many other things this breaks. -- 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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Fix Released Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@PowerKiKi Yes, this is just a temporary step until I finish minimizing the verbs. I was hoping it would be as easy as just finding the single command or two in the group of 788, but it appears to be a longer combination of sequences, so will take just a bit more tinkering to isolate. I will get it sorted and then we can ask Mike to add it as part of his patch. I didn't test with bluetooth headphones (I still use old school wired ones), but bluetooth is a completely different pathway and bluetooth audio has always worked on mine from the very start. I am able to go between regular headphones and the speakers now and pulse changes the source automatically back and forth, so for me at least, it is not as bad as the original stickiness problem. Pretty much once I boot and run the script it lasts until I reboot. As you suggest, we can hopefully even eliminate that step once Mike adds to a patch... -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter:
[Kernel-packages] [Bug 1847105]
If you have followed the mailing list discussion, this might be: - stay as-is in virt-manager - improve libvirt to explicitly select the prealloc mode (optional) - zfs got a fix to no more surface such an unexpected waiting time (but in to be released 2.0) The discussion isn't over but I wanted to summarize here as well for everyone just reading this bug now or later. -- 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/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Confirmed Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16 real 1m43,196s user 0m3,564s sys 1m26,720s andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 image: with-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.7M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 2,8M with-prealloc-image.qcow2 andreas@nsn7:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libvirt-daemon 5.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 11:36:03 2019 InstallationDate: Installed on 2019-10-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml']
[Kernel-packages] [Bug 1847105]
Hi, as outlined above the behavior is still wrong. The patch suggested in [1] will fix the behavior of libvirt to what it was meant to be when preallocation=falloc was added. But now virt-manager comes into play, the XML sent by virt-manager is exactly matching the definition of the use case to use falloc. So virt-manager triggered storage request will continue to use falloc despite libvirt being "fixed to how it was intended". The question now is should we consider changing the XML virt-manager submits so that we are back at the much faster preallocation=metadata mode? [1]: https://www.redhat.com/archives/libvir- list/2020-September/msg00105.html -- 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/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Confirmed Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16 real 1m43,196s user 0m3,564s sys 1m26,720s andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 image: with-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.7M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 2,8M with-prealloc-image.qcow2 andreas@nsn7:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libvirt-daemon 5.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 11:36:03 2019 InstallationDate: Installed on 2019-10-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible:
[Kernel-packages] [Bug 1893914] Re: [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893914 Title: [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] When stress S3 on AMD 0x15e5 usb host controller, it failed to resume. The controller indicates "internal Host Controller Error" [Fix] To fix this, sparse controller enable bit has to be disabled. [Test Case] Verified on the target platform, OK for 100 times of S3. [Regression Potential] Low, Add specific ID quirk for hw, no other hw related, tested with positive results. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407599/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407602/+files/gdm3_3.34.1-1ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: In Progress Status in gdm3 package in Ubuntu: In Progress Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I'd confirmed the regression with enabling Wayland. Due to nvidia-driver (nvidia-driver-440) disable wayland as default, I'll separate the verification to two scenarios. 1. Make sure the new gdm3 fixes this issue. 2. Make sure the new gdm3 without the regression (https://gitlab.gnome.org/GNOME/gdm/-/issues/602) --- * Make sure the new gdm3 fixes this issue * [Summary] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1. Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically". 2. Install with default options 2.1 Install nvidia-driver-440 (450.66-0ubuntu2) from ubuntu-archive. 2.2 Enable "Login automatically" from system settings. After reboot, the system won't login automatically even can not login manually. [Environment] HP 800 G6 DM + GeForce GTX 1660 [10de:2191] [Solution] Backport the solution from comment#119 as a debian package[2] (commit ID from upstream: f843233a, 690b3c01). The problem is solved. (Verified in scenario 2) The debdiff as attachment, please help to review. [1] sha256sum ``` $ sha256sum ~/Downloads/groovy-desktop-amd64.iso bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 /home/jeremysu/Downloads/groovy-desktop-amd64.iso ``` [2] gdm3 from https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801/+packages --- * Make sure the new gdm3 without the regression (https://gitlab.gnome.org/GNOME/gdm/-/issues/602) * This issue is happens when switching user under Wayland. I'd verified gdm3#602 issue when using intel graphic in the same machine because nvidia-driver disable Wayland as default. Steps to reproduce gdm3#602 issue: 1. Login a user "test" under x11 2. Create a user "test2" 3. Press "switch user ..." to "test2" under wayland 4. Switch back to "test" under x11 5. Switch to "test2" under wayland (then the running session be killed immediately) 6. Login again and then the mouse won't work. After applying commit 690b3c01, above problems are solved. Repeat to switch user and everything goes well. ** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407599/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5406013/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Description changed: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: - 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. + 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 - [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 - [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 + [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 + [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64
[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Changed in: xorg-server (Ubuntu) Status: Triaged => 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/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 1893831] Re: linux-image-unsigned-5.4.0-46-generic wont initialize console
"initialize console": Did you mean switch to virtual console session by Ctrl-Alt-F3, or by booting to console-only runlevel by type e in grub and append 3 to `linux ` line? -- 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/1893831 Title: linux-image-unsigned-5.4.0-46-generic wont initialize console Status in linux package in Ubuntu: Confirmed Bug description: linux-image-unsigned-5.4.0-46-generic wont initialize console as expected. No monitor is used or found. No graphics, no text console. Only a blank black screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-unsigned-5.4.0-46-generic 5.4.0-46.50 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps6668 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 1 21:20:15 2020 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3240 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-04-27 (493 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894157] Re: No recupera tras suspensión en MacBook Pro
Can you please translate the bug to English? -- 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/1894157 Title: No recupera tras suspensión en MacBook Pro Status in linux package in Ubuntu: Confirmed Bug description: Se fuerza el apagado con el botón de encendido, no funciona "resume". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1193 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Sep 3 23:57:55 2020 InstallationDate: Installed on 2020-08-31 (3 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro4,1 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=3a38607a-f3e9-4f46-840c-edf92ddc3ad9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP41.88Z.00C1.B00.0802091544 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F42C89C8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B00.0802091544:bd02/09/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro4,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889110] Re: zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than 120 seconds. "
Hi Rob, It may be worth exercising the raw device by performing a lot of random I/O reads rather that via zfs, that way we can eliminate zfs out of the equation to see if it's a controller or driver issue and not a zfs error. That way we can at least use occams razor to remove a lot of software complexity from the debugging process. -- 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/1889110 Title: zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than 120 seconds. " Status in zfs-linux package in Ubuntu: Incomplete Bug description: ZFS filesystem becomes unresponsive and subsequent NFS shares unresponsive. ESXi sees all paths down. See this error 3 times in a row. [184383.479511] INFO: task txg_sync:4307 blocked for more than 120 seconds. [184383.479565] Tainted: P IO 5.4.0-42-generic #46-Ubuntu [184383.479607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [184383.479655] txg_syncD0 4307 2 0x80004000 [184383.479658] Call Trace: [184383.479670] __schedule+0x2e3/0x740 [184383.479673] schedule+0x42/0xb0 [184383.479676] schedule_timeout+0x152/0x2f0 [184383.479683] ? __next_timer_interrupt+0xe0/0xe0 [184383.479685] io_schedule_timeout+0x1e/0x50 [184383.479697] __cv_timedwait_common+0x15e/0x1c0 [spl] [184383.479702] ? wait_woken+0x80/0x80 [184383.479710] __cv_timedwait_io+0x19/0x20 [spl] [184383.479816] zio_wait+0x11b/0x230 [zfs] [184383.479905] ? __raw_spin_unlock+0x9/0x10 [zfs] [184383.479983] dsl_pool_sync+0xbc/0x410 [zfs] [184383.480069] spa_sync_iterate_to_convergence+0xe0/0x1c0 [zfs] [184383.480156] spa_sync+0x312/0x5b0 [zfs] [184383.480245] txg_sync_thread+0x27a/0x310 [zfs] [184383.480334] ? txg_dispatch_callbacks+0x100/0x100 [zfs]
[Kernel-packages] [Bug 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
Passed with F-kvm 5.4.0-1022.22 -- 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/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Bionic: Fix Committed Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Released Bug description: == SRU Justification [ FOCAL ] == The msg_zerocopy.sh kernel self test will fail on machines that don't have 2 or 3 CPUs such as 1 CPU cloud instances since the C test program tries to set CPU affinity to CPUs 2 and 3 and bails out if it fails. == Fix == Upstream linux-next commit commit 16f6458f2478b55e2b628797bc81a4455045c74e Author: Willem de Bruijn Date: Wed Aug 5 04:40:45 2020 -0400 selftests/net: relax cpu affinity requirement in msg_zerocopy test The fix now just emits a warning that CPU affinity can't be set rather than cause an exit(1) termination. == Test cast == Run the msg_zerocopy.sh test from the kernel net selftest on a 1 CPU system. Without the fix the test fails. With the fix it runs successfully as expected. == Regression Potential == The original test pinned the CPUs for a benchmarking metric, for our testing we are using this to test to see if the operations in the test work successfully. There is a potential that users using this test will not notice the warning if they are using this test as a benchmark on a 1 CPU system and may get more jittery timing in their benchmarks rather than a test failing and complaining they are not running it on a suitable multi-CPU system. However, the likelyhood of a user using this test on a single CPU system for benchmarking is small and as it stands the test will now run and produce potentially jittery benchmarks on a 1 CPU system compared to previously where it never ran. This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 07:50:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux
** Tags added: sru-20200831 -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1 This failure is similar to bug 1884234, however, this test didn't fail on ADT with focal/linux before 5.4.0-44.48. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892213/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1893914] Re: [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3
verified on linux-image-unsigned-5.6.0-1025-oem. 60 times of S3 with positive result. -- 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/1893914 Title: [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] When stress S3 on AMD 0x15e5 usb host controller, it failed to resume. The controller indicates "internal Host Controller Error" [Fix] To fix this, sparse controller enable bit has to be disabled. [Test Case] Verified on the target platform, OK for 100 times of S3. [Regression Potential] Low, Add specific ID quirk for hw, no other hw related, tested with positive results. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882088] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-04 03:06 EDT--- IBM Bugzilla status-> closed, Fix Released with all requested distros. -- 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/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * Connections from later-level SMC (protocol) versions to an SMC- enabled server on Linux hang. * Later-level versions of SMC (although backwards-compatible) present a higher version number and use larger messages during the CLC handshake. * The solution to avoid such hangs is to introduce toleration for later version numbers, and support CLC messages of arbitrary length. [Fix] * fb4f79264c0fc6fd5a68ffe3e31bfff97311e1f1 fb4f79264c0f "net/smc: tolerate future SMCD versions" [Test Case] * Requires two IBM z13/z13s GA2 or LinuxONE Rockhopper/Emperor systems with RoCE Express adapter v2(.1) for SMC-D usage. * One system needs to run the initial SMC-D version, the other a newer version. * Establish a connection between both system and monitor/verify if it's reliable or if it hangs. [Regression Potential] * The regression can be considered as medium to low: * Since SMC-D is a pretty special way of doing shared memory communications and not that wide-spread. * However, the code that is changed is common code. * But the patch is straight forward and only modifies /net/smc/smc_clc.c and /net/smc/smc_clc.h * It largely bumps limits (allows larger messages), adds a check and introduces toleration, rather than changing control or flow. [Other] * The above fix is currently in 'linux-next' and tagged with next-20200709. * It is still assumed that it gets accepted for 5.8. * However, since this is not guaranteed this SRU request is for focal and groovy - to make sure that no potential regressions are introduced in case the patch will not end up in 5.8. __ Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886814] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-04 03:04 EDT--- IBM Bugzilla status->closed, Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886814 Title: posix_spawn usage in gnu make causes failures on s390x Status in Ubuntu on IBM z Systems: Fix Released Status in flatpak package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in make-dfsg package in Ubuntu: Invalid Bug description: posix_spawn usage in gnu make causes failures on s390x Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it started to use posix_spawn, instead of fork()/exec(). This has caused failure of an unrelated package flatpak-builder autopkgtests on s390x only, like so echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 Julian Klaude investigated this in-depth. His earlier research also indicated that this is a heisenbug, if one tries to print to stderr before printing to stdout, no issue occurs. We are configuring GNU make to be build with --disable-posix-spawn on s390x only. We passed these details to Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964541 too. But I do wonder, if there is something different or incorrect about posix_spawn() implementation in either glibc, or linux kernel, on s390x. Or gnu-make's usage of posix_spawn(). As otherise, using posix_spawn() in gnu-make works on other architectures, and flatpak-builder autopkgtests pass too. It seems very weird that stdout does not appear to be functional, unless stderr was opened/written to, from gnu-make execution compiled with posix-spawn feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887124] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-04 02:35 EDT--- IBM Buzgilla status->closed, now released for all requested distros... -- 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/1887124 Title: [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally, in case one activates either zfcp DIF (data integrity field) or DIX (data integrity extention) and attaches any LU. * zfcp used to allocate/add the shost object for a HBA, before knowing all the HBA's capabilities. But later the shost object got patched to make more of the capabilities known - including the protection capabilities. * Changes that are later made to the protection capabilities don't get reflected in the tag-set requests and are missing. * Now sending I/O, scsi_mod tries to access the protection payload data, that isn't there, and the kernel crashes. [Fix] * The SRU request was created as pull request, so please pull starting at 0b38938af911 to head / 9227405ee311 from https://code.launchpad.net/~fheimes/+git/lp1887124 [Test Case] * Have a IBM Z or LInuxONE system (ideally on LPAR) in place that is connected to a DS8xxx storage subsystem that supports, zfcp SCSI storage with DIF and DIX. * Have an Ubuntu Server 20.04 installed in such a LPAR system. * Now enable DIF (zfcp.dif=1) or DIX (zfcp.dix=1) and connect the system to a logical unit. * Monitor the system for any kernel crashes (/var/log/syslog and /var/log/kern.log) - look for kernel panic in scsi_queue_rq. [Regression Potential] * Even if the modifications are substantial, the regression potnetial can be considered as moderate. * This issue could be mainly tracked down to commit '737eb78e82d5' (made for v5.4) that made the problem more visible. * With the old blk queue DIF/DIX worked fine, but after scsi_mod switched to blk-mq (and because requests are now all allocated during allocation time of the blk-mq tag-set), it didn't worked anymore. * The solution is to allocate/add the shost object for a HBA after all of its base capabilities are known. * Since the situation is like this for quite a while, several places in the zfcp driver code (where it's assumed that the shost object was correctly allocated) needed to be touched. * This is finally the reason (as well as the fact that some parts depend on code that went upstream with the kernels 5.5 and 5.7) for this rather big patchset for fixing DIF and DIX support in zfcp. * On the other hand side this entire set is now upstream accepted and entirely included in 5.8 (and with that soon in groovy), and no 5.4-specific (hand-crafted) backports are needed. * Also notice that all modifications are in the zfcp driver layer, hence they are s390x specific, and with that limited to /drivers/s390/scsi/zfcp_* * Finally the patches were already tested with a patched focal kernel with DIF/DIX/NONE, with I/O, and local/remote cable pulls - switched and point-to-point connected. No regressions were identified. [Other] * Alternatively the patches can also be cherry-picked from linux master with: git cherry-pick 92953c6e0aa7~1..e76acc519426 git cherry-pick a3fd4bfe85fb git cherry-pick e05a10a05509~1..42cabdaf103b git cherry-pick cec9cbac5244 git cherry-pick 978857c7e367~1..d0dff2ac98dd * The following lists the individual commits - just for the reason of completeness: * 92953c6e0aa77d4febcca6dd691e8192910c8a28 92953c6e0aa77 "scsi: zfcp: signal incomplete or error for sync exchange config/port data" * 7e418833e68948cb9ed15262889173b7db2960cb 7e418833e6894 "scsi: zfcp: diagnostics buffer caching and use for exchange port data" * 088210233e6fc039fd2c0bfe44b06bb94328d09e 088210233e6fc "scsi: zfcp: add diagnostics buffer for exchange config data" * a10a61e807b0a226b78e2041843cbf0521bd0c35 a10a61e807b0a "scsi: zfcp: support retrieval of SFP Data via Exchange Port Data" * 6028f7c4cd87cac13481255d7e35dd2c9207ecae 6028f7c4cd87c "scsi: zfcp: introduce sysfs interface for diagnostics of local SFP transceiver" * 8155eb0785279728b6b2e29aba2ca52d16aa526f 8155eb0785279 "scsi: zfcp: implicitly refresh port-data diagnostics when reading sysfs" * 5a2876f0d1ef26b76755749f978d46e4666013dd 5a2876f0d1ef2 "scsi: zfcp: introduce sysfs interface to read the local B2B-Credit" * 8a72db70b5ca3c3feb3ca25519e8a9516cc60cfe 8a72db70b5ca3 "scsi: zfcp:
[Kernel-packages] [Bug 1881096] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-04 02:11 EDT--- IBM Bugzilla status-> closed, Fix Released with 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/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * d68d5d51dc898895b4e15bea52e5668ca9e76180 d68d5d51dc898895b "s390/cpum_cf: Add new extended counters for IBM z15" [Test Case] * Requires the fix/patch of the perf tool, as mentioned in the bug, too. * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only additional (s390x) hardware counters are defined and added. [Other] * This requires a patch to be included into the perf itself, too - please see bug description for more details. * Since this patch is upstream in kernel 5.7 it will automatically land in groovy. __ ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
