[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
OMG, this looks like it's it. On my main computer with Geforce 330M I have a background that's 1x screen res and I haven't been getting the corrupted background. I just switched to a stock Ubuntu bg image, which I presume is much larger than 1440x900, suspended the machine and now it's completely white. The corruption I now get after resume from suspend is this: 1. The Gnome menu (the one on the left after pressing the super key) when using Gnome session is corrupted or invisible. Moving the mouse over the icons makes them appear and closing and re-opening the overlay fixes it. The left menu from Ubuntu session seems fine, but I only tried a couple of suspends as I use the Gnome session. 2. Current program icon in the top bar of the Gnome session gets corrupted. 3. Icons in some applications (like Cura) get corrupted. I think it may be related to Qt. But I guess that would be a different bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Invalid Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873194] Re: clipit interface not working in 20.04
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873194 Title: clipit interface not working in 20.04 Status in clipit package in Ubuntu: Confirmed Bug description: When running clipit in focal fossa the interface will crash when opening the history list via shortcut (ctr + alt + h). Starting it from cli shows this error message: (clipit:7248): Gdk-CRITICAL **: 10:42:40.873: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Clipit version is 1.4.4+git20190202-1 from https://launchpad.net/ubuntu/focal/+package/clipit Ubuntu version is Ubuntu Focal Fossa (20.04) as of 2nd of May 2020 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-04-29 (1447 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-15 (0 days ago) UserGroups: adm cdrom dip docker kismet kvm lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/1873194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Sounds like a userspace issue. Have you tried any chromium based browser? -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 jackpoll_ms :
[Kernel-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
Do you see the issue on Ubuntu proper? -- 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/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. 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] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO 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.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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] Re: Very slow boot with kernel 5.4.0-37-generic
Would it be possible for you to do a kernel bisection? First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the working version you found) $ git bisect bad $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. -- 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/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887829] Re: graphic card not working
Please reproduce the freeze again, reboot and then immediately run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Incomplete -- 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/1887829 Title: graphic card not working Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes 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: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: 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.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/nvidia-graphics-drivers-340/+bug/1887829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886366] Re: USB External Drive Stalls and Timeouts
"linux-image-unsigned" is also needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886366 Title: USB External Drive Stalls and Timeouts Status in linux package in Ubuntu: Incomplete Bug description: Not sure of the package naming for the Linux Kernel. However since version 4.15.0.28 I've been getting timeouts like this in dmesg: [63075.835488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [63075.835491] scsi_eh_7 D0 273 2 0x80004000 [63075.835494] Call Trace: [63075.835504] __schedule+0x2b9/0x6c0 [63075.835507] schedule+0x42/0xb0 [63075.835510] schedule_preempt_disabled+0xe/0x10 [63075.835513] __mutex_lock.isra.0+0x182/0x4f0 [63075.835515] ? __switch_to_asm+0x40/0x70 [63075.835517] ? __switch_to_asm+0x34/0x70 [63075.835519] ? __switch_to_asm+0x34/0x70 [63075.835520] ? __switch_to_asm+0x40/0x70 [63075.835523] __mutex_lock_slowpath+0x13/0x20 [63075.835526] mutex_lock+0x2e/0x40 [63075.835531] device_reset+0x22/0x50 [usb_storage] [63075.835535] scsi_eh_ready_devs+0x56c/0xa30 [63075.835540] ? __pm_runtime_resume+0x60/0x80 [63075.835543] scsi_error_handler+0x432/0x500 [63075.835548] kthread+0x104/0x140 [63075.835550] ? scsi_eh_get_sense+0x210/0x210 [63075.835553] ? kthread_park+0x80/0x80 [63075.83] ret_from_fork+0x35/0x40 The drive works fine on kernels 4.15.0.28 and older. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nick 2943 F pulseaudio /dev/snd/controlC0: nick 2943 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2e62fe89-0a58-42ff-95bd-80760e43753b InstallationDate: Installed on 2014-12-31 (2014 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f21814d2-6d82-426b-a5e0-cb4734f1a929 ro quiet splash init=/lib/systemd/systemd vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 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 RfKill: Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-06-29 (7 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3506 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3506:bd01/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1887829] Re: graphic card not working
I installed 340 now let's see if the freeze problem still exists. On Fri, Jul 17, 2020 at 8:25 AM Daniel van Vugt <1887...@bugs.launchpad.net> wrote: > The Nvidia web site seems to confirm that 'GeForce 8400 GS' is only > supported by driver version 340. So please uninstall 390 and install 340 > instead. > > > ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1887829 > > Title: > graphic card not working > > Status in nvidia-graphics-drivers-390 package in Ubuntu: > Invalid > > Bug description: > graphic card not working properly so I have to switch to custom > graphic driver |If i use nvidia driver the system freezes after few > minutes > > 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: Thu Jul 16 22:06:22 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GraphicsCard: >NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] > [1043:8322] > InstallationDate: Installed on 2020-07-15 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic > root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/19/2009 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: DH55TC > dmi.board.vendor: Intel Corporation > dmi.board.version: AAE70932-206 > dmi.chassis.type: 3 > dmi.modalias: > dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: > 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.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/nvidia-graphics-drivers-390/+bug/1887829/+subscriptions > -- 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/1887829 Title: graphic card not working Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes 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: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M.
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@ Thank you for the detailed attempt to help. On my 20KHCTO1WW, with kernel 5.6.19-050619-generic, BIOS 1.49, and the latest updates delivered by fwup, I enabled the fingerprint reader and enabled S3 sleep. I did those things in the BIOS. Then I put the computer to sleep for ten minutes or so. Then I woke it. The trackpoint *still* did not work. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W
[Kernel-packages] [Bug 1879123] Re: kernel 4.15.99 & Cinamon freeze on suspend / resume on
[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/1879123 Title: kernel 4.15.99 & Cinamon freeze on suspend / resume on Status in linux package in Ubuntu: Expired Bug description: kernel 4.15.99 & Cinamon Mint 19.1 freeze on suspend / resume on desktop every time. At first lights on front board blink, but then stop blinking and screen stays black. With previous kernels it happened from time to time (once per month or so), now it happens every day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886390] Re: Fix an issue that HID devices are not scanned by Realtek 8822C
Do we have an ETA for this firmware update to complete the SRU process. We need to plan OEM image delivery schedule with it. Thanks. -- 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/1886390 Title: Fix an issue that HID devices are not scanned by Realtek 8822C Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Bug description: [Impact] HID devices are not scanned by Realtek 8822C Bluetooth, so keyboard or mouse cannot connect to the host. [Fix] New firmware release for 8822C. [Test] HID devices can be scanned now. Pairing and connecting also work. [Regression Potential] Low. It's an upstream firmware release. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1886390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880792] Re: linux-firmware: add sof-firmware and tplg files for tgl machines
** Merge proposal linked: https://code.launchpad.net/~kchsieh/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/387514 -- 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/1880792 Title: linux-firmware: add sof-firmware and tplg files for tgl machines Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Bug description: [Impact] When booting our 20.04 + oem-5.6 kernel on tgl platforms, the sof audio driver always fails to load the sof firmware, the audio function deosn't work at all on tgl platforms. [Fix] Intel released sof-firmware including tplg for tgl platforms, after putting them in the /lib/firmware/inte/sof|sof-tplg, the audio works well on those tgl platforms. [Test Case] Put those firmware and tplg to linux-firmware folders, boot 20.04 + oem-5.6 kernel on tgl platforms, the audio works well. [Regression Risk] Low, just adding some new files, no change on existing files. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887829] Re: graphic card not working
The Nvidia web site seems to confirm that 'GeForce 8400 GS' is only supported by driver version 340. So please uninstall 390 and install 340 instead. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Invalid -- 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/1887829 Title: graphic card not working Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes 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: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: 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.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/nvidia-graphics-drivers-390/+bug/1887829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887829] Re: graphic card not working
Oh, maybe the problem is simpler than that... Your kernel log is telling you that you have the wrong driver version installed. It's asking you to use version 340 instead: [ 2047.082719] NVRM: The NVIDIA GeForce 8400 GS GPU installed in this system is NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 390.138 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... -- 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/1887829 Title: graphic card not working Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes 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: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: 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.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/nvidia-graphics-drivers-390/+bug/1887829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887829] Re: graphic card not working
Please switch back to the Nvidia driver, reproduce the freeze again, reboot and then immediately run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- 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/1887829 Title: graphic card not working Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes 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: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: 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.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/nvidia-graphics-drivers-390/+bug/1887829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887829] [NEW] graphic card not working
You have been subscribed to a public bug: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes 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: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: 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.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 ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal nvidia ubuntu -- graphic card not working https://bugs.launchpad.net/bugs/1887829 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 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 1887595] Re: linux-firmware: integrate TGL_SOF_FW_prod_signed_v0.6.2_release for tigerlake machines
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High -- 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/1887595 Title: linux-firmware: integrate TGL_SOF_FW_prod_signed_v0.6.2_release for tigerlake machines Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: Fix Released Bug description: [Impact] There is no sof-firmware for tgl platforms in the focal and groovy, so the audio driver can't work on the tgl machines. [Fix] Intel released a firmware for tgl platforms, it is signed by production key. [Test Case] Install the TGL_SOF_FW_prod_signed_v0.6.2_release to /lib/firmware/intel/sof, boot the dell tgl machines, the sof driver loads the sof-firmware successfully, and the audio driver works well too. [Regression Risk] Low, this SRU adds new firmware, this firmware is only used by intel tgl machines, and Intel told us this firmware is signed by production key and is ok to release to ubuntu archive. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887728] 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/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. 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] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO 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.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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887796] Re: Bluetooth headset cant set output as A2DP sink while using the mic as input device
*** This bug is a duplicate of bug 1838151 *** https://bugs.launchpad.net/bugs/1838151 This is unfortunately not a bug, it's the Bluetooth standard... A2DP (high quality output) does not support any input. So if you enable input you will get forced back to HSP/HFP (which does sound terrible). But there's a solution coming in the form of a different standard, which we are tracking in bug 1838151. ** This bug has been marked a duplicate of bug 1838151 Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1887796 Title: Bluetooth headset cant set output as A2DP sink while using the mic as input device Status in bluez package in Ubuntu: Incomplete Bug description: I have the popular Sony WH-100XM3 headset. I can connect to the headset fine using bluetooth. I set the Output device in Sound Option, there are two configurations A2DP Sink (sounds great) and HSP/HFP (sounds terrible). If I set the input device to the headset, it silently switches the output configuration to HSP/HFP and so the audio sounds terrible. If I then switch the output configuation back to A2DP sink, the audio output sounds good again, but then the input device switches to something else. So the problem is that I cant use the headset as audio input while having the good-sounding output configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
Disk encryption should have no influence on display corruption. Most likely something else about the machine changed around the same time you enabled encryption. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. 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] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO 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.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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861284] Re: Build and ship a signed wireguard.ko
The -modules package of the -112 kernel contains the following wireguard module: â””[~]> modinfo /tmp/wireguard.ko filename: /tmp/wireguard.ko intree: Y alias: net-pf-16-proto-16-family-wireguard alias: rtnl-link-wireguard version:1.0.20200611 author: Jason A. Donenfeld description:WireGuard secure network tunnel license:GPL v2 srcversion: DB5EB522A99DFA7CDEC1B3A depends:udp_tunnel,ip6_udp_tunnel retpoline: Y name: wireguard vermagic: 4.15.0-112-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 -- 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/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847643] Re: iwlwifi during heavy transfers on XPS15 7590 (19.10)
** Tags added: hwe-networking-wifi ** Summary changed: - iwlwifi during heavy transfers on XPS15 7590 (19.10) + Intel Killer AX1650 [8086:2723] Subsystem [1a56:1654] iwlwifi during heavy transfers on XPS15 7590 (19.10) -- 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/1847643 Title: Intel Killer AX1650 [8086:2723] Subsystem [1a56:1654] iwlwifi during heavy transfers on XPS15 7590 (19.10) Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Bug description: I'm running 19.10 (beta). The Dell's 7590 wifi card is identified in `lspci` as: 3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a) From my googling the Dell 7590 seems to have a Killer AX1650 (in collaboration with Intel?) And when uploading a massive image to say S3, for example through CLI or browser, I get the following messages in `dmesg` after a few dozens of MB, at which point the net is killed and I need to turn the wifi off and on again to get online: [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump: [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6 [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0 [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0 [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1 [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2 [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1 [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2 [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1 [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2 [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3 [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1 [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2 [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0 [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1 [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2 [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3 [234483.616572] iwlwifi :3b:00.0: 0x | isr4 [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel [234483.616577] iwlwifi :3b:00.0: 0x | timestamp [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump: [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7 [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1 [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2 [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1 [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2 [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1 [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2 [234483.616657] iwlwifi :3b:00.0: 0x | umac data3 [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg [234483.616688] iwlwifi :3b:00.0: Fseq Registers: [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
If you have an Intel GPU then you should not be subscribed to this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887607] Re: NFS4.2: Cutting and Pasting files from NFS sec=sys to NFS sec=krb5p causes NFS to hang
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1887607 [Impact] - If you have a desktop system, with two NFS mounts: - - One that uses the baseline IP based security, aka sec=sys, + If you have a desktop system, with two NFS v4.2 mounts: + - One that uses the baseline IP based security, aka sec=sys, - and the other that uses Kerberos sec=krb5p based security, If you try and cut a file from the normal NFS mount, and paste it to a directory on the kerberos krb5p mount (using Nautilus), the NFS subsystem will lock up, Nautilus will hang, and the file won't be moved. The problem only reproduces if you cut and paste. Copying and pasting does not trigger any problems. Using mv in terminal doesn't reproduce either, you need to use Nautilus. The issue was introduced into 4.15.0-60-generic, by the commit: commit 594d1644cd59447f4fceb592448d5cd09eb09b5e Author: Chris Perl Date: Mon Dec 17 10:56:38 2018 -0500 Subject: NFS: nfs_compare_mount_options always compare auth flavors. - Link: https://github.com/torvalds/linux/commit/594d1644cd59447f4fceb592448d5cd09eb09b5e + Link: https://github.com/torvalds/linux/commit/594d1644cd59447f4fceb592448d5cd09eb09b5e It was backported to 4.15.0-60-generic from upstream -stable, and landed in 4.4.175, 4.14.99 and 4.19.21. The commit itself does not actually cause the problem, it simply removes a check for NFS server security settings, which simply reveals a broken codepath which the testcase triggers. Xenial 4.4.0-185-generic is not affected, only Bionic 4.15.0-60-generic onward. [Fix] The fix landed in 5.1-rc1, in the following commit: commit 02ef04e432babf8fc703104212314e54112ecd2d Author: Chuck Lever Date: Mon Feb 11 11:25:25 2019 -0500 Subject: NFS: Account for XDR pad of buf->pages - Link: https://github.com/torvalds/linux/commit/02ef04e432babf8fc703104212314e54112ecd2d + Link: https://github.com/torvalds/linux/commit/02ef04e432babf8fc703104212314e54112ecd2d The above commit more or less relies on the below commit as a dependency, and is included in the SRU: commit cf500bac8fd48b57f38ece890235923d4ed5ee91 Author: Chuck Lever Date: Mon Feb 11 11:25:20 2019 -0500 Subject: SUNRPC: Introduce rpc_prepare_reply_pages() Link: https://github.com/torvalds/linux/commit/cf500bac8fd48b57f38ece890235923d4ed5ee91 + + Also, as Andrea Righi pointed out, we need the following fixes commit: + + commit 29e7ca715f2a0b6c0a99b1aec1b0956d1f271955 + Author: Chuck Lever + Date: Tue Apr 9 10:44:16 2019 -0400 + Subject: NFS: Fix handling of reply page vector + Link: https://github.com/torvalds/linux/commit/29e7ca715f2a0b6c0a99b1aec1b0956d1f271955 It appears that some NFS calls return a NFS payload which is not a multiple of 4 bytes, but any payload sent over the network needs to be padded to an exact multiple of 4 bytes. It seems cutting and pasting from Nautilus triggers one such payload which is missing a byte, and it causes the NFS subsystem to hang during packet transmission. The fix ensures that all payloads use correct padding. [Testcase] You will need four machines. The first, is a kerberos KDC. Set up Kerberos correctly and create new service principals for the NFS server - and for the client. + and for the client. I used: nfs/nfskerb.mydomain.com and + nfs/client.mydomain.com. - The second machine will be a NFS server with the krb5p share. Add the - nfs server kerberos keys to the system's keytab, and set up a NFS server - that exports a directory with sec=krb5p. + The second machine will be a NFS server with the krb5p share. Add the nfs server kerberos keys to the system's keytab, and set up a NFS server that exports a directory with sec=krb5p. Example export: + /mnt/secretfolder *.mydomain.com(rw,sync,no_subtree_check,sec=krb5p) - The third machine is a regular NFS server. Export a directory with - normal sec=sys security. + The third machine is a regular NFS server. Export a directory with normal sec=sys security. Example export: + /mnt/sharedfolder *.mydomain.com(rw,sync) - The fourth is a desktop machine. Add the client kerberos keys to the - system's keytab. Mount both NFS shares, and generate some files full of - random data. I found 20MB from /dev/random works great. + The fourth is a desktop machine. Add the client kerberos keys to the system's keytab. Mount both NFS shares, making sure to use the NFS v4.2 protocol. I used the commands: + mount -t nfs4 nfskerb.mydomain.com:/mnt/secretfolder /mnt/secretfolder_client/ + mount -t nfs4 nfs.mydomain.com:/mnt/sharedfolder /mnt/sharedfolder_client + + Check "mount -l" to ensure that NFS v4.2 is used: + nfskerb.mydomain.com:/mnt/secretfolder on /mnt/secretfolder_client type nfs4 (rw,relatime,vers=4.2,<...>,sec=krb5p,<...>) + nfs.mydomain.com:/mnt/sharedfolder on /mnt/sharedfolder_client type nfs4 (rw,relatime,vers=4.2,<...>,sec=sys,<...>) + + Generate
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
And another data point: I wiped the computer clean and installed Ubuntu 18.04.4; the problem disappeared. TCP performance was near wire speed. Kernel: 4.15.0-111-generic #112-Ubuntu SMP Thu Jul 9 20:32:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux This clearly points to a regression in software, not a hardware or BIOS problem. -- 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/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0:
[Kernel-packages] [Bug 1886366] Re: USB External Drive Stalls and Timeouts
Tried installing the mainline kernel but does not show up in grub. Used these three packages: linux-headers-5.7.0-050700_5.7.0-050700.202006082127_all.deb linux-headers-5.7.0-050700-generic_5.7.0-050700.202006082127_amd64.deb linux-modules-5.7.0-050700-generic_5.7.0-050700.202006082127_amd64.deb No idea why it does not show up even after grub-update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886366 Title: USB External Drive Stalls and Timeouts Status in linux package in Ubuntu: Incomplete Bug description: Not sure of the package naming for the Linux Kernel. However since version 4.15.0.28 I've been getting timeouts like this in dmesg: [63075.835488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [63075.835491] scsi_eh_7 D0 273 2 0x80004000 [63075.835494] Call Trace: [63075.835504] __schedule+0x2b9/0x6c0 [63075.835507] schedule+0x42/0xb0 [63075.835510] schedule_preempt_disabled+0xe/0x10 [63075.835513] __mutex_lock.isra.0+0x182/0x4f0 [63075.835515] ? __switch_to_asm+0x40/0x70 [63075.835517] ? __switch_to_asm+0x34/0x70 [63075.835519] ? __switch_to_asm+0x34/0x70 [63075.835520] ? __switch_to_asm+0x40/0x70 [63075.835523] __mutex_lock_slowpath+0x13/0x20 [63075.835526] mutex_lock+0x2e/0x40 [63075.835531] device_reset+0x22/0x50 [usb_storage] [63075.835535] scsi_eh_ready_devs+0x56c/0xa30 [63075.835540] ? __pm_runtime_resume+0x60/0x80 [63075.835543] scsi_error_handler+0x432/0x500 [63075.835548] kthread+0x104/0x140 [63075.835550] ? scsi_eh_get_sense+0x210/0x210 [63075.835553] ? kthread_park+0x80/0x80 [63075.83] ret_from_fork+0x35/0x40 The drive works fine on kernels 4.15.0.28 and older. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nick 2943 F pulseaudio /dev/snd/controlC0: nick 2943 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2e62fe89-0a58-42ff-95bd-80760e43753b InstallationDate: Installed on 2014-12-31 (2014 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f21814d2-6d82-426b-a5e0-cb4734f1a929 ro quiet splash init=/lib/systemd/systemd vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 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 RfKill: Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-06-29 (7 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3506 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3506:bd01/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887607] Re: NFS4.2: Cutting and Pasting files from NFS sec=sys to NFS sec=krb5p causes NFS to hang
** Summary changed: - Cutting and Pasting files from NFS sec=sys to NFS sec=krb5p causes NFS to hang + NFS4.2: Cutting and Pasting files from NFS sec=sys to NFS sec=krb5p causes NFS to hang -- 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/1887607 Title: NFS4.2: Cutting and Pasting files from NFS sec=sys to NFS sec=krb5p causes NFS to hang Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1887607 [Impact] If you have a desktop system, with two NFS mounts: - One that uses the baseline IP based security, aka sec=sys, - and the other that uses Kerberos sec=krb5p based security, If you try and cut a file from the normal NFS mount, and paste it to a directory on the kerberos krb5p mount (using Nautilus), the NFS subsystem will lock up, Nautilus will hang, and the file won't be moved. The problem only reproduces if you cut and paste. Copying and pasting does not trigger any problems. Using mv in terminal doesn't reproduce either, you need to use Nautilus. The issue was introduced into 4.15.0-60-generic, by the commit: commit 594d1644cd59447f4fceb592448d5cd09eb09b5e Author: Chris Perl Date: Mon Dec 17 10:56:38 2018 -0500 Subject: NFS: nfs_compare_mount_options always compare auth flavors. Link: https://github.com/torvalds/linux/commit/594d1644cd59447f4fceb592448d5cd09eb09b5e It was backported to 4.15.0-60-generic from upstream -stable, and landed in 4.4.175, 4.14.99 and 4.19.21. The commit itself does not actually cause the problem, it simply removes a check for NFS server security settings, which simply reveals a broken codepath which the testcase triggers. Xenial 4.4.0-185-generic is not affected, only Bionic 4.15.0-60-generic onward. [Fix] The fix landed in 5.1-rc1, in the following commit: commit 02ef04e432babf8fc703104212314e54112ecd2d Author: Chuck Lever Date: Mon Feb 11 11:25:25 2019 -0500 Subject: NFS: Account for XDR pad of buf->pages Link: https://github.com/torvalds/linux/commit/02ef04e432babf8fc703104212314e54112ecd2d The above commit more or less relies on the below commit as a dependency, and is included in the SRU: commit cf500bac8fd48b57f38ece890235923d4ed5ee91 Author: Chuck Lever Date: Mon Feb 11 11:25:20 2019 -0500 Subject: SUNRPC: Introduce rpc_prepare_reply_pages() Link: https://github.com/torvalds/linux/commit/cf500bac8fd48b57f38ece890235923d4ed5ee91 It appears that some NFS calls return a NFS payload which is not a multiple of 4 bytes, but any payload sent over the network needs to be padded to an exact multiple of 4 bytes. It seems cutting and pasting from Nautilus triggers one such payload which is missing a byte, and it causes the NFS subsystem to hang during packet transmission. The fix ensures that all payloads use correct padding. [Testcase] You will need four machines. The first, is a kerberos KDC. Set up Kerberos correctly and create new service principals for the NFS server and for the client. The second machine will be a NFS server with the krb5p share. Add the nfs server kerberos keys to the system's keytab, and set up a NFS server that exports a directory with sec=krb5p. The third machine is a regular NFS server. Export a directory with normal sec=sys security. The fourth is a desktop machine. Add the client kerberos keys to the system's keytab. Mount both NFS shares, and generate some files full of random data. I found 20MB from /dev/random works great. Open each NFS share up in tabs in Nautilus. Copy the random data files to the sec=sys NFS share. When they are done, one at a time cut and then paste the file into the sec=krb5p NFS share. The bug will trigger either on the first, or subsequent tries, but less than 10 tries are needed usually. There is a test kernel available in the following PPA: https://launchpad.net/~mruffell/+archive/ubuntu/sf285439-test If you install the test kernel, files will cut and paste correctly, and NFS will work as expected. [Regression Potential] If a regression were to occur, it would impact users of the NFS subsystem, since the changes modify how padding is applied to all NFS packets, and a regression would affect all versions of NFS. If a regression were to occur, users would need to downgrade their kernel while awaiting a fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887607/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.
*** This bug is a duplicate of bug 1835660 *** https://bugs.launchpad.net/bugs/1835660 ** This bug has been marked a duplicate of bug 1835660 initramfs unpacking failed -- 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/1870260 Title: initramfs unpacking failed: Decoding failed", message appears on boot up. Status in linux package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: OS : Ubuntu 20.04(20200401) Problem: "initramfs unpacking failed: Decoding failed", message appears on boot up solution: If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to COMPRESS=gzip then the error is fixing . Expected solution: This but in there from a long time I have seen this from Ubuntu 18.04,19.04,19.10 now in 20.04 So please fix it or change it from lz4 to gzip. an early reply is highly appreciated Thank you . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tamal 1451 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx Package: ubuntu-meta ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY34PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
One more data point. Using the ethtool command described in comment 16 (rx-usecs 200, tx-usecs 200) I see about a 10% improvement in bandwidth but still a large number of dropped incoming packets resulting in small TCP congestion windows (and thus a small fraction of the overall TCP goodput achieved by Windows on the same hardware). -- 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/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Kernel-packages] [Bug 1848429] Re: generic/527 from ubuntu_xfstests_btrfs failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848429 Title: generic/527 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/527- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad) --- tests/generic/527.out 2019-10-16 10:51:13.160701040 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad 2019-10-16 12:22:10.315449210 + @@ -1,4 +1,9 @@ QA output created by 527 -File fname1 data after power failure: bar -File fname2 data after power failure: foo -File fname3 data after power failure: foo +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system call failed: File exists. +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such file or directory +File fname1 data after power failure: ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out 2019-10-16 10:51:13.160701040 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad 2019-10-16 12:22:10.315449210 + @@ -1,4 +1,9 @@ QA output created by 527 -File fname1 data after power failure: bar -File fname2 data after power failure: foo -File fname3 data after power failure: foo +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system call failed: File exists. +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such file or directory +File fname1 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: No such file or directory +File fname2 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: No such file or directory +File fname3 data after power failure: +umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted. Syslog: Oct 16 12:22:09 kili ubuntu: run xfstest generic/527 Oct 16 12:22:09 kili kernel: [ 6068.948341] run fstests generic/527 at 2019-10-16 12:22:09 Oct 16 12:22:09 kili kernel: [ 6069.125238] BTRFS info (device sdb1): disk space caching is enabled Oct 16 12:22:09 kili kernel: [ 6069.125240] BTRFS info (device sdb1): has skinny extents Oct 16 12:22:09 kili kernel: [ 6069.132427] BTRFS info (device sdb1): enabling ssd optimizations Oct 16 12:22:09 kili kernel: [ 6069.246264] BTRFS: device fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 transid 5 /dev/sdb2 Oct 16 12:22:09 kili multipathd[1484]: dm-0: remove map (uevent) Oct 16 12:22:09 kili kernel: [ 6069.353749] BTRFS info (device dm-0): disk space caching is enabled Oct 16 12:22:09 kili kernel: [ 6069.353751] BTRFS info (device dm-0): has skinny extents Oct 16 12:22:09 kili kernel: [ 6069.353752] BTRFS info (device dm-0): flagging fs with big metadata feature Oct 16 12:22:09 kili kernel: [ 6069.358172] BTRFS info (device dm-0): enabling ssd optimizations Oct 16 12:22:09 kili kernel: [ 6069.359885] BTRFS info (device dm-0): checking UUID tree Oct 16 12:22:09 kili kernel: [ 6069.677202] BTRFS info (device dm-0): device fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved old:/dev/mapper/flakey-test new:/dev/dm-0 Oct 16 12:22:09 kili kernel: [ 6069.677914] BTRFS info (device dm-0): device fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved old:/dev/dm-0 new:/dev/mapper/flakey-test Oct 16 12:22:09 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 12:22:09 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 12:22:10 kili kernel: [ 6069.781083] BTRFS info (device dm-0): disk space caching is enabled Oct 16 12:22:10 kili kernel: [ 6069.781085] BTRFS info (device dm-0): has
[Kernel-packages] [Bug 1848439] Re: generic/562 from ubuntu_xfstests_btrfs failed on D
** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848439 Title: generic/562 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/562_check_dmesg: something found in dmesg (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.dmesg) - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad) --- tests/generic/562.out 2019-10-16 10:51:13.164700997 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad 2019-10-16 12:35:45.694630398 + @@ -1,5 +1,102404 @@ QA output created by 562 +XFS_IOC_CLONE: No space left on device File foo data after cloning and remount: -000 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 +000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +* +0004096 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/562.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad' to see the entire diff) Syslog with kernel traces: BTRFS info (device sdb2): checking UUID tree [ cut here ] BTRFS: Transaction aborted (error -28) WARNING: CPU: 52 PID: 53560 at fs/btrfs/ioctl.c:3350 clone_finish_inode_update+0x102/0x130 [btrfs] Modules linked in: dm_thin_pool dm_persistent_data dm_bio_prison dm_snapshot dm_bufio btrfs zstd_compress dm_flakey dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ioatdma irqbypass mei_me mei ipmi_si crct10dif_pclmul crc32_pclmul ghash_clmulni_intel joydev input_leds ipmi_devintf intel_cstate ipmi_msghandler intel_rapl_perf mac_hid acpi_pad acpi_power_meter sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid aesni_intel mgag200 aes_x86_64 crypto_simd i2c_algo_bit cryptd ttm glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ixgbe ahci lpc_ich xfrm_algo i2c_i801 libahci dca mdio wmi [last unloaded: scsi_debug] CPU: 52 PID: 53560 Comm: xfs_io Tainted: G I 5.0.0-31-generic #33-Ubuntu Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.1008.031920151331 03/19/2015 RIP: 0010:clone_finish_inode_update+0x102/0x130 [btrfs] Code: ff ff ff 49 8b 45 50 f0 48 0f ba a8 40 ce 00 00 02 72 19 83 fb fb 0f 84 86 3a 05 00 89 de 48 c7 c7 48 08 ad c0 e8 90 18 03 e4 <0f> 0b 4c 89 ef 89 d9 ba 16 0d 00 00 48 c7 c6 90 30 ac c0 e8 2e d9 RSP: 0018:bcf6e4017b60 EFLAGS: 00010286 RAX: RBX: ffe4 RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9ec45fa16440 RBP: bcf6e4017b90 R08: 0001 R09: 3827 R10: 0004 R11: R12: 9ec455442a60 R13: 9ec4533992d8 R14: 0a40 R15: 9ec1cb06c800 FS: 7f34c46f3800() GS:9ec45fa0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f34c46f1ef8 CR3: 000d124f6003 CR4: 001606e0 Call Trace: btrfs_clone+0xa18/0x1080 [btrfs] btrfs_clone_files+0xfe/0x160 [btrfs] btrfs_remap_file_range+0x321/0x410 [btrfs] do_clone_file_range+0x12b/0x260 vfs_clone_file_range+0x3a/0xb0 ioctl_file_clone+0x93/0xc0 do_vfs_ioctl+0x495/0x640 ? putname+0x47/0x50 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x5a/0x110 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f34c4a5e417 Code: 00 00 90 48 8b 05 79 0a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 49 0a 0d 00 f7 d8 64 89 01 48 RSP: 002b:7fff6c7b9e98 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0012 RCX: 7f34c4a5e417 RDX: 0012 RSI: 40049409 RDI: 0008 RBP: R08: 7fff6c7de0a0 R09: 7fff6c7de080
[Kernel-packages] [Bug 1848428] Re: generic/526 from ubuntu_xfstests_btrfs failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848428 Title: generic/526 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/526- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad) --- tests/generic/526.out 2019-10-16 10:51:13.160701040 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad 2019-10-16 12:22:09.159460024 + @@ -1,5 +1,11 @@ QA output created by 526 -File fname1 data after power failure: bar -File fname2 data after power failure: foo -File fname3 data after power failure: foo -File fname4 data after power failure: hello +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system call failed: File exists. +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such file or directory ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out 2019-10-16 10:51:13.160701040 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad 2019-10-16 12:22:09.159460024 + @@ -1,5 +1,11 @@ QA output created by 526 -File fname1 data after power failure: bar -File fname2 data after power failure: foo -File fname3 data after power failure: foo -File fname4 data after power failure: hello +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system call failed: File exists. +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such file or directory +File fname1 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: No such file or directory +File fname2 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: No such file or directory +File fname3 data after power failure: +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname4: No such file or directory +File fname4 data after power failure: +umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted. Syslog: Oct 16 12:22:07 kili ubuntu: run xfstest generic/526 Oct 16 12:22:07 kili kernel: [ 6067.439549] run fstests generic/526 at 2019-10-16 12:22:07 Oct 16 12:22:07 kili kernel: [ 6067.619112] BTRFS info (device sdb1): disk space caching is enabled Oct 16 12:22:07 kili kernel: [ 6067.619114] BTRFS info (device sdb1): has skinny extents Oct 16 12:22:07 kili kernel: [ 6067.623160] BTRFS info (device sdb1): enabling ssd optimizations Oct 16 12:22:07 kili kernel: [ 6067.740396] BTRFS: device fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 transid 5 /dev/sdb2 Oct 16 12:22:08 kili kernel: [ 6067.845454] BTRFS info (device dm-0): disk space caching is enabled Oct 16 12:22:08 kili kernel: [ 6067.845456] BTRFS info (device dm-0): has skinny extents Oct 16 12:22:08 kili kernel: [ 6067.845458] BTRFS info (device dm-0): flagging fs with big metadata feature Oct 16 12:22:08 kili kernel: [ 6067.851055] BTRFS info (device dm-0): enabling ssd optimizations Oct 16 12:22:08 kili kernel: [ 6067.851555] BTRFS info (device dm-0): checking UUID tree Oct 16 12:22:08 kili kernel: [ 6068.206539] BTRFS info (device dm-0): device fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 moved old:/dev/mapper/flakey-test new:/dev/dm-0 Oct 16 12:22:08 kili kernel: [ 6068.207207] BTRFS info (device dm-0): device fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 moved old:/dev/dm-0 new:/dev/mapper/flakey-test Oct 16 12:22:08 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 12:22:08 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 12:22:08 kili kernel: [ 6068.292235]
[Kernel-packages] [Bug 1878356] Re: generic/001 from ubuntu_xfstests_btrfs / ext4 / xfs failed on F
** Tags added: sru-20200629 ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) ** Changed in: ubuntu-kernel-tests Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878356 Title: generic/001 from ubuntu_xfstests_btrfs / ext4 / xfs failed on F Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Focal (5.4.0-31.35, 5.4.0-26.30): generic/001 - output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/001.out.bad) --- tests/generic/001.out 2020-05-09 00:34:22.099406165 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/001.out.bad 2020-05-09 01:24:51.034988549 + @@ -1,9 +1,14 @@ QA output created by 001 cleanup setup -iter 1 chain ... check -iter 2 chain ... check -iter 3 chain ... check -iter 4 chain ... check ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/001.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/001.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
Two additional data points: 1) When I boot the "broken" computer -- i.e. the one that gets rx misses under Linux -- into Windows, Windows can drive the Ethernet chip at full wire speed; I get 500mbps to a WAN host over TCP. I believe this suggests it is not a problem with the BIOS. 2) I actually have two of the broken systems (I bought two identical computers) -- they both show the same ethernet receive problem. I believe this suggests it's a software problem and not a hardware problem. -- 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/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname:
[Kernel-packages] [Bug 1848423] Re: generic/260 from ubuntu_xfstests_btrfs failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848423 Title: generic/260 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/260[failed, exit status 1]- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad) --- tests/generic/260.out 2019-10-16 10:51:13.136701298 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad 2019-10-16 11:46:46.002804112 + @@ -1,14 +1,15 @@ QA output created by 260 [+] Start beyond the end of fs (should fail) -fstrim: SCRATCH_MNT: FITRIM ioctl failed: Invalid argument + [+] Start beyond the end of fs with len set (should fail) -fstrim: SCRATCH_MNT: FITRIM ioctl failed: Invalid argument + ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/260.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad' to see the entire diff) Syslog: Oct 16 11:46:26 kili ubuntu: run xfstest generic/260 Oct 16 11:46:26 kili kernel: [ 3925.966035] run fstests generic/260 at 2019-10-16 11:46:26 Oct 16 11:46:26 kili kernel: [ 3926.146996] BTRFS info (device sdb1): disk space caching is enabled Oct 16 11:46:26 kili kernel: [ 3926.146998] BTRFS info (device sdb1): has skinny extents Oct 16 11:46:26 kili kernel: [ 3926.150850] BTRFS info (device sdb1): enabling ssd optimizations Oct 16 11:46:26 kili kernel: [ 3926.233032] BTRFS: device fsid 38d9a8f4-3115-4a21-adaa-a1a68be4d42c devid 1 transid 5 /dev/sdb2 Oct 16 11:46:26 kili kernel: [ 3926.252529] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:46:26 kili kernel: [ 3926.252530] BTRFS info (device sdb2): has skinny extents Oct 16 11:46:26 kili kernel: [ 3926.252531] BTRFS info (device sdb2): flagging fs with big metadata feature Oct 16 11:46:26 kili kernel: [ 3926.257694] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:46:26 kili kernel: [ 3926.259525] BTRFS info (device sdb2): checking UUID tree Oct 16 11:46:33 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:33 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:33 kili kernel: [ 3933.374556] BTRFS: device fsid cd6d9b8b-abdd-4c38-b9bb-c97b36cb3117 devid 1 transid 5 /dev/sdb2 Oct 16 11:46:33 kili kernel: [ 3933.394698] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:46:33 kili kernel: [ 3933.394700] BTRFS info (device sdb2): has skinny extents Oct 16 11:46:33 kili kernel: [ 3933.394701] BTRFS info (device sdb2): flagging fs with big metadata feature Oct 16 11:46:33 kili kernel: [ 3933.399463] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:46:33 kili kernel: [ 3933.401342] BTRFS info (device sdb2): checking UUID tree Oct 16 11:46:41 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:41 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:41 kili kernel: [ 3941.143873] BTRFS: device fsid f10eab55-8c80-402c-84d2-002a6a1339de devid 1 transid 5 /dev/sdb2 Oct 16 11:46:41 kili kernel: [ 3941.162874] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:46:41 kili kernel: [ 3941.162876] BTRFS info (device sdb2): has skinny extents Oct 16 11:46:41 kili kernel: [ 3941.162876] BTRFS info (device sdb2): flagging fs with big metadata feature Oct 16 11:46:41 kili kernel: [ 3941.170124] BTRFS info (device sdb2): enabling ssd optimizations Oct 16 11:46:41 kili kernel: [ 3941.172812] BTRFS info (device sdb2): checking UUID tree Oct 16 11:46:42 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:42 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded. Oct 16 11:46:43 kili kernel: [ 3942.718482] BTRFS: device fsid 030f6bb2-f009-4cf6-91f0-75ea33b909c6 devid 1 transid 5 /dev/sdb2 Oct 16 11:46:43 kili kernel: [ 3942.737021] BTRFS info (device sdb2): disk space caching is enabled Oct 16 11:46:43 kili kernel: [ 3942.737022] BTRFS info (device sdb2): has skinny extents Oct 16 11:46:43 kili kernel: [ 3942.737023] BTRFS info (device
[Kernel-packages] [Bug 1846293] Re: generic/554 from ubuntu_xfstests_btrfs / ext4 failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846293 Title: generic/554 from ubuntu_xfstests_btrfs / ext4 failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: Issue found on node amd64 node "gonzo" generic/554- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/554.out.bad)  --- tests/generic/554.out 2019-10-01 07:38:07.096386372 +  +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/554.out.bad 2019-10-01 14:01:59.541113516 +  @@ -1,3 +1,2 @@   QA output created by 554   swap files return ETXTBUSY  -copy_range: Text file busy  ...  (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/tests/generic/554.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/554.out.bad' to see the entire diff) $ cat /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/554.out.bad QA output created by 554 swap files return ETXTBUSY ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: User Name 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 AlsaDevices:  total 0  crw-rw 1 root audio 116, 1 Oct 1 11:07 seq  crw-rw 1 root audio 116, 33 Oct 1 11:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.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: CurrentDmesg: Date: Wed Oct 2 06:03:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R415 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro RelatedPackageVersions:  linux-restricted-modules-5.0.0-29-generic N/A  linux-backports-modules-5.0.0-29-generic N/A  linux-firmware1.178.4 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/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 08WNM9 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R415 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1846293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848424] Re: generic/471 from ubuntu_xfstests_btrfs failed on D
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848424 Title: generic/471 from ubuntu_xfstests_btrfs failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: Issue found on node amd64 node "kili" generic/471- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad) --- tests/generic/471.out 2019-10-16 10:51:13.156701083 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad 2019-10-16 12:16:10.594841128 + @@ -2,12 +2,10 @@ pwrite: Resource temporarily unavailable wrote 8388608/8388608 bytes at offset 0 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -RWF_NOWAIT time is within limits. +pwrite: Resource temporarily unavailable +(standard_in) 1: syntax error +RWF_NOWAIT took seconds ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad' to see the entire diff) $ diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad --- /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out 2019-10-16 10:51:13.156701083 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad 2019-10-16 12:16:10.594841128 + @@ -2,12 +2,10 @@ pwrite: Resource temporarily unavailable wrote 8388608/8388608 bytes at offset 0 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) -RWF_NOWAIT time is within limits. +pwrite: Resource temporarily unavailable +(standard_in) 1: syntax error +RWF_NOWAIT took seconds : aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa * -0020: bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb -* -0030: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa -* read 8388608/8388608 bytes at offset 0 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) Syslog: Oct 16 12:16:09 kili ubuntu: run xfstest generic/471 Oct 16 12:16:09 kili kernel: [ 5708.949736] run fstests generic/471 at 2019-10-16 12:16:09 Oct 16 12:16:10 kili systemd[1]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 12:16:10 kili systemd[1894]: home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded. Oct 16 12:16:10 kili kernel: [ 5710.290570] BTRFS info (device sdb1): disk space caching is enabled Oct 16 12:16:10 kili kernel: [ 5710.290573] BTRFS info (device sdb1): has skinny extents Oct 16 12:16:10 kili kernel: [ 5710.294454] BTRFS info (device sdb1): enabling ssd optimizations ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 16 10:41 seq crw-rw 1 root audio 116, 33 Oct 16 10:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.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: Thu Oct 17 04:55:08 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S2600WTT PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C610.86B.01.01.1008.031920151331 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name:
[Kernel-packages] [Bug 1878347] Re: btrfs/136 from ubuntu_xfstests_btrfs failed on Focal
** Tags added: sru-20200629 -- 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/1878347 Title: btrfs/136 from ubuntu_xfstests_btrfs failed on Focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Focal (5.4.0-31.35, 5.4.0-26.30):  btrfs/136 [failed, exit status 1]- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/136.out.bad)  --- tests/btrfs/136.out 2020-05-09 00:34:22.075405127 +  +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/136.out.bad 2020-05-09 01:14:37.317409196 +  @@ -1,2 +1,4 @@  QA output created by 136  -Silence is golden  +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error.  +Could not mount new btrfs fs  +(see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/136.full for details)  ...  (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/136.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/136.out.bad' to see the entire diff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
In my case the bug is in the receiving direction. I see no problems with transmitting. Here is the output of lspci -vv (for only the ethernet controller in question) on the broken system. Below, I have the output from the working system. Broken system: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx ProblemType: Bug DistroRelease: Ubuntu 20.04 Package:
[Kernel-packages] [Bug 1846308] Re: generic/228 from ubuntu_xfstests_btrfs / ext4 / xfs failed on B/D/F
** Tags added: sru-20200629 -- 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/1846308 Title: generic/228 from ubuntu_xfstests_btrfs / ext4 / xfs failed on B/D/F Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux source package in Focal: New Bug description: Issue found on node amd64 node "gonzo" generic/228- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad) --- tests/generic/228.out 2019-10-01 07:38:07.060386413 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad 2019-10-01 12:27:44.465549241 + @@ -1,6 +1,6 @@ QA output created by 228 File size limit is now set to 100 MB. Let us try to preallocate 101 MB. This should fail. -File size limit exceeded +fallocate: File too large Let us now try to preallocate 50 MB. This should succeed. Test over. ... (Run 'diff -u /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/tests/generic/228.out /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad' to see the entire diff) $ cat /home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad QA output created by 228 File size limit is now set to 100 MB. Let us try to preallocate 101 MB. This should fail. fallocate: File too large Let us now try to preallocate 50 MB. This should succeed. Test over. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: User Name 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 1 11:07 seq crw-rw 1 root audio 116, 33 Oct 1 11:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.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: CurrentDmesg: [68184.314209] cfg80211: Loading compiled-in X.509 certificates for regulatory database [68184.315939] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed Oct 2 07:45:38 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R415 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.4 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/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 08WNM9 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R415 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1846308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877536] Re: BlueZ 5.54 release
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1877536 Title: BlueZ 5.54 release Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.54 to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887703] Re: 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller
An additional update, according to the person who reported this to me, the last known working kernel is 5.3: $lsb-release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 18.04.3 LTS Release: 18.04 Codename:bionic ubuntu@Server:~$ uname -a Linux MyServer 5.3.0-62-generic #56~18.04.1-Ubuntu SMP Wed Jun 24 16:17:03 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux0 So at least we know now that this breaks somewhere between 5.3 and 5.4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887703 Title: 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller  [Created at pci.386]  Unique ID: rz7Q.2osif2+gzUA  Parent ID: dkRe.4r+z9AQbRI0  SysFS ID: /devices/pci:32/:32:00.0/:33:00.2  SysFS BusID: :33:00.2  Hardware Class: network  Device Name: "Intel Ethernet X710-TM4 #3"  Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+"  Vendor: pci 0x8086 "Intel Corporation"  Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+"  SubVendor: pci 0x15d9 "Super Micro Computer Inc"  SubDevice: pci 0x  Revision: 0x02  Driver: "i40e"  Driver Modules: "i40e"  Device File: eno3  Memory Range: 0xa700-0xa7ff (ro,non-prefetchable)  Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable)  Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled)  IRQ: 60 (no events)  HW Address: 3c:ec:ef:3f:b2:16  Permanent HW Address: 3c:ec:ef:3f:b2:16  Link detected: yes  Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00"  Driver Info #0:   Driver Status: i40e is active   Driver Activation Cmd: "modprobe i40e"  Config Status: cfg=new, avail=yes, need=no, active=unknown  Attached to: #794 (PCI bridge) 625: PCI 3300.2: 0200 Ethernet controller  [Created at pci.386]  Unique ID: rz7Q.2osif2+gzUA  Parent ID: dkRe.4r+z9AQbRI0  SysFS ID: /devices/pci:32/:32:00.0/:33:00.2  SysFS BusID: :33:00.2  Hardware Class: network  Device Name: "Intel Ethernet X710-TM4 #3"  Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+"  Vendor: pci 0x8086 "Intel Corporation"  Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+"  SubVendor: pci 0x15d9 "Super Micro Computer Inc"  SubDevice: pci 0x  Revision: 0x02  Driver: "i40e"  Driver Modules: "i40e"  Device File: eno3  Memory Range: 0xa700-0xa7ff (ro,non-prefetchable)  Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable)  Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled)  IRQ: 60 (no events)  HW Address: 3c:ec:ef:3f:b2:16  Permanent HW Address: 3c:ec:ef:3f:b2:16  Link detected: yes  Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00"  Driver Info #0:   Driver Status: i40e is active   Driver Activation Cmd: "modprobe i40e"  Config Status: cfg=new, avail=yes, need=no, active=unknown  Attached to: #794 (PCI bridge) However, Ubuntu does not see the copper ports... it will only address/configure the two SFP+ ports. This is currently blocking certification for one of our hardware partners. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887218] 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 1887218 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/1887218 Title: Ryzen 5 3500U - laptop won't boot when on battery power Status in linux package in Ubuntu: Incomplete Bug description: Ryzen 5 3500U (release in 2019) won't boot when laptop is on battery power. It affects different brands of laptops. Laptop boots normally with charger in and you can unplug the charger and then use battery. For some a work around is possible on kernel 5.4. For others kernel should be 5.5 or better yet 5.6. issue described in more detail in Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2446942 dmesg: https://paste.ubuntu.com/p/C2xNzpBKq5/ iommu=soft boot options provides the work arround on some laptops, while on others USB ports stop working. OS: Kubuntu 20.04 LTS CPU: Ryzen 5 3500U GPU: AMD Vega 8 RAM: 8 GB DDR4 2400 Mhz disk: 256 GB nvme I patched kernel (now tainted) to get driver for rtl8821ce (wi-fi). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887218] Re: Ryzen 5 3500U - laptop won't boot when on battery power
** 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/1887218 Title: Ryzen 5 3500U - laptop won't boot when on battery power Status in linux package in Ubuntu: New Bug description: Ryzen 5 3500U (release in 2019) won't boot when laptop is on battery power. It affects different brands of laptops. Laptop boots normally with charger in and you can unplug the charger and then use battery. For some a work around is possible on kernel 5.4. For others kernel should be 5.5 or better yet 5.6. issue described in more detail in Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2446942 dmesg: https://paste.ubuntu.com/p/C2xNzpBKq5/ iommu=soft boot options provides the work arround on some laptops, while on others USB ports stop working. OS: Kubuntu 20.04 LTS CPU: Ryzen 5 3500U GPU: AMD Vega 8 RAM: 8 GB DDR4 2400 Mhz disk: 256 GB nvme I patched kernel (now tainted) to get driver for rtl8821ce (wi-fi). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887218] [NEW] Ryzen 5 3500U - laptop won't boot when on battery power
You have been subscribed to a public bug: Ryzen 5 3500U (release in 2019) won't boot when laptop is on battery power. It affects different brands of laptops. Laptop boots normally with charger in and you can unplug the charger and then use battery. For some a work around is possible on kernel 5.4. For others kernel should be 5.5 or better yet 5.6. issue described in more detail in Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2446942 dmesg: https://paste.ubuntu.com/p/C2xNzpBKq5/ iommu=soft boot options provides the work arround on some laptops, while on others USB ports stop working. OS: Kubuntu 20.04 LTS CPU: Ryzen 5 3500U GPU: AMD Vega 8 RAM: 8 GB DDR4 2400 Mhz disk: 256 GB nvme I patched kernel (now tainted) to get driver for rtl8821ce (wi-fi). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment ryzen53500u -- Ryzen 5 3500U - laptop won't boot when on battery power https://bugs.launchpad.net/bugs/1887218 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 1887853] [NEW] Focal update: v5.4.52 upstream stable release
Public bug reported: SRU Justification Impact:    The upstream process for stable tree updates is quite similar    in scope to the Ubuntu SRU process, e.g., each patch has to    demonstrably fix a bug, and each patch is vetted by upstream    by originating either directly from a mainline/stable Linux tree or    a minimally backported form of that patch. The following upstream    stable patches should be included in the Ubuntu kernel:    v5.4.52 upstream stable release    from git://git.kernel.org/ Revert "cgroup: Add memory barriers to plug cgroup_rstat_updated() race window" KVM: s390: reduce number of IO pins to 1 spi: spi-fsl-dspi: Adding shutdown hook spi: spi-fsl-dspi: Fix lockup if device is removed during SPI transfer regmap: fix alignment issue perf/x86/rapl: Move RAPL support to common x86 code perf/x86/rapl: Fix RAPL config variable bug UBUNTU: [Packaging] module intel-rapl-perf rename ARM: dts: omap4-droid4: Fix spi configuration and increase rate drm/ttm: Fix dma_fence refcnt leak when adding move fence drm/tegra: hub: Do not enable orphaned window group gpu: host1x: Detach driver on unregister drm: mcde: Fix display initialization problem ASoC: SOF: Intel: add PCI ID for CometLake-S ALSA: hda: Intel: add missing PCI IDs for ICL-H, TGL-H and EKL spi: spidev: fix a race between spidev_release and spidev_remove spi: spidev: fix a potential use-after-free in spidev_release() net: ethernet: mvneta: Fix Serdes configuration for SoCs without comphy net: ethernet: mvneta: Add 2500BaseX support for SoCs without comphy ixgbe: protect ring accesses with READ- and WRITE_ONCE i40e: protect ring accesses with READ- and WRITE_ONCE ibmvnic: continue to init in CRQ reset returns H_CLOSED powerpc/kvm/book3s64: Fix kernel crash with nested kvm & DEBUG_VIRTUAL iommu/vt-d: Don't apply gfx quirks to untrusted devices drm: panel-orientation-quirks: Add quirk for Asus T101HA panel drm: panel-orientation-quirks: Use generic orientation-data for Acer S1003 s390/kasan: fix early pgm check handler execution cifs: update ctime and mtime during truncate ARM: imx6: add missing put_device() call in imx6q_suspend_init() scsi: mptscsih: Fix read sense data size usb: dwc3: pci: Fix reference count leak in dwc3_pci_resume_work block: release bip in a right way in error path nvme-rdma: assign completion vector correctly x86/entry: Increase entry_stack size to a full page sched/core: Check cpus_mask, not cpus_ptr in __set_cpus_allowed_ptr(), to fix mask corruption net: qrtr: Fix an out of bounds read qrtr_endpoint_post() gpio: pca953x: Override IRQ for one of the expanders on Galileo Gen 2 gpio: pca953x: Fix GPIO resource leak on Intel Galileo Gen 2 nl80211: don't return err unconditionally in nl80211_start_ap() drm/mediatek: Check plane visibility in atomic_update bpf, sockmap: RCU splat with redirect and strparser error or TLS bpf, sockmap: RCU dereferenced psock may be used outside RCU block netfilter: ipset: call ip_set_free() instead of kfree() net: mvneta: fix use of state->speed net: cxgb4: fix return error value in t4_prep_fw IB/sa: Resolv use-after-free in ib_nl_make_request() net: dsa: microchip: set the correct number of ports netfilter: conntrack: refetch conntrack after nf_conntrack_update() perf report TUI: Fix segmentation fault in perf_evsel__hists_browse() perf intel-pt: Fix recording PEBS-via-PT with registers perf intel-pt: Fix PEBS sample for XMM registers smsc95xx: check return value of smsc95xx_reset smsc95xx: avoid memory leak in smsc95xx_bind net: hns3: add a missing uninit debugfs when unload driver net: hns3: fix use-after-free when doing self test ALSA: compress: fix partial_drain completion state RDMA/siw: Fix reporting vendor_part_id arm64: kgdb: Fix single-step exception handling oops nbd: Fix memory leak in nbd_add_socket cxgb4: fix all-mask IP address comparison IB/mlx5: Fix 50G per lane indication qed: Populate nvm-file attributes while reading nvm config partition. net/mlx5: Fix eeprom support for SFP module net/mlx5e: Fix 50G per lane indication bnxt_en: fix NULL dereference in case SR-IOV configuration fails net: macb: fix wakeup test in runtime suspend/resume routines net: macb: mark device wake capable when "magic-packet" property present net: macb: fix call to pm_runtime in the suspend/resume functions mlxsw: spectrum_router: Remove inappropriate usage of WARN_ON() mlxsw: pci: Fix use-after-free in case of failed devlink reload IB/hfi1: Do not destroy hfi1_wq when the device is shut down IB/hfi1: Do not destroy link_wq when the device is shut down ALSA: opl3: fix infoleak in opl3 ALSA: hda - let hs_mic be picked ahead of hp_mic ALSA: usb-audio: add quirk for MacroSilicon MS2109 ALSA: usb-audio: Add implicit feedback quirk for RTX6001 ALSA: hda/realtek - Fix Lenovo Thinkpad X1 Carbon 7th quirk subdevice id ALSA: hda/realtek - Enable audio jacks of Acer vCopperbox with ALC269VC ALSA: hda/realtek: Enable headset mic of Acer C20-820 with ALC269VC ALSA:
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1- This means ASPM sub-state 1.2 is enabled. This should not be the case because the driver disables ASPM at probe time. Also there's no message in dmesg that ASPM can't be controlled by OS. So this might be a BIOS bug. This could also explain why there are not significantly more such reports, as RTL8168h is a very common chip version. Regarding the iperf log it's not clear whether it's rx or tx direction. If client is the system we talk about, then it's tx direction. Please run iperf also with the "-R" option. Please also check with irq cialescing enabled: ethtool -C rx-usecs 200 tx-usecs 200 -- 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/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
[Kernel-packages] [Bug 1887703] Re: 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller
Further update, According to the engineer at SMC, they did try "18.04.3" (not sure if that means 4.15, or 5.3, hopefully not 5.2) and all four ports did work for them, so this appears to be a regression in the i40e driver. I've asked him to provide more info about what kernels they have tried specifically to help narrow down where it 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/1887703 Title: 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller  [Created at pci.386]  Unique ID: rz7Q.2osif2+gzUA  Parent ID: dkRe.4r+z9AQbRI0  SysFS ID: /devices/pci:32/:32:00.0/:33:00.2  SysFS BusID: :33:00.2  Hardware Class: network  Device Name: "Intel Ethernet X710-TM4 #3"  Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+"  Vendor: pci 0x8086 "Intel Corporation"  Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+"  SubVendor: pci 0x15d9 "Super Micro Computer Inc"  SubDevice: pci 0x  Revision: 0x02  Driver: "i40e"  Driver Modules: "i40e"  Device File: eno3  Memory Range: 0xa700-0xa7ff (ro,non-prefetchable)  Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable)  Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled)  IRQ: 60 (no events)  HW Address: 3c:ec:ef:3f:b2:16  Permanent HW Address: 3c:ec:ef:3f:b2:16  Link detected: yes  Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00"  Driver Info #0:   Driver Status: i40e is active   Driver Activation Cmd: "modprobe i40e"  Config Status: cfg=new, avail=yes, need=no, active=unknown  Attached to: #794 (PCI bridge) 625: PCI 3300.2: 0200 Ethernet controller  [Created at pci.386]  Unique ID: rz7Q.2osif2+gzUA  Parent ID: dkRe.4r+z9AQbRI0  SysFS ID: /devices/pci:32/:32:00.0/:33:00.2  SysFS BusID: :33:00.2  Hardware Class: network  Device Name: "Intel Ethernet X710-TM4 #3"  Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+"  Vendor: pci 0x8086 "Intel Corporation"  Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+"  SubVendor: pci 0x15d9 "Super Micro Computer Inc"  SubDevice: pci 0x  Revision: 0x02  Driver: "i40e"  Driver Modules: "i40e"  Device File: eno3  Memory Range: 0xa700-0xa7ff (ro,non-prefetchable)  Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable)  Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled)  IRQ: 60 (no events)  HW Address: 3c:ec:ef:3f:b2:16  Permanent HW Address: 3c:ec:ef:3f:b2:16  Link detected: yes  Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00"  Driver Info #0:   Driver Status: i40e is active   Driver Activation Cmd: "modprobe i40e"  Config Status: cfg=new, avail=yes, need=no, active=unknown  Attached to: #794 (PCI bridge) However, Ubuntu does not see the copper ports... it will only address/configure the two SFP+ ports. This is currently blocking certification for one of our hardware partners. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1884910] Re: Very slow boot with kernel 5.4.0-37-generic
I installed the following: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/amd64/linux- headers-5.8.0-050800rc5-generic_5.8.0-050800rc5.202007140715_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/amd64/linux- image- unsigned-5.8.0-050800rc5-generic_5.8.0-050800rc5.202007140715_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/amd64/linux- modules-5.8.0-050800rc5-generic_5.8.0-050800rc5.202007140715_amd64.deb The problem with the sound card still persists and boot is still slow. I noticed that I requied root privileges to access the dmesg file, which is attached. On 16/07/2020 15:58, Kai-Heng Feng wrote: > Ok. Now please test latest mainline kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ > ** Attachment added: "dmesg58rc5" https://bugs.launchpad.net/bugs/1884910/+attachment/5393229/+files/dmesg58rc5 -- 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/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887564] Re: Laptop XPS13 can't sleep Ubuntu 16.04.6 LTS when USB3 device is/was attached.
@bybeu, USB Emulation: This allows USB devices (keyboard, mouse, USB drives) to operate in BIOS / DOS. USB Powershare: This allows USB ports to provide powers in sleep or power-off, depends on hardware designs. This consumes some battery power in sleep or power-off USB Wake Support: This allows / disallows USB devices to wake up systems from sleep. External USB Ports: external ports are ports you can connect devices to. "Internal" ports are ones connecting to built-in devices like webcam, sd card and so on. You can disable "USB emulation and USB powershare" if you are not using them. A problem like this can be the results of (1) system sleeps but is waken up immediately, or (2) device driver fails to put hardware into sleep. Comment #3 (and "USB wake up support) is to address (1), and #22 is to verify whether new drivers in kernel can address (2), since are are running on much older kernel 4.4 You can boot to Ubuntu 20.04 (kernel 5.4) live with USB and suspend, if you don't want to install kernel package, or try kernel 5.8 as in #22 if you feel comfortable with installing kernels. -- 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/1887564 Title: Laptop XPS13 can't sleep Ubuntu 16.04.6 LTS when USB3 device is/was attached. Status in linux package in Ubuntu: Incomplete Bug description: (Ubuntu 4.4.0-185.215-generic 4.4.224) If I plug a USB3 device on the USB3 port then I can't send the laptop to sleep. (this happens with audio interface UMC404HD and Gbit Ethernet Adapter Trendnet) Instead it cancels the sleep process: Jul 13 10:24:22 xps kernel: [318785.373269] video LNXVIDEO:00: Restoring backlight state Jul 13 10:24:24 xps kernel: [318785.375145] PM: Syncing filesystems ... done. Jul 13 10:24:24 xps kernel: [318785.424201] PM: Preparing system for sleep (freeze) Jul 13 10:24:24 xps kernel: [318785.424337] Freezing user space processes ... (elapsed 0.001 seconds) done. Jul 13 10:24:24 xps kernel: [318785.426132] Freezing remaining freezable tasks ... (elapsed 0.037 seconds) done. Jul 13 10:24:24 xps kernel: [318785.463699] PM: Suspending system (freeze) Jul 13 10:24:24 xps kernel: [318785.463701] Suspending console(s) (use no_console_suspend to debug) Jul 13 10:24:24 xps kernel: [318785.463921] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 13 10:24:24 xps kernel: [318785.463971] sd 0:0:0:0: [sda] Stopping disk Jul 13 10:24:24 xps kernel: [318786.150701] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -16 Jul 13 10:24:24 xps kernel: [318786.150716] PM: Device usb4 failed to suspend async: error -16 Jul 13 10:24:24 xps kernel: [318786.150831] PM: Some devices failed to suspend, or early wake event detected Jul 13 10:24:24 xps kernel: [318786.166836] sd 0:0:0:0: [sda] Starting disk Jul 13 10:24:24 xps kernel: [318786.254775] rtc_cmos 00:01: System wakeup disabled by ACPI Jul 13 10:24:24 xps kernel: [318786.490641] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 13 10:24:24 xps kernel: [318786.513275] ata1.00: configured for UDMA/133 Jul 13 10:24:24 xps kernel: [318786.942366] PM: resume of devices complete after 791.556 msecs Jul 13 10:24:24 xps kernel: [318786.942703] PM: Finishing wakeup. Jul 13 10:24:24 xps kernel: [318786.942706] Restarting tasks ... done. Jul 13 10:24:24 xps systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Jul 13 10:24:24 xps kernel: [318786.967694] video LNXVIDEO:00: Restoring backlight state --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fab1827 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7 InstallationDate: Installed on 2013-07-05 (2567 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.4.0-185-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom debian-tor dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
frank@frank-G5-U20:~ $ uname -a Linux frank-G5-U20 5.4.52-custom #1 SMP Thu Jul 16 19:16:51 CEST 2020 x86_64 x86_64 x86_64 GNU/Linux frank@frank-G5-U20:~ $ iperf3 -c 192.168.0.11 Connecting to host 192.168.0.11, port 5201 [ 5] local 192.168.0.21 port 49482 connected to 192.168.0.11 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 90.5 MBytes 759 Mbits/sec0411 KBytes [ 5] 1.00-2.00 sec 90.5 MBytes 759 Mbits/sec0411 KBytes [ 5] 2.00-3.00 sec 90.0 MBytes 755 Mbits/sec0411 KBytes [ 5] 3.00-4.00 sec 89.9 MBytes 754 Mbits/sec0411 KBytes [ 5] 4.00-5.00 sec 89.6 MBytes 752 Mbits/sec0411 KBytes [ 5] 5.00-6.00 sec 90.4 MBytes 758 Mbits/sec0411 KBytes [ 5] 6.00-7.00 sec 101 MBytes 848 Mbits/sec0433 KBytes [ 5] 7.00-8.00 sec 103 MBytes 860 Mbits/sec0672 KBytes [ 5] 8.00-9.00 sec 90.0 MBytes 755 Mbits/sec0672 KBytes [ 5] 9.00-10.00 sec 90.0 MBytes 755 Mbits/sec0672 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 925 MBytes 776 Mbits/sec0 sender [ 5] 0.00-10.00 sec 920 MBytes 771 Mbits/sec receiver iperf Done. at least no retransmitts...but not the best transmission speed (on 18.4 i had ~930Mbit/s) will try before the first change in drivers/net/ethernet/realtek next https://wiki.ubuntu.com/KernelTeam/GitKernelBuild i used stable git-tree instead of mainline git clone --single-branch --branch=linux-5.4.y https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git and had to disable secureboot because of wrong signature-message on first boot...but at least easier than i thought... -- 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/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2
[Kernel-packages] [Bug 1887838] [NEW] Eoan update: upstream stable patchset 2020-07-16
Public bug reported: SRU Justification Impact:    The upstream process for stable tree updates is quite similar    in scope to the Ubuntu SRU process, e.g., each patch has to    demonstrably fix a bug, and each patch is vetted by upstream    by originating either directly from a mainline/stable Linux tree or    a minimally backported form of that patch. The following upstream    stable patches should be included in the Ubuntu kernel:    upstream stable patchset 2020-07-16 Ported from the following upstream stable releases: v4.19.132, v.5.4.51    from git://git.kernel.org/ btrfs: fix a block group ref counter leak after failure to remove block group mm: fix swap cache node allocation mask EDAC/amd64: Read back the scrub rate PCI register on F15h usbnet: smsc95xx: Fix use-after-free after removal mm/slub.c: fix corrupted freechain in deactivate_slab() mm/slub: fix stack overruns with SLUB_STATS usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect s390/debug: avoid kernel warning on too large number of pages nvme-multipath: set bdi capabilities once nvme-multipath: fix deadlock between ana_work and scan_work kgdb: Avoid suspicious RCU usage warning crypto: af_alg - fix use-after-free in af_alg_accept() due to bh_lock_sock() drm/msm/dpu: fix error return code in dpu_encoder_init cxgb4: use unaligned conversion for fetching timestamp cxgb4: parse TC-U32 key values and masks natively cxgb4: use correct type for all-mask IP address comparison cxgb4: fix SGE queue dump destination buffer context hwmon: (max6697) Make sure the OVERT mask is set correctly hwmon: (acpi_power_meter) Fix potential memory leak in acpi_power_meter_add() drm: sun4i: hdmi: Remove extra HPD polling virtio-blk: free vblk-vqs in error path of virtblk_probe() SMB3: Honor 'posix' flag for multiuser mounts nvme: fix a crash in nvme_mpath_add_disk i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665 i2c: mlxcpld: check correct size of maximum RECV_LEN packet nfsd: apply umask on fs without ACL support Revert "ALSA: usb-audio: Improve frames size computation" SMB3: Honor 'seal' flag for multiuser mounts SMB3: Honor persistent/resilient handle flags for multiuser mounts SMB3: Honor lease disabling for multiuser mounts cifs: Fix the target file was deleted when rename failed. MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen irqchip/gic: Atomically update affinity dm zoned: assign max_io_len correctly UBUNTU: [Config] updateconfigs for EFI_CUSTOM_SSDT_OVERLAYS efi: Make it possible to disable efivar_ssdt entirely sched/debug: Make sd->flags sysctl read-only rxrpc: Fix race between incoming ACK parser and retransmitter tools lib traceevent: Add append() function helper for appending strings tools lib traceevent: Handle __attribute__((user)) in field names nvme-multipath: fix deadlock due to head->lock nvme-multipath: fix bogus request queue reference put selftests: tpm: Use /bin/sh instead of /bin/bash tpm: Fix TIS locality timeout problems rxrpc: Fix afs large storage transmission performance drop RDMA/counter: Query a counter before release cxgb4: fix endian conversions for L4 ports in filters thermal/drivers/mediatek: Fix bank number settings on mt8183 thermal/drivers/rcar_gen3: Fix undefined temperature if negative nfsd4: fix nfsdfs reference count loop nfsd: fix nfsdfs inode reference count leak samples/vfs: avoid warning in statx override spi: spi-fsl-dspi: Fix external abort on interrupt in resume or exit paths SMB3: Honor 'handletimeout' flag for multiuser mounts MIPS: lantiq: xway: sysctrl: fix the GPHY clock alias names drm/amd/display: Only revalidate bandwidth on medium and fast updates drm/amdgpu: use %u rather than %d for sclk/mclk drm/amdgpu/atomfirmware: fix vram_info fetching for renoir dma-buf: Move dma_buf_release() from fops to dentry_ops mm, compaction: fully assume capture is not NULL in compact_zone_order() mm, compaction: make capture control handling safe wrt interrupts x86/resctrl: Fix memory bandwidth counter width for AMD UBUNTU: upstream stable to v4.19.132, v5.4.51 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: +    The upstream process for stable tree updates is quite similar +    in scope to the Ubuntu SRU process, e.g., each patch has to +    demonstrably fix a bug,
[Kernel-packages] [Bug 1847643] Re: iwlwifi during heavy transfers on XPS15 7590 (19.10)
I have an HP notebook computer which uses the same AX1650 WiFi chip. After suspend (sleep) and resume, WiFi ceases to function. Rfkill indicates that the radio is hardware blocked. Are any of you experiencing the same? -- 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/1847643 Title: iwlwifi during heavy transfers on XPS15 7590 (19.10) Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Bug description: I'm running 19.10 (beta). The Dell's 7590 wifi card is identified in `lspci` as: 3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a) From my googling the Dell 7590 seems to have a Killer AX1650 (in collaboration with Intel?) And when uploading a massive image to say S3, for example through CLI or browser, I get the following messages in `dmesg` after a few dozens of MB, at which point the net is killed and I need to turn the wifi off and on again to get online: [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump: [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6 [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0 [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0 [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1 [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2 [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1 [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2 [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1 [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2 [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3 [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1 [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2 [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0 [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1 [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2 [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3 [234483.616572] iwlwifi :3b:00.0: 0x | isr4 [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel [234483.616577] iwlwifi :3b:00.0: 0x | timestamp [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump: [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7 [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1 [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2 [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1 [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2 [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1 [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2 [234483.616657] iwlwifi :3b:00.0: 0x | umac data3 [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg [234483.616688] iwlwifi :3b:00.0: Fseq Registers: [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION [234483.616735] iwlwifi :3b:00.0: 0xA503 |
[Kernel-packages] [Bug 1887703] Re: 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller
** Description changed: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 - arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the + arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller  [Created at pci.386]  Unique ID: rz7Q.2osif2+gzUA  Parent ID: dkRe.4r+z9AQbRI0  SysFS ID: /devices/pci:32/:32:00.0/:33:00.2  SysFS BusID: :33:00.2  Hardware Class: network  Device Name: "Intel Ethernet X710-TM4 #3"  Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+"  Vendor: pci 0x8086 "Intel Corporation"  Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+"  SubVendor: pci 0x15d9 "Super Micro Computer Inc" -  SubDevice: pci 0x +  SubDevice: pci 0x  Revision: 0x02  Driver: "i40e"  Driver Modules: "i40e"  Device File: eno3  Memory Range: 0xa700-0xa7ff (ro,non-prefetchable)  Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable)  Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled)  IRQ: 60 (no events)  HW Address: 3c:ec:ef:3f:b2:16  Permanent HW Address: 3c:ec:ef:3f:b2:16  Link detected: yes  Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00"  Driver Info #0:   Driver Status: i40e is active   Driver Activation Cmd: "modprobe i40e"  Config Status: cfg=new, avail=yes, need=no, active=unknown  Attached to: #794 (PCI bridge) 625: PCI 3300.2: 0200 Ethernet controller  [Created at pci.386]  Unique ID: rz7Q.2osif2+gzUA  Parent ID: dkRe.4r+z9AQbRI0  SysFS ID: /devices/pci:32/:32:00.0/:33:00.2  SysFS BusID: :33:00.2  Hardware Class: network  Device Name: "Intel Ethernet X710-TM4 #3"  Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+"  Vendor: pci 0x8086 "Intel Corporation"  Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+"  SubVendor: pci 0x15d9 "Super Micro Computer Inc"  SubDevice: pci 0x  Revision: 0x02  Driver: "i40e"  Driver Modules: "i40e"  Device File: eno3  Memory Range: 0xa700-0xa7ff (ro,non-prefetchable)  Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable)  Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled)  IRQ: 60 (no events)  HW Address: 3c:ec:ef:3f:b2:16  Permanent HW Address: 3c:ec:ef:3f:b2:16  Link detected: yes  Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00"  Driver Info #0:   Driver Status: i40e is active   Driver Activation Cmd: "modprobe i40e"  Config Status: cfg=new, avail=yes, need=no, active=unknown  Attached to: #794 (PCI bridge) However, Ubuntu does not see the copper ports... it will only address/configure the two SFP+ ports. This is currently blocking certification for one of our hardware partners. -- 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/1887703 Title: 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller  [Created at pci.386]  Unique ID: rz7Q.2osif2+gzUA  Parent ID: dkRe.4r+z9AQbRI0  SysFS ID: /devices/pci:32/:32:00.0/:33:00.2  SysFS BusID: :33:00.2  Hardware Class: network  Device Name: "Intel Ethernet X710-TM4 #3"  Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+"  Vendor: pci 0x8086 "Intel Corporation"  Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+"  SubVendor: pci 0x15d9 "Super Micro Computer Inc"  SubDevice: pci 0x  Revision: 0x02  Driver: "i40e"  Driver Modules: "i40e"  Device File: eno3  Memory Range: 0xa700-0xa7ff (ro,non-prefetchable)  Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable)  Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled)  IRQ: 60 (no events)  HW Address: 3c:ec:ef:3f:b2:16  Permanent HW Address: 3c:ec:ef:3f:b2:16  Link detected: yes  Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00"  Driver Info #0:   Driver Status: i40e is active   Driver Activation Cmd: "modprobe i40e"  Config Status: cfg=new, avail=yes, need=no, active=unknown  Attached to: #794 (PCI bridge) 625: PCI 3300.2: 0200
[Kernel-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
Remark: this problems only ocurrs in encrypted Kubuntu (LVM). Without encryption it was OK. -- 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/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. 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] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO 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.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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802474] Re: test_map in ubuntu_bpf failed on D PowerPC
** Changed in: ubuntu-kernel-tests Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802474 Title: test_map in ubuntu_bpf failed on D PowerPC Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: The test_map test will fail with the following error on powerpc boxes: $ sudo ./test_maps libbpf: object file doesn't contain bpf program Failed to load SK_SKB parse prog ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-11.12~18.04.1-generic 4.18.12 Uname: Linux 4.18.0-11-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.4 Architecture: ppc64el Date: Fri Nov 9 08:37:46 2018 ProcLoadAvg: 0.18 0.51 0.47 1/1615 14440 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-11-generic (buildd@bos02-ppc64el-012) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #12~18.04.1-Ubuntu SMP Thu Oct 25 12:58:39 UTC 2018 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.695 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865965] Re: kill11 from ubuntu_ltp_syscalls failed
Also passes when run directly as outlined in comment #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/1865965 Title: kill11 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: startup='Tue Mar 3 15:46:25 2020' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s kill11.c:97: PASS: signal SIGHUP kill11.c:97: PASS: signal SIGINT kill11.c:97: PASS: signal SIGQUIT dumped core kill11.c:97: PASS: signal SIGILL dumped core kill11.c:97: PASS: signal SIGTRAP dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGBUS dumped core kill11.c:97: PASS: signal SIGFPE dumped core kill11.c:97: PASS: signal SIGKILL kill11.c:97: PASS: signal SIGUSR1 kill11.c:97: PASS: signal SIGSEGV dumped core kill11.c:97: PASS: signal SIGUSR2 kill11.c:97: PASS: signal SIGPIPE kill11.c:97: PASS: signal SIGALRM kill11.c:97: PASS: signal SIGTERM kill11.c:97: PASS: signal SIGSTKFLT kill11.c:97: PASS: signal SIGXCPU dumped core Test timeouted, sending SIGKILL! tst_test.c:1269: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1270: BROK: Test killed! (timeout?) Summary: passed 18 failed 0 skipped 0 warnings 0 tag=kill11 stime=1583250385 dur=302 exit=exited stat=2 core=no cu=0 cs=0 Need to see if bump the timeout threshold can help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Tags added: sru-20200629 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865965] Re: kill11 from ubuntu_ltp_syscalls failed
9366. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGHUP 9367. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGINT 9368. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGQUIT dumped core 9369. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGILL dumped core 9370. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGTRAP dumped core 9371. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGIOT/SIGABRT dumped core 9372. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGIOT/SIGABRT dumped core 9373. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGBUS dumped core 9374. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGFPE dumped core 9375. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGKILL 9376. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGUSR1 9377. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGSEGV dumped core 9378. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGUSR2 9379. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGPIPE 9380. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGALRM 9381. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGTERM 9382. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGSTKFLT 9383. 07/13 20:30:37 DEBUG| utils:0153| [stdout] kill11.c:98: PASS: signal SIGXCPU dumped core 9384. 07/13 20:30:37 DEBUG| utils:0153| [stdout] Test timeouted, sending SIGKILL! 9385. 07/13 20:30:37 DEBUG| utils:0153| [stdout] tst_test.c:1286: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 9386. 07/13 20:30:37 DEBUG| utils:0153| [stdout] tst_test.c:1288: BROK: Test killed! (timeout?) ** Tags added: bionic sru-20200629 -- 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/1865965 Title: kill11 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: startup='Tue Mar 3 15:46:25 2020' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s kill11.c:97: PASS: signal SIGHUP kill11.c:97: PASS: signal SIGINT kill11.c:97: PASS: signal SIGQUIT dumped core kill11.c:97: PASS: signal SIGILL dumped core kill11.c:97: PASS: signal SIGTRAP dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGBUS dumped core kill11.c:97: PASS: signal SIGFPE dumped core kill11.c:97: PASS: signal SIGKILL kill11.c:97: PASS: signal SIGUSR1 kill11.c:97: PASS: signal SIGSEGV dumped core kill11.c:97: PASS: signal SIGUSR2 kill11.c:97: PASS: signal SIGPIPE kill11.c:97: PASS: signal SIGALRM kill11.c:97: PASS: signal SIGTERM kill11.c:97: PASS: signal SIGSTKFLT kill11.c:97: PASS: signal SIGXCPU dumped core Test timeouted, sending SIGKILL! tst_test.c:1269: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1270: BROK: Test killed! (timeout?) Summary: passed 18 failed 0 skipped 0 warnings 0 tag=kill11 stime=1583250385 dur=302 exit=exited stat=2 core=no cu=0 cs=0 Need to see if bump the timeout threshold can help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1003731] Re: package linux-image-3.2.0-24-generic 3.2.0-24.38 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./boot/vmlinuz-3.2.0-24-generic'
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1003731 Title: package linux-image-3.2.0-24-generic 3.2.0-24.38 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./boot/vmlinuz-3.2.0-24-generic' Status in linux package in Ubuntu: Invalid Bug description: This is the second failed Linux-image install I've had to deal with. I got the previous to install with dpkg. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic 3.2.0-24.38 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: SB [HDA ATI SB], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myron 1933 F pulseaudio /dev/snd/controlC0: myron 1933 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0x90444000 irq 42' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'SB'/'HDA ATI SB at 0x9044 irq 16' Mixer name : 'Conexant CX20588' Components : 'HDA:14f1506c,10250598,0010' Controls : 17 Simple ctrls : 11 Date: Wed May 23 20:29:58 2012 DuplicateSignature: Unpacking replacement linux-image-3.2.0-24-generic ... dpkg-deb (subprocess): data: internal bzip2 read error: 'DATA_ERROR' dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing /var/cache/apt/archives/linux-image-3.2.0-24-generic_3.2.0-24.39_amd64.deb (--unpack): short read on buffer copy for backend dpkg-deb during `./boot/vmlinuz-3.2.0-24-generic' ErrorMessage: short read on buffer copy for backend dpkg-deb during `./boot/vmlinuz-3.2.0-24-generic' InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0402:9665 ALi Corp. Gateway Webcam MachineType: Acer AO722 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=a1262381-dd1c-4c24-8873-9368460814c0 ro quiet splash pcie_aspm=force vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 1.99-21ubuntu3 SourcePackage: linux Title: package linux-image-3.2.0-24-generic 3.2.0-24.38 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./boot/vmlinuz-3.2.0-24-generic' UpgradeStatus: Upgraded to precise on 2012-04-07 (46 days ago) dmi.bios.date: 09/19/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnAcer:bvrV1.07:bd09/19/2011:svnAcer:pnAO722:pvrV1.07:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.07: dmi.product.name: AO722 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Hello! When I log in, the sound does not appear. Then I have to close the application and try again until the sound appears. -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index :
[Kernel-packages] [Bug 868796] Re: package linux-image-2.6.38-11-generic 2.6.38-11.48 failed to install/upgrade: subprocess dpkg-deb --control returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/868796 Title: package linux-image-2.6.38-11-generic 2.6.38-11.48 failed to install/upgrade: subprocess dpkg-deb --control returned error exit status 2 Status in linux package in Ubuntu: Invalid Bug description: MY LINUXI IS NOT WORK PROPERLY Automatic aPPLICATIONS OPEN oR cLOSE ProblemType: Package DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-11-generic 2.6.38-11.48 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AptOrdering: linux-image-2.6.38-11-generic: Install linux-image-2.6.38-11-generic: Configure Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: akaushik 1296 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfea78000 irq 44' Mixer name : 'VIA VT1708S' Components : 'HDA:11064397,104383a1,0010' Controls : 28 Simple ctrls : 17 Date: Wed Oct 5 16:11:02 2011 DpkgTerminalLog: dpkg-deb: error: `/var/cache/apt/archives/linux-image-2.6.38-11-generic_2.6.38-11.50_i386.deb' is not a debian format archive dpkg: error processing /var/cache/apt/archives/linux-image-2.6.38-11-generic_2.6.38-11.50_i386.deb (--unpack): subprocess dpkg-deb --control returned error exit status 2 ErrorMessage: subprocess dpkg-deb --control returned error exit status 2 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=C204B3FE04B3F38F loop=/hostname/disks/root.disk ro quiet splash RelatedPackageVersions: linux-restricted-modules-2.6.38-11-generic N/A linux-backports-modules-2.6.38-11-generic N/A linux-firmware 1.52 RfKill: SourcePackage: linux Title: package linux-image-2.6.38-11-generic 2.6.38-11.48 failed to install/upgrade: subprocess dpkg-deb --control returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-AM IN dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd05/07/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMIN:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/868796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
I installed kernel 5.7.9. The scramble screen did not change. -- 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/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. 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] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO 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.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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887213] Re: Touchpad stopped working after upgrade: 18.04 => 20.04
Invalid. I tested my laptop with 18.04 live image. The touchpad doesn't work there. I guess, it's broken physically. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1887213 Title: Touchpad stopped working after upgrade: 18.04 => 20.04 Status in linux package in Ubuntu: Invalid Bug description: > Laptop model directly from the sticker of the computer. Lenovo T450 ThinkPad > Manufacturer of the Touchpad. > When the symptom first appeared. Right after 18.04 => 20.04 upgrade. Touchpad never worked after upgrade. Nor movements, neither clicks. 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 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyga 2740 F pulseaudio /dev/snd/controlC0: cyga 2740 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 13:36:53 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d66c9dac-9065-401a-8f9a-3f208be7d2e6 InstallationDate: Installed on 2017-06-07 (1129 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20BV0005US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 acpi=force irqpoll 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: Upgraded to focal on 2020-06-27 (13 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV0005US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BV0005US:pvrThinkPadT450:rvnLENOVO:rn20BV0005US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV0005US dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887156] Re: USB ports not working on the Pi 4 rev 1.4 board
** Changed in: linux-raspi2 (Ubuntu Bionic) Milestone: None => ubuntu-18.04.5 ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1887156 Title: USB ports not working on the Pi 4 rev 1.4 board Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: Confirmed Status in linux-raspi2 source package in Eoan: Won't Fix Bug description: [Impact] USB on the Pi 4B rev 1.4 running the raspi 5.3 kernel is non- functional. [Test Case] See original description below. [Regression Potential] Low. The changes are isolated to the PCIe driver used for the Raspberry Pi. The commit is a clean cherry-pick from the raspi 5.4 kernel. [Original Description] On the Pi 4 board revision 1.4 (of which the 8Gb model is currently the main example), the VL805 USB controller doesn't appear to be recognized by the 5.3 kernel. To reproduce: * Flash a current bionic image (e.g. http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04.4-preinstalled-server-arm64+raspi4.img.xz) * Boot the card on an older Pi model (3, 4 rev 1.2, etc.) * sudo add-apt-repository ppa:waveform/firmware * sudo apt install linux-firmware-raspi2 (the rev 1.4 requires a newer firmware package to boot; this PPA contains a test package with a back-ported firmware) * Boot the card on a Pi 4 rev 1.4 * Observe USB2 and USB3 ports do not work * Boot the card on an older Pi 4 rev 1.2 * Observe USB2 and USB3 ports do work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1887156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884981] Re: The touchpad soesn't work at all
Please raise the issue to the following email address: Jarkko Nikula (maintainer:SYNOPSYS DESIGNWARE I2C DRIVER) Andy Shevchenko (reviewer:SYNOPSYS DESIGNWARE I2C DRIVER) Mika Westerberg (reviewer:SYNOPSYS DESIGNWARE I2C DRIVER) Philipp Zabel (maintainer:RESET CONTROLLER FRAMEWORK) linux-...@vger.kernel.org (open list:SYNOPSYS DESIGNWARE I2C DRIVER) linux-ker...@vger.kernel.org (open list) -- 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/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) 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 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884981] Re: The touchpad soesn't work at all
Possible dupe of lp: #1887190, with different error though. -- 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/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) 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 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875274] Re: usrmerge breaks perf symbol lookup
Hi Travis, do you have an easy reproducer for this? I'm not familiar with perf, so a step to step guide would help me a lot. -- 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/1875274 Title: usrmerge breaks perf symbol lookup Status in linux package in Ubuntu: Confirmed Bug description: In 19.10, perf cannot find the symbols for libc even after installing libc-dbg. The symbols for libc are in: /usr/lib/debug/lib/x86_64-linux-gnu/ but libc is in: /usr/lib/x86_64-linux-gnu/ so applications expect to find the corresponding symbols at: /usr/lib/debug/usr/lib/x86_64-linux-gnu/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tdowns 1637 F pulseaudio /dev/snd/pcmC1D0p: tdowns 1637 F...m pulseaudio /dev/snd/controlC0: tdowns 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-02-14 (73 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=0a6fd287-c693-42a9-baa6-d90a59e83b42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-45-generic N/A linux-backports-modules-5.3.0-45-generic N/A linux-firmware1.183.5 Tags: eoan Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Possible dupe of lp: #1884981, with different error though. -- 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 linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: 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 dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on
[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
Also, you can use "hdajackretask" to see if overriding some pins helps. -- 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/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
Ok, I guess we need override a pin for it. I am checking the device spec, and it says the jack is "Speaker/Headset Jack", but icon indicates it only support outputs. Does it support mic? -- 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/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883229] Re: Ubuntu server installation on S3260M4 server fails
For us to develop this feature we need hardware access to such system, which we do not have. Can you please provide us with such hardware? either remote access, or ship it to us? Need to be able to remotely power it up and down, and be able to control bootloader to boot new installers. ** Changed in: subiquity Importance: High => Wishlist ** Changed in: subiquity Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883229 Title: Ubuntu server installation on S3260M4 server fails Status in subiquity: Incomplete Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Details/Description: - Ubuntu 20.04 fails on S3260 M4 with Gonga Beach in UEFI mode. Os get installed. However, upon rebooting OS never came up. Grub loads only to get hanged in a black screen. No options work later. Unable to collect Installer logs. How to reproduce: -- 1.Update S3260M4 M4 to bios build ucs-s3260-huu-4.1.2S36 2.Deploy Ubuntu 20.04 on S3260 M4. 3.Observe the installation proceeding and after installation OS reboots and loads the kernel and gets hanged on the black screen 4. The same OS works in Legacy mode in C3000 RAID controller card of LSI. Expected behavior: - Ubuntu 20.04 should get deployed in GB/DD-Raid in UEFI mode Screenshots -- Screenshot attached. Please let us know how to collect logs on this scenario Note :With MASS deployment we are able to deploy OS successfully with USFI method. Attached the logs of MASS server in this bug. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Cisco Systems Inc UCSC-C3K-M4SRB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1db32ed4-cafc-4d2c-b57c-d0b6a3943066 ro ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/06/2020 dmi.bios.vendor: Cisco Systems, Inc. dmi.bios.version: C3X60M4.4.1.1.13.0306200116 dmi.board.name: UCSC-C3K-M4SRB dmi.board.vendor: Cisco Systems Inc dmi.board.version: 73-17622-03 dmi.chassis.type: 23 dmi.chassis.vendor: Cisco Systems Inc dmi.chassis.version: 68-5829-03 dmi.modalias: dmi:bvnCiscoSystems,Inc.:bvrC3X60M4.4.1.1.13.0306200116:bd03/06/2020:svnCiscoSystemsInc:pnUCSC-C3K-M4SRB:pvrA0:rvnCiscoSystemsInc:rnUCSC-C3K-M4SRB:rvr73-17622-03:cvnCiscoSystemsInc:ct23:cvr68-5829-03: dmi.product.name: UCSC-C3K-M4SRB dmi.product.version: A0 dmi.sys.vendor: Cisco Systems Inc --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release
[Kernel-packages] [Bug 1883229] Re: Ubuntu server installation on S3260M4 server fails
** Tags removed: rls-ff-incoming -- 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/1883229 Title: Ubuntu server installation on S3260M4 server fails Status in subiquity: Incomplete Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Details/Description: - Ubuntu 20.04 fails on S3260 M4 with Gonga Beach in UEFI mode. Os get installed. However, upon rebooting OS never came up. Grub loads only to get hanged in a black screen. No options work later. Unable to collect Installer logs. How to reproduce: -- 1.Update S3260M4 M4 to bios build ucs-s3260-huu-4.1.2S36 2.Deploy Ubuntu 20.04 on S3260 M4. 3.Observe the installation proceeding and after installation OS reboots and loads the kernel and gets hanged on the black screen 4. The same OS works in Legacy mode in C3000 RAID controller card of LSI. Expected behavior: - Ubuntu 20.04 should get deployed in GB/DD-Raid in UEFI mode Screenshots -- Screenshot attached. Please let us know how to collect logs on this scenario Note :With MASS deployment we are able to deploy OS successfully with USFI method. Attached the logs of MASS server in this bug. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Cisco Systems Inc UCSC-C3K-M4SRB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1db32ed4-cafc-4d2c-b57c-d0b6a3943066 ro ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/06/2020 dmi.bios.vendor: Cisco Systems, Inc. dmi.bios.version: C3X60M4.4.1.1.13.0306200116 dmi.board.name: UCSC-C3K-M4SRB dmi.board.vendor: Cisco Systems Inc dmi.board.version: 73-17622-03 dmi.chassis.type: 23 dmi.chassis.vendor: Cisco Systems Inc dmi.chassis.version: 68-5829-03 dmi.modalias: dmi:bvnCiscoSystems,Inc.:bvrC3X60M4.4.1.1.13.0306200116:bd03/06/2020:svnCiscoSystemsInc:pnUCSC-C3K-M4SRB:pvrA0:rvnCiscoSystemsInc:rnUCSC-C3K-M4SRB:rvr73-17622-03:cvnCiscoSystemsInc:ct23:cvr68-5829-03: dmi.product.name: UCSC-C3K-M4SRB dmi.product.version: A0 dmi.sys.vendor: Cisco Systems Inc --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002
Re: [Kernel-packages] [Bug 1850654] Re: update-initramfs complains of missing amdgpu firmware files
On Thu, Jul 16, 2020 at 02:48:00PM -, Andrew Stachura wrote: > Is this fixed. I believe this is what is crashing my 20.04 LTS installer > in during the final stages. Stuck with a non functioning distribution. > Can you help? I'm not sure if they've all been eliminated. However, these are only warnings and shouldn't cause anything to fail, so I'd be very surprised if they are causing the installer to crash. -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881813] Re: [qxl] Desktop freezes 20.04
Installed v5.8 so far so good, but it's hard to say till it freezes or not during some use. -- 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/1881813 Title: [qxl] Desktop freezes 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Not too much info yet, will add apport report, but see it very often on 20.04 (upgraded from 18.04) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-05-07 (759 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.36.1-5ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-05-07 (759 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.36.1-5ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuriw 1143 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-05-07 (764 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: ens8 no wireless extensions. lono wireless extensions. ens3 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b5969aa-16c5-43c7-9a83-1c75e5e19363 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (46 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1881813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] Re: Very slow boot with kernel 5.4.0-37-generic
Ok. Now please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ -- 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/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Please raise the issue to the following email address: Jarkko Nikula (maintainer:SYNOPSYS DESIGNWARE I2C DRIVER) Andy Shevchenko (reviewer:SYNOPSYS DESIGNWARE I2C DRIVER) Mika Westerberg (reviewer:SYNOPSYS DESIGNWARE I2C DRIVER) Philipp Zabel (maintainer:RESET CONTROLLER FRAMEWORK) linux-...@vger.kernel.org (open list:SYNOPSYS DESIGNWARE I2C DRIVER) linux-ker...@vger.kernel.org (open list) -- 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 linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: 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 dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5
[Kernel-packages] [Bug 1879401] Re: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound rarely works
Hi @kaihengfeng, I'm happy to do that but it'll have to wait a few days for the 5.8-rc6 rebase. The bpfilter regression in rc5 is blocking for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879401 Title: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound rarely works Status in linux package in Ubuntu: Confirmed Bug description: I have an Ice Lake laptop (Dell 7390 2-in-one) which I am connecting to a TV over HDMI via a Novoo USB-C multiport adapter. This is not a Thunderbolt device, it is just USB-C. It seemed like things used to work fine before I upgraded this system from Ubuntu 19.10 to 20.04, although I couldn't say for certain at this point. But I'm having a ton of difficulty getting audio output over HDMI. Getting it to work requires a lot of retries to reinitialize the device (either by suspending/resuming the laptop, or plugging/unplugging the HDMI cable and/or the multiport adapter). It does work sometimes, but my success rate is very low at this point. Even when it does work, it's brittle: any change to the output port (to speaker and back to HDMI, or from stereo to surround and back) will often break the audio. This fact seems to suggest that the problem doesn't have anything to do with the low-level initialization of the HDMI port; I'd be looking at some mid-layer code. To be clear, there doesn't seem to be any particular symptom, or anything of interest in the logs, other than an absence of sound output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbryant1510 F pulseaudio /dev/snd/pcmC0D9p: nbryant1510 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 17:32:11 2020 InstallationDate: Installed on 2020-01-31 (108 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: May 18 16:36:42 atlantis dbus-daemon[633]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.41' (uid=124 pid=1116 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") May 18 16:36:53 atlantis systemd[1109]: pulseaudio.service: Succeeded. May 18 16:37:03 atlantis systemd[1109]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] fails after a while UpgradeStatus: Upgraded to focal on 2020-04-21 (27 days ago) dmi.bios.date: 03/02/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.1 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbryant1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-31 (108 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 8087:0026 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 2-in-1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=caffa21a-82f2-4555-a416-67926241525a ro cma=64M pcie_aspm.policy=powersupersave drm.vblankoffdelay=1 video=1600x1200 mem_sleep_default=deep ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 RelatedPackageVersions: linux-restricted-modules-5.6.0-1010-oem N/A
[Kernel-packages] [Bug 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
** Tags added: 5.4 ** Tags added: sru-20200629 -- 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/1865967 Title: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == The fill_fs test for XFS in fallocate06 from ubuntu_ltp_syscalls will fail on X/B/D/E: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 8192) fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Fix == * e093c4be (xfs: Fix tail rounding in xfs_alloc_file_space()) This patch can be cherry-picked in D/E and needs some minor context adjustmest on X/B. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1865967-xfs-fallocate06/ All patched kernels are working as expected, this issue will no longer exist on XFS: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop5 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Regression Potential == Low, this ensures all the blocks are properly allocated and it's only affecting the allocation on XFS.
[Kernel-packages] [Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 kernels
This appears to just be a nuisance now, rather than a reliable test as it is consistently failing in clouds. Will take some time to break this down and figure out if we can fix the test. ** Changed in: ubuntu-kernel-tests Assignee: Marcelo Cerri (mhcerri) => Sean Feole (sfeole) ** Changed in: linux (Ubuntu Eoan) Assignee: Marcelo Cerri (mhcerri) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Marcelo Cerri (mhcerri) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 kernels Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gcp source package in Eoan: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Status in linux-gcp source package in Focal: New Bug description: Test failed with: FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Steps: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control Test output: == sysdig smoke test to trace dd, cat, read and writes == Limiting raw capture file to 16384 blocks Try 1 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 18 Mbytes Try 2 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 22 Mbytes Try 3 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 4 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 5 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 6 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 7 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 8 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 9 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 10 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Found: 279845 sysdig events 29882 context switches 0 reads from /dev/zero by dd 0 writes to /dev/null by dd PASSED (trace at least 25 context switches) FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Summary: 1 passed, 2 failed ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 18 08:10 seq crw-rw 1 root audio 116, 33 Sep 18 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu7 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: CurrentDmesg: Date: Wed Sep 18 08:18:54 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 RfKill: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1850654] Re: update-initramfs complains of missing amdgpu firmware files
Is this fixed. I believe this is what is crashing my 20.04 LTS installer in during the final stages. Stuck with a non functioning distribution. Can you help? Andy -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887774] Re: [UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed ERP
Kernel SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2020-July/thread.html#112154 Updating status to 'In Progress'. ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-z-systems Status: Triaged => In Progress ** Description changed: + SRU Justification: + == + + [Impact] + + * Linux kernel panics due to kernel page fault in IRQ context when + running zfcp_erp_timeout_handler() calling zfcp_erp_notify(). + + [Fix] + + * 936e6b85da0476dd2edac7c51c68072da9fb4ba2 936e6b85da04 "scsi: zfcp: Fix + panic on ERP timeout for previously dismissed ERP action" + + [Test Case] + + * Requires an IBM z13/z13s or LinuxONE Rockhopper/Emperor system (or + newer) connected to zfcp capcble storage sub-system. + + * Initiate an (ERP) timeout (maybe by injection or by causing a slow + recovery otherwise). + + * Monitor the system log for any kernel panics. + + [Regression Potential] + + * The regression can be considered as medium since the modification is + platform specific / limited to s390x and again limited to the zfcp + layer. + + * Within zfcp it's further limited to the error recovery procedure (ERP) + of fcp and only touches zfcp_erp.c, means the code path is mainly active + under error conditions. + + [Other] + + * The above fix is upstream accepted with v5.8-rc3, hence will make it's + way to groovy with kernel 5.8. + + * Therefore this SRU request was submitted for bionic and focal only and + not for groovy. + + __ + Description: zfcp: Fix panic on ERP timeout for previously dismissed ERP Symptom: Linux kernel panic due to kernel page fault in IRQ context -when running zfcp_erp_timeout_handler() calling -zfcp_erp_notify(). + Â Â Â when running zfcp_erp_timeout_handler() calling + Â Â Â zfcp_erp_notify(). Problem: Suppose that, for unrelated reasons, FSF requests on behalf -of recovery are very slow and can run into the ERP timeout. -In the case at hand, we did adapter recovery to a large -degree. However due to the slowness a LUN open is pending so -the corresponding fc_rport remains blocked. After -fast_io_fail_tmo we trigger close physical port recovery for -the port under which the LUN should have been opened. The -new higher order port recovery dismisses the pending LUN -open ERP action and dismisses the pending LUN open FSF -request. Such dismissal decouples the ERP action from the -pending corresponding FSF request by setting -zfcp_fsf_req->erp_action to NULL (among other things) -[zfcp_erp_strategy_check_fsfreq()]. -If now the ERP timeout for the pending open LUN request runs -out, we must not use zfcp_fsf_req->erp_action in the ERP -timeout handler. This is a problem since v4.15 commit -75492a51568b ("s390/scsi: Convert timers to use -timer_setup()"). Before that we intentionally only passed -zfcp_erp_action as context argument to -zfcp_erp_timeout_handler(). -Note: The lifetime of the corresponding zfcp_fsf_req object -continues until a (late) response or an (unrelated) adapter -recovery. + Â Â Â of recovery are very slow and can run into the ERP timeout. + Â Â Â In the case at hand, we did adapter recovery to a large + Â Â Â degree. However due to the slowness a LUN open is pending so + Â Â Â the corresponding fc_rport remains blocked. After + Â Â Â fast_io_fail_tmo we trigger close physical port recovery for + Â Â Â the port under which the LUN should have been opened. The + Â Â Â new higher order port recovery dismisses the pending LUN + Â Â Â open ERP action and dismisses the pending LUN open FSF + Â Â Â request. Such dismissal decouples the ERP action from the + Â Â Â pending corresponding FSF request by setting + Â Â Â zfcp_fsf_req->erp_action to NULL (among other things) + Â Â Â [zfcp_erp_strategy_check_fsfreq()]. + Â Â Â If now the ERP timeout for the pending open LUN request runs + Â Â Â out, we must not use zfcp_fsf_req->erp_action in the ERP + Â Â Â timeout handler. This is a problem since v4.15 commit + Â Â Â 75492a51568b ("s390/scsi: Convert timers to use + Â Â Â timer_setup()"). Before that we intentionally only passed + Â Â Â zfcp_erp_action as context argument to + Â Â Â zfcp_erp_timeout_handler(). + Â Â Â Note: The lifetime of the corresponding zfcp_fsf_req object + Â Â Â continues until a (late) response or an (unrelated) adapter + Â Â Â recovery. Solution: Just
[Kernel-packages] [Bug 1885033] Re: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- 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/1885033 Title: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: The touchpad switch, Fn-F6, does not work for me. It does work on Windows 10 (dual boot) The touchpad works well, but I can only set the option in System Conguration. See launchpad answer : https://answers.launchpad.net/ubuntu/+question/691511 Kubuntu 20.04 Lenovo IdeaPad L340-15IRH - Type 81LK --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yann 1350 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-20 (125 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30) Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81LK NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=0ac30ea3-dc16-4323-a1a3-acea99fa90b5 ro quiet splash resume=/dev/nvme0n1p6 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-14 (41 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN29WW 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 L340-15IRH Gaming dmi.modalias: dmi:bvnLENOVO:bvrBGCN29WW:bd02/10/2020:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887703] Re: 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller
All the necessary logs should be in the attached sosreport, if not, I can ask them to also run apport-collect, but that seemed unnecessary. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Confirmed ** Summary changed: - 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller + 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller -- 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/1887703 Title: 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller  [Created at pci.386]  Unique ID: rz7Q.2osif2+gzUA  Parent ID: dkRe.4r+z9AQbRI0  SysFS ID: /devices/pci:32/:32:00.0/:33:00.2  SysFS BusID: :33:00.2  Hardware Class: network  Device Name: "Intel Ethernet X710-TM4 #3"  Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+"  Vendor: pci 0x8086 "Intel Corporation"  Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+"  SubVendor: pci 0x15d9 "Super Micro Computer Inc"  SubDevice: pci 0x  Revision: 0x02  Driver: "i40e"  Driver Modules: "i40e"  Device File: eno3  Memory Range: 0xa700-0xa7ff (ro,non-prefetchable)  Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable)  Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled)  IRQ: 60 (no events)  HW Address: 3c:ec:ef:3f:b2:16  Permanent HW Address: 3c:ec:ef:3f:b2:16  Link detected: yes  Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00"  Driver Info #0:   Driver Status: i40e is active   Driver Activation Cmd: "modprobe i40e"  Config Status: cfg=new, avail=yes, need=no, active=unknown  Attached to: #794 (PCI bridge) 625: PCI 3300.2: 0200 Ethernet controller  [Created at pci.386]  Unique ID: rz7Q.2osif2+gzUA  Parent ID: dkRe.4r+z9AQbRI0  SysFS ID: /devices/pci:32/:32:00.0/:33:00.2  SysFS BusID: :33:00.2  Hardware Class: network  Device Name: "Intel Ethernet X710-TM4 #3"  Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+"  Vendor: pci 0x8086 "Intel Corporation"  Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+"  SubVendor: pci 0x15d9 "Super Micro Computer Inc"  SubDevice: pci 0x  Revision: 0x02  Driver: "i40e"  Driver Modules: "i40e"  Device File: eno3  Memory Range: 0xa700-0xa7ff (ro,non-prefetchable)  Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable)  Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled)  IRQ: 60 (no events)  HW Address: 3c:ec:ef:3f:b2:16  Permanent HW Address: 3c:ec:ef:3f:b2:16  Link detected: yes  Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00"  Driver Info #0:   Driver Status: i40e is active   Driver Activation Cmd: "modprobe i40e"  Config Status: cfg=new, avail=yes, need=no, active=unknown  Attached to: #794 (PCI bridge) However, Ubuntu does not see the copper ports... it will only address/configure the two SFP+ ports. This is currently blocking certification for one of our hardware partners. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887796] Re: Bluetooth headset cant set output as A2DP sink while using the mic as input device
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1887796 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1887796 Title: Bluetooth headset cant set output as A2DP sink while using the mic as input device Status in bluez package in Ubuntu: Incomplete Bug description: I have the popular Sony WH-100XM3 headset. I can connect to the headset fine using bluetooth. I set the Output device in Sound Option, there are two configurations A2DP Sink (sounds great) and HSP/HFP (sounds terrible). If I set the input device to the headset, it silently switches the output configuration to HSP/HFP and so the audio sounds terrible. If I then switch the output configuation back to A2DP sink, the audio output sounds good again, but then the input device switches to something else. So the problem is that I cant use the headset as audio input while having the good-sounding output configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887774] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-07-16 09:33 EDT--- Due to the fact, that this problem comes up with kernel 4.15, also integration for 18.04 is also required. -- 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/1887774 Title: [UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed ERP Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: Description: zfcp: Fix panic on ERP timeout for previously dismissed ERP Symptom: Linux kernel panic due to kernel page fault in IRQ context when running zfcp_erp_timeout_handler() calling zfcp_erp_notify(). Problem: Suppose that, for unrelated reasons, FSF requests on behalf of recovery are very slow and can run into the ERP timeout. In the case at hand, we did adapter recovery to a large degree. However due to the slowness a LUN open is pending so the corresponding fc_rport remains blocked. After fast_io_fail_tmo we trigger close physical port recovery for the port under which the LUN should have been opened. The new higher order port recovery dismisses the pending LUN open ERP action and dismisses the pending LUN open FSF request. Such dismissal decouples the ERP action from the pending corresponding FSF request by setting zfcp_fsf_req->erp_action to NULL (among other things) [zfcp_erp_strategy_check_fsfreq()]. If now the ERP timeout for the pending open LUN request runs out, we must not use zfcp_fsf_req->erp_action in the ERP timeout handler. This is a problem since v4.15 commit 75492a51568b ("s390/scsi: Convert timers to use timer_setup()"). Before that we intentionally only passed zfcp_erp_action as context argument to zfcp_erp_timeout_handler(). Note: The lifetime of the corresponding zfcp_fsf_req object continues until a (late) response or an (unrelated) adapter recovery. Solution: Just like the regular response path ignores dismissed requests [zfcp_fsf_req_complete() => zfcp_fsf_protstatus_eval() => return early] the ERP timeout handler now needs to ignore dismissed requests. So simply return early in the ERP timeout handler if the FSF request is marked as dismissed in its status flags. To protect against the race where zfcp_erp_strategy_check_fsfreq() dismisses and sets zfcp_fsf_req->erp_action to NULL after our previous status flag check, return early if zfcp_fsf_req->erp_action is NULL. After all, the former ERP action does not need to be woken up as that was already done as part of the dismissal above [zfcp_erp_action_dismiss()]. Upstream-ID: 936e6b85da0476dd2edac7c51c68072da9fb4ba2 -> kernel 5.8 Will be integrated by kernel 5.8 by groovy. Please check that this also be integrated into 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
sorry 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 1427 F pulseaudio
[Kernel-packages] [Bug 1887774] Re: [UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed ERP
A patched kernel (that I created during the SRU preparation and test compile) is available for further testing here: https://people.canonical.com/~fheimes/lp1887774/ -- 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/1887774 Title: [UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed ERP Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: Description: zfcp: Fix panic on ERP timeout for previously dismissed ERP Symptom: Linux kernel panic due to kernel page fault in IRQ context when running zfcp_erp_timeout_handler() calling zfcp_erp_notify(). Problem: Suppose that, for unrelated reasons, FSF requests on behalf of recovery are very slow and can run into the ERP timeout. In the case at hand, we did adapter recovery to a large degree. However due to the slowness a LUN open is pending so the corresponding fc_rport remains blocked. After fast_io_fail_tmo we trigger close physical port recovery for the port under which the LUN should have been opened. The new higher order port recovery dismisses the pending LUN open ERP action and dismisses the pending LUN open FSF request. Such dismissal decouples the ERP action from the pending corresponding FSF request by setting zfcp_fsf_req->erp_action to NULL (among other things) [zfcp_erp_strategy_check_fsfreq()]. If now the ERP timeout for the pending open LUN request runs out, we must not use zfcp_fsf_req->erp_action in the ERP timeout handler. This is a problem since v4.15 commit 75492a51568b ("s390/scsi: Convert timers to use timer_setup()"). Before that we intentionally only passed zfcp_erp_action as context argument to zfcp_erp_timeout_handler(). Note: The lifetime of the corresponding zfcp_fsf_req object continues until a (late) response or an (unrelated) adapter recovery. Solution: Just like the regular response path ignores dismissed requests [zfcp_fsf_req_complete() => zfcp_fsf_protstatus_eval() => return early] the ERP timeout handler now needs to ignore dismissed requests. So simply return early in the ERP timeout handler if the FSF request is marked as dismissed in its status flags. To protect against the race where zfcp_erp_strategy_check_fsfreq() dismisses and sets zfcp_fsf_req->erp_action to NULL after our previous status flag check, return early if zfcp_fsf_req->erp_action is NULL. After all, the former ERP action does not need to be woken up as that was already done as part of the dismissal above [zfcp_erp_action_dismiss()]. Upstream-ID: 936e6b85da0476dd2edac7c51c68072da9fb4ba2 -> kernel 5.8 Will be integrated by kernel 5.8 by groovy. Please check that this also be integrated into 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884159] Re: Update lockdown patches
Tested against -proposed kernels for xenial, bionic, eoan, and focal. Tested against a suite of tests I wrote to exercise as many of the interfaces as possible which are restricted by kernel lockdown, and also tested against the applicable "American Unsigned Language" exploits [1]. Everything looks good. [1] https://git.zx2c4.com/american-unsigned-language/ ** Tags removed: verification-needed-bionic verification-needed-eoan verification-needed-focal verification-needed-xenial ** Tags added: verification-done-bionic verification-done-eoan verification-done-focal verification-done-xenial -- 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/1884159 Title: Update lockdown patches Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: Impact: The lockdown patches have evolved over time, and part of this was restricting more areas of the kernel. Not all of these additions were backported, and some can lead to lockdown bypasses, see [1] and [2]. Fix: Backport newer lockdown restrictions to older releases. Test Case: Test cases for most of the backports can be found at [3], and [4] is another test case. Some which need e.g. specific hardware to test have not been tested. Regression Potential: Most of these are small, simple fixes with low potential for regression. Users may also lose access to some functionality previously accissible under secure boot. Some changes are more substantial, especially the hw_param and debugfs changes for xenial, but they are based on well-tested upstream code. The xmon backports also carry a more moderate risk of regression. [1] https://lists.ubuntu.com/archives/kernel-team/2020-June/111050.html [2] https://lore.kernel.org/lkml/20200615104332.901519-1-ja...@zx2c4.com/ [3] https://git.launchpad.net/~sforshee/+git/lockdown-tests [4] https://git.zx2c4.com/american-unsigned-language/tree/american-unsigned-language.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
Gentle bump to raise visibility. If more information is needed, please let me know. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885033] Re: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04)
I tried to contact them about this, but so far I have a forum post that didn't gather importance, two cancelled support requests and a conversation where they told me they didn't support Linux, hence couldn't report a bug for Linux. Could we set this bug in a state where it won't disappear, so that other people affected can know about it and maybe raise more attention to Lenovo? -- 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/1885033 Title: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04) Status in linux package in Ubuntu: Incomplete Bug description: The touchpad switch, Fn-F6, does not work for me. It does work on Windows 10 (dual boot) The touchpad works well, but I can only set the option in System Conguration. See launchpad answer : https://answers.launchpad.net/ubuntu/+question/691511 Kubuntu 20.04 Lenovo IdeaPad L340-15IRH - Type 81LK --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yann 1350 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-20 (125 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30) Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81LK NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=0ac30ea3-dc16-4323-a1a3-acea99fa90b5 ro quiet splash resume=/dev/nvme0n1p6 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-14 (41 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN29WW 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 L340-15IRH Gaming dmi.modalias: dmi:bvnLENOVO:bvrBGCN29WW:bd02/10/2020:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884981] Re: The touchpad soesn't work at all
Thanks, that was helpful. I used the .config from the mainline 5.7.8 that I was running, but commented out the CONFIG_DEBUG_INFO_BTF and just hit enter for the default value for the remaining new parameters. It did not eliminate the problem. It does seem better, a full shutdown/start seemed to recover more frequently, but in my sample of ~10 cycles it's hard to tell if that is significant. The acpidump was identical to the previous kernel. I have attached the dmesg dump when the touchpad failed to work. ** Attachment added: "dmesg_failed_5.8" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+attachment/5393189/+files/dmesg_failed_5.8 -- 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/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) 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 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
The "lspci -vv" output misses the relevant part. Please execute the command as root. The firmware hasn't changed for years, so this should not be the reason. -- 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/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 1427 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 22 06:49:34 2020 InstallationDate: Installed on
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
btw. it looks like i have a rtl8168h as lshw report this firmware to be loaded firmware=rtl8168h-2_0.0.2 that matches with jeremy's test...there was also 8168h affected can be the firmware also be the case? how can i load firmware from 18.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/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 1427 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop:
[Kernel-packages] [Bug 1887774] Re: [UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed ERP
In the bug description I'm reading: >>> This is a problem since v4.15 commit 75492a51568b ("s390/scsi: Convert >>> timers to use timer_setup()"). <<< This makes me think that Ubuntu 18.04 / bionic is affected as well, is that correct? -- 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/1887774 Title: [UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed ERP Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: Description: zfcp: Fix panic on ERP timeout for previously dismissed ERP Symptom: Linux kernel panic due to kernel page fault in IRQ context when running zfcp_erp_timeout_handler() calling zfcp_erp_notify(). Problem: Suppose that, for unrelated reasons, FSF requests on behalf of recovery are very slow and can run into the ERP timeout. In the case at hand, we did adapter recovery to a large degree. However due to the slowness a LUN open is pending so the corresponding fc_rport remains blocked. After fast_io_fail_tmo we trigger close physical port recovery for the port under which the LUN should have been opened. The new higher order port recovery dismisses the pending LUN open ERP action and dismisses the pending LUN open FSF request. Such dismissal decouples the ERP action from the pending corresponding FSF request by setting zfcp_fsf_req->erp_action to NULL (among other things) [zfcp_erp_strategy_check_fsfreq()]. If now the ERP timeout for the pending open LUN request runs out, we must not use zfcp_fsf_req->erp_action in the ERP timeout handler. This is a problem since v4.15 commit 75492a51568b ("s390/scsi: Convert timers to use timer_setup()"). Before that we intentionally only passed zfcp_erp_action as context argument to zfcp_erp_timeout_handler(). Note: The lifetime of the corresponding zfcp_fsf_req object continues until a (late) response or an (unrelated) adapter recovery. Solution: Just like the regular response path ignores dismissed requests [zfcp_fsf_req_complete() => zfcp_fsf_protstatus_eval() => return early] the ERP timeout handler now needs to ignore dismissed requests. So simply return early in the ERP timeout handler if the FSF request is marked as dismissed in its status flags. To protect against the race where zfcp_erp_strategy_check_fsfreq() dismisses and sets zfcp_fsf_req->erp_action to NULL after our previous status flag check, return early if zfcp_fsf_req->erp_action is NULL. After all, the former ERP action does not need to be woken up as that was already done as part of the dismissal above [zfcp_erp_action_dismiss()]. Upstream-ID: 936e6b85da0476dd2edac7c51c68072da9fb4ba2 -> kernel 5.8 Will be integrated by kernel 5.8 by groovy. Please check that this also be integrated into 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883676] Re: ZFS performance drops suddenly
Hi Andrey, does setting zfs_arc_max resolve your issue? -- 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/1883676 Title: ZFS performance drops suddenly Status in zfs-linux package in Ubuntu: Incomplete Bug description: Run Phoronix Flexible IO / Random write benchmark. After running the benchmark repeatedly multiple times (occasionally it can be 30 minutes or 8 hours), the performance drops suddenly. The only way (I know of) to get back to high performance is reboot. --- $ for i in $(seq 1 1000); do printf "2\n4\n2\n1\n1\n1\nn\n" | phoronix-test-suite run fio | awk '/Average.*IOPS/ {print $2}' >> /tmp/iops; done $ less /tmp/iops ... 2095 2095 2093 783 388 389 ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.9 ProcVersionSignature: User Name 5.3.0-1023.25~18.04.1-aws 5.3.18 Uname: Linux 5.3.0-1023-aws x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Tue Jun 16 08:55:01 2020 Ec2AMI: ami-06fd83ae47b05282f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1f Ec2InstanceType: c4.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1883676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
i did not find any bios-setting regarding pcie/aspm and no "expert-mode" to get more settings also the "powercfg /energy" command in windows does not print any helpful information if i can builtin all needed drivers (localmodconfig),maybe i can use tftp with grub anyhow (if i know how to configure it)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880076 Title: ubuntu 20.4 - retransmitts with r8169 Status in linux package in Ubuntu: Incomplete Bug description: Hi, i run some network-tests (iperf3) and noticed massive retransmitts in ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network- adapter 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) if i boot my ubuntu 18.4 and did same iperf-test (same hardware, same network configuration, other client is not rebooted) i have not these retransmitts. root@bpi-r2:~# iperf3 -c 192.168.0.21 Connecting to host 192.168.0.21, port 5201 [ 5] local 192.168.0.11 port 35702 connected to 192.168.0.21 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 337 14.1 KBytes [ 5] 1.00-2.00 sec 14.9 MBytes 125 Mbits/sec 331 14.1 KBytes [ 5] 2.00-3.00 sec 15.1 MBytes 126 Mbits/sec 296 19.8 KBytes [ 5] 3.00-4.00 sec 14.7 MBytes 124 Mbits/sec 314 14.1 KBytes [ 5] 4.00-5.00 sec 12.8 MBytes 107 Mbits/sec 259 14.1 KBytes [ 5] 5.00-6.01 sec 67.4 MBytes 560 Mbits/sec 137362 KBytes [ 5] 6.01-7.00 sec 111 MBytes 940 Mbits/sec0366 KBytes [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec0409 KBytes [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec0421 KBytes [ 5] 9.00-10.00 sec 112 MBytes 936 Mbits/sec0426 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 586 MBytes 491 Mbits/sec 1674 sender [ 5] 0.00-10.01 sec 585 MBytes 491 Mbits/sec receiver iperf Done. 2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff inet 192.168.0.21/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0 valid_lft 171856sec preferred_lft 171856sec inet6 fe80::781a:829f:5030:ad6a/64 scope link noprefixroute valid_lft forever preferred_lft forever $ ethtool -S enp3s0 NIC statistics: tx_packets: 571053 rx_packets: 1184934 tx_errors: 0 rx_errors: 0 rx_missed: 1919 <<< align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 1184926 broadcast: 6 multicast: 2 tx_aborted: 0 tx_underrun: 0 2: enp3s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether e4:b9:7a:f7:c4:8b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1785166133 1184970 0 0 0 2 TX: bytes packets errors dropped carrier collsns 39395440 570500 0 0 0 0 on the other side i see dropped packets, maybe flowcontrol-related? ethtool reports "Link partner advertised pause frame use: Symmetric" but maybe flowcontrol is not working... also driver reports flowcontrol is enabled... $ dmesg | grep r8169 [0.939358] libphy: r8169: probed [0.939491] r8169 :03:00.0 eth0: RTL8168h/8111h, e4:b9:7a:f7:c4:8b, XID 541, IRQ 128 [0.939492] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [0.986853] r8169 :03:00.0 enp3s0: renamed from eth0 [3.478981] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [3.591124] r8169 :03:00.0 enp3s0: Link is Down [7.171198] r8169 :03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 1427 F
[Kernel-packages] [Bug 1887796] [NEW] Bluetooth headset cant set output as A2DP sink while using the mic as input device
Public bug reported: I have the popular Sony WH-100XM3 headset. I can connect to the headset fine using bluetooth. I set the Output device in Sound Option, there are two configurations A2DP Sink (sounds great) and HSP/HFP (sounds terrible). If I set the input device to the headset, it silently switches the output configuration to HSP/HFP and so the audio sounds terrible. If I then switch the output configuation back to A2DP sink, the audio output sounds good again, but then the input device switches to something else. So the problem is that I cant use the headset as audio input while having the good-sounding output configuration. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Description changed: I have the popular Sony WH-100XM3 headset. I can connect to the headset fine using bluetooth. I set the Output device in Sound Option, there are two configurations A2DP Sink (sounds great) and HSP/HFP (sounds terrible). If I set the input device to the headset, it silently switches the Configuration to HSP/HFP and so the audio sounds terrible. - If I then switch the configuation back to A2DP sink, the audio output - sounds good again, but then the input device switches to something else. + If I then switch the output configuation back to A2DP sink, the audio + output sounds good again, but then the input device switches to + something else. So the problem is that I cant use the headset as audio input while having the good-sounding output configuration. ** Description changed: I have the popular Sony WH-100XM3 headset. I can connect to the headset fine using bluetooth. I set the Output device in Sound Option, there are two configurations A2DP Sink (sounds great) and HSP/HFP (sounds terrible). If I set the input device to the headset, it silently switches the - Configuration to HSP/HFP and so the audio sounds terrible. + output configuration to HSP/HFP and so the audio sounds terrible. If I then switch the output configuation back to A2DP sink, the audio output sounds good again, but then the input device switches to something else. So the problem is that I cant use the headset as audio input while having the good-sounding output configuration. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1887796 Title: Bluetooth headset cant set output as A2DP sink while using the mic as input device Status in bluez package in Ubuntu: New Bug description: I have the popular Sony WH-100XM3 headset. I can connect to the headset fine using bluetooth. I set the Output device in Sound Option, there are two configurations A2DP Sink (sounds great) and HSP/HFP (sounds terrible). If I set the input device to the headset, it silently switches the output configuration to HSP/HFP and so the audio sounds terrible. If I then switch the output configuation back to A2DP sink, the audio output sounds good again, but then the input device switches to something else. So the problem is that I cant use the headset as audio input while having the good-sounding output configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
I have no background set at all (but I have Intel and Nvidia GPUs). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp